[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9c3d29f-0507-e8a2-9e0a-4499ede6aeb5@starfivetech.com>
Date: Sat, 6 May 2023 09:34:30 +0800
From: Minda Chen <minda.chen@...rfivetech.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.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>,
Roger Quadros <rogerq@...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 v1 1/2] dt-binding: cdns,usb3: Add clock and reset
On 2023/5/3 4:10, Krzysztof Kozlowski wrote:
> On 02/05/2023 10:18, Minda Chen wrote:
>> To support generic clock and reset init in Cadence USBSS
>> controller. Add clock and reset dts configuration.
>
> s/. Add/, add/
> (although still weird sentence)
>
ok
>>
>> Signed-off-by: Minda Chen <minda.chen@...rfivetech.com>
>> ---
>> Documentation/devicetree/bindings/usb/cdns,usb3.yaml | 12 ++++++++++++
>
> Also update the example or any in-tree DTS. Why existing users do not
> need it? Aren't you duplicating clocks with wrapping node?
>
> Best regards,
> Krzysztof
>
I will update the example. Exiting users are NXP and TI. NXP codes do not contain clock and resets, TI usb2 refclk require to set clock rateļ¼
TI codes can't direct use it. And I don't know TI's hardware. Maybe Roger can take into account to use it.
Powered by blists - more mailing lists