[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4de3b1b-31b6-c257-29a5-f404ff0fbe99@starfivetech.com>
Date: Fri, 12 May 2023 18:22:21 +0800
From: Minda Chen <minda.chen@...rfivetech.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Roger Quadros <rogerq@...nel.org>,
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 2023/5/11 22: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.
>
> Best regards,
> Krzysztof
>
I can change like these. Are these changes can be approved?
lpm , bus clock and "pwrup" reset can be specific cases. (The changes are from snps,dwc3.yaml.)
clocks:
description:
In general the core supports two types of clocks. bus is a SoC Bus
Clock(AHB/AXI/APB). lpm is a link power management clock. But particular
cases may differ from that having less or more clock sources with
another names.
clock-names:
contains:
anyOf:
- enum: [bus, lpm]
- true
resets:
description:
In general the core supports controller power-up reset. Also clock and
other resets can be added. Particular cases may differ from that having
less or more resets with another names.
reset-names:
contains:
anyOf:
- const: pwrup
- true
Powered by blists - more mailing lists