[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5dd3237f-e0a2-4214-a63f-233e89a26b8d@linaro.org>
Date: Fri, 22 Mar 2024 07:34:24 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Kousik Sanagavarapu <five231003@...il.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-spi@...r.kernel.org, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Mark Brown <broonie@...nel.org>, Shuah Khan <skhan@...uxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@...il.com>
Subject: Re: [PATCH v2] spi: dt-bindings: jcore,spi: convert spi-jcore to
dtschema
On 22/03/2024 07:23, Kousik Sanagavarapu wrote:
> On Fri, 22 Mar 2024, 11:33 Krzysztof Kozlowski, <
> krzysztof.kozlowski@...aro.org> wrote:
>
>> On 21/03/2024 19:02, Kousik Sanagavarapu wrote:
>>
>>> + spi-max-frequency:
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>
>> No, drop. From which other SPI binding did you take it? I asked you to
>> look at existing code.
>>
>
> Without this, "make dt_binding_check" would break though, right at the
> position in the example where "spi-max-frequency" is used. That was
> also the reason why additionalProperties was set to true in the last
> iteration, but after reading the doc more carefully I realized that was
> wrong after you pointed it out.
>
> I followed along bindings/spi/nvidia,tegra114-spi.yaml.
OK, you are right, the property is used here in controller node, however
Linux driver never parsed it. It was never used, so I propose to drop it
from the binding and example. You can mention in commit msg that
spi-max-frequency was not documented thus you drop it from the example.
DTS should be fixed as well. I'll send a patch for it.
Best regards,
Krzysztof
Powered by blists - more mailing lists