[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAN19-EdU5OPb=0Qz0_b3GxAJsjD_DAoVRrQM1+38p2SGVTAOgQ@mail.gmail.com>
Date: Fri, 22 Mar 2024 12:03:33 +0530
From: Kousik Sanagavarapu <five231003@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-spi@...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: [PATCH v2] spi: dt-bindings: jcore,spi: convert spi-jcore to dtschema
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.
(Sorry for the HTML mail ping, I'm replying from mobile)
Powered by blists - more mailing lists