[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <A9A1C6C4-2B40-4769-9C9D-3A4DB2C27C95@gmail.com>
Date: Wed, 24 Apr 2024 15:59:04 +0900
From: "D. Jeff Dionne" <djeffdionne@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: 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>,
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
devicetree@...r.kernel.org,
linux-sh@...r.kernel.org,
linux-kernel@...r.kernel.org,
Kousik Sanagavarapu <five231003@...il.com>
Subject: Re: [PATCH] sh: j2: drop incorrect SPI controller max frequency
property
Adrian,
IMHO, this driver should go through the SH tree. Thanks Rob, for testing the patch.
J.
> On Apr 24, 2024, at 3:48 PM, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> 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.
>
> Applied, thanks!
>
> [1/1] sh: j2: drop incorrect SPI controller max frequency property
> https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-dt.git/commit/?h=next/dt&id=cc92bf017f7c66c8a4050c61a7d11ddfd43f5cee
>
> Best regards,
> --
> Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>
Powered by blists - more mailing lists