[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e1e12c86-da0d-0ae0-0542-86bdc4c81bb3@linaro.org>
Date: Thu, 6 Jul 2023 09:51:34 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Jerome Brunet <jbrunet@...libre.com>,
Rob Herring <robh@...nel.org>,
Neil Armstrong <neil.armstrong@...aro.org>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Kevin Hilman <khilman@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
linux-amlogic@...ts.infradead.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 2/3] dt-bindings: clock: amlogic: convert
amlogic,gxbb-aoclkc.txt to dt-schema
On 06/07/2023 09:15, Jerome Brunet wrote:
>>> + then:
>>> + properties:
>>> + clock-names:
>>> + minItems: 2
>>> + items:
>>> + - const: xtal
>>> + - const: mpeg-clk
>>> + - const: ext-32k-0
>>> + - const: ext-32k-1
>>> + - const: ext-32k-2
>>
>> As the names are always the same, move this to top-level and just set
>> the length here (except the constraints are the same as top-level, so
>> you can just drop this if/then).
>
> If this is done, aren't we losing information ?
>
> For example, "ext-32k-1" would become valid with a g12a as long as the
> number of clocks is alright, which it is not.
How it would be valid? It would be fourth item but only three are allowed.
>
> I'm not concerned by the automated verification, more the information
> provided to the users, which we used to have in the txt format.
No information is lost here, unless you claim that entries are entirely
different?
Best regards,
Krzysztof
Powered by blists - more mailing lists