[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b98196a-c898-4d08-9101-31feb4e59b5c@kernel.org>
Date: Fri, 27 Sep 2024 09:30:30 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Frank Wang <frawang.cn@...il.com>, vkoul@...nel.org, kishon@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, heiko@...ech.de
Cc: linux-phy@...ts.infradead.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-rockchip@...ts.infradead.org, william.wu@...k-chips.com,
tim.chen@...k-chips.com, frank.wang@...k-chips.com
Subject: Re: [PATCH v3 1/2] dt-bindings: phy: rockchip,inno-usb2phy: add
rk3576
On 27/09/2024 09:01, Frank Wang wrote:
> Hi Krzysztof,
>
> On 2024/9/26 22:19, Krzysztof Kozlowski wrote:
>> On 26/09/2024 12:32, Frank Wang wrote:
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - rockchip,rk3576-usb2phy
>>> + then:
>>> + properties:
>>> + clocks:
>>> + minItems: 3
>>> + maxItems: 3
>> Read one more time the example I gave you. Top-level constraints are
>> saying max one clock.
>>
>> Best regards,
>> Krzysztof
>>
>
> Sorry for overlooking this, I will set both "clocks" and "clock-names"
> to true, and add the else case below the above codes for the "old" SoCs.
> Just like the below.
>
> - clocks:
> - maxItems: 1
> + clocks: true
>
> - clock-names:
> - const: phyclk
> + clock-names: true
For the third time, read the code I gave you. Do you see something like
this there? Why doing all the time something different than existing code?
Best regards,
Krzysztof
Powered by blists - more mailing lists