[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c028e0b1-2eff-a6f4-c4c1-83b1a77bd6ba@linaro.org>
Date: Sat, 13 May 2023 20:43:41 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Roger Quadros <rogerq@...nel.org>,
Minda Chen <minda.chen@...rfivetech.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Pawel Laszczak <pawell@...ence.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Peter Chen <peter.chen@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: cdns,usb3: Add clock and reset
On 12/05/2023 13:08, Roger Quadros wrote:
>
>
> On 11/05/2023 17:49, Krzysztof Kozlowski wrote:
>> On 11/05/2023 14:16, Roger Quadros wrote:
>>>
>>>
>>> On 11/05/2023 12:26, Krzysztof Kozlowski wrote:
>>>> On 10/05/2023 15:28, Minda Chen wrote:
>>>>> To support generic clock and reset init in Cadence USBSS
>>>>> controller, add clock and reset dts configuration.
>>>>>
>>>>> Signed-off-by: Minda Chen <minda.chen@...rfivetech.com>
>>>>> ---
>>>>> .../devicetree/bindings/usb/cdns,usb3.yaml | 14 ++++++++++++++
>>>>> 1 file changed, 14 insertions(+)
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/usb/cdns,usb3.yaml b/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
>>>>> index cae46c4982ad..623c6b34dee3 100644
>>>>> --- a/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
>>>>> +++ b/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
>>>>> @@ -42,6 +42,18 @@ properties:
>>>>> - const: otg
>>>>> - const: wakeup
>>>>>
>>>>> + clocks:
>>>>> + minItems: 1
>>>>> + maxItems: 8
>>>>> + description:
>>>>> + USB controller clocks.
>>>>
>>>> You need to list the items. And why is it variable? Your clock choice in
>>>> the example is poor, I doubt it is real.
>>>>
>>>>> +
>>>>> + resets:
>>>>> + minItems: 1
>>>>> + maxItems: 8
>>>>> + description:
>>>>> + USB controller generic resets.
>>>>
>>>> Here as well.
>>>>
>>>> You had one clock last time, thus the review was - drop the names. Now
>>>> you changed it to 8 clocks... I don't understand.
>>>>
>>>
>>> Different platforms may have different number of clocks/resets or none.
>>> So I don't think minItems/maxItems should be specified.
>>
>> Yeah, but we want the clocks to be specific per platform. Not anything
>> anywhere.
>>
>
> Agreed. So we don't specify min/maxItems at top level but use conditional
> constraints per platform?
> Which means we will need to add platform specific compatibles as well.
Yes, exactly. This can be done here in this binding or through some
re-usable common part and then multiple bindings using it and customizing.
Best regards,
Krzysztof
Powered by blists - more mailing lists