[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc7797641f9b9a2e5581ac8396ac75260b691e6c.camel@physik.fu-berlin.de>
Date: Wed, 24 Apr 2024 09:08:24 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, Rob Herring
<robh@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Yoshinori Sato
<ysato@...rs.sourceforge.jp>, Rich Felker <dalias@...c.org>,
devicetree@...r.kernel.org, linux-sh@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Kousik Sanagavarapu <five231003@...il.com>
Subject: Re: [PATCH] sh: j2: drop incorrect SPI controller max frequency
property
On Wed, 2024-04-24 at 08:48 +0200, Krzysztof Kozlowski wrote:
> On Fri, 22 Mar 2024 07:42:21 +0100, Krzysztof Kozlowski wrote:
> > The J2 SPI controller bindings never allowed spi-max-frequency property
> > in the controller node. Neither old spi-bus.txt bindings, nor new DT
> > schema allows it. Linux driver does not parse that property from
> > controller node, thus drop it from DTS as incorrect hardware
> > description. The SPI child device has already the same property with
> > the same value, so functionality should not be affected.
> >
> > [...]
>
> Month passed, no replies from maintainers about picking it up. Dunno, looks
> abandoned, so let me grab this. If anyone else wants to pick it up, let me
> know.
I'll pick it up this weekend.
Sorry, I have been quite busy the past weeks with my dayjob.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists