[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c5a7421-2948-674d-91a0-9cafe336401b@linaro.org>
Date: Mon, 20 Mar 2023 09:36:04 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Xingyu Wu <xingyu.wu@...rfivetech.com>,
William Qiu <william.qiu@...rfivetech.com>
Cc: linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
Conor Dooley <conor@...nel.org>,
Emil Renner Berthing <kernel@...il.dk>,
Rob Herring <robh+dt@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Hal Feng <hal.feng@...rfivetech.com>,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 3/6] dt-bindings: soc: starfive: syscon: Add optional
patternProperties
On 20/03/2023 09:26, Xingyu Wu wrote:
> On 2023/3/20 15:40, Krzysztof Kozlowski wrote:
>> On 20/03/2023 08:29, Xingyu Wu wrote:
>>> On 2023/3/20 14:37, Krzysztof Kozlowski wrote:
>>>> On 20/03/2023 04:54, Xingyu Wu wrote:
>>>>> On 2023/3/19 20:28, Krzysztof Kozlowski wrote:
>>>>>> On 16/03/2023 04:05, Xingyu Wu wrote:
>>>>>>> Add optional compatible and patternProperties.
>>>>>>>
>>>>>>> Signed-off-by: Xingyu Wu <xingyu.wu@...rfivetech.com>
>>>>>>> ---
>>>>>>> .../soc/starfive/starfive,jh7110-syscon.yaml | 39 ++++++++++++++++---
>>>>>>> 1 file changed, 33 insertions(+), 6 deletions(-)
>>>>>>>
>>>>>>> diff --git a/Documentation/devicetree/bindings/soc/starfive/starfive,jh7110-syscon.yaml b/Documentation/devicetree/bindings/soc/starfive/starfive,jh7110-syscon.yaml
>>>>>>> index ae7f1d6916af..b61d8921ef42 100644
>>>>>>> --- a/Documentation/devicetree/bindings/soc/starfive/starfive,jh7110-syscon.yaml
>>>>>>> +++ b/Documentation/devicetree/bindings/soc/starfive/starfive,jh7110-syscon.yaml
>>>>>>> @@ -15,16 +15,31 @@ description: |
>>>>>>>
>>>>>>> properties:
>>>>>>> compatible:
>>>>>>> - items:
>>>>>>> - - enum:
>>>>>>> - - starfive,jh7110-aon-syscon
>>>>>>> - - starfive,jh7110-stg-syscon
>>>>>>> - - starfive,jh7110-sys-syscon
>>>>>>> - - const: syscon
>>>>>>> + oneOf:
>>>>>>> + - items:
>>>>>>> + - enum:
>>>>>>> + - starfive,jh7110-aon-syscon
>>>>>>> + - starfive,jh7110-stg-syscon
>>>>>>> + - starfive,jh7110-sys-syscon
>>>>>>> + - const: syscon
>>>>>>> + - items:
>>>>>>> + - enum:
>>>>>>> + - starfive,jh7110-aon-syscon
>>>>>>> + - starfive,jh7110-stg-syscon
>>>>>>> + - starfive,jh7110-sys-syscon
>>>>>>> + - const: syscon
>>>>>>> + - const: simple-mfd
>>
>> BTW, this also looks wrong. You just said that clock controller exists
>> only in few variants. Also, why sometimes the same device goes with
>> simple-mfd and sometimies without? It's the same device.
>
> Oh yes, If modified to:
>
> oneOf:
> - items:
> - enum:
> - starfive,jh7110-aon-syscon
> - starfive,jh7110-stg-syscon
> - const: syscon
> - items:
> - const: starfive,jh7110-sys-syscon
> - const: syscon
> - const: simple-mfd
>
> Or:
>
> - minItems: 2
> items:
> - enum:
> - starfive,jh7110-aon-syscon
> - starfive,jh7110-stg-syscon
> - starfive,jh7110-sys-syscon
> - const: syscon
> - const: simple-mfd
>
>
> Which one is better?
If aon and stg are not supposed to have children, then only the first is
correct. It's not which is better, the second is not really correct in
such case.
Best regards,
Krzysztof
Powered by blists - more mailing lists