[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f42248f1-c8fa-4ca1-806a-94c06cba8689@linaro.org>
Date: Wed, 6 Dec 2023 11:28:34 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Inochi Amaoto <inochiama@...look.com>,
Conor Dooley <conor@...nel.org>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Chen Wang <unicorn_wang@...look.com>,
Jisheng Zhang <jszhang@...nel.org>, qiujingbao.dlmu@...il.com,
dlan@...too.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: clock: sophgo: Add clock controller
of CV1800 series SoC
On 06/12/2023 03:04, Inochi Amaoto wrote:
>>>> +
>>>> + clock-names:
>>>> + items:
>>>> + - const: osc
>>>
>>> You have one clock, why do you need a name?
>>
>> I am not pretty familiar with this. I just wrote this binding by
>> referencing others. Maybe use "maxItems: 1" is just fine?
No, just drop clock-names and get clocks by indices in the driver.
>>
>
> I have referenced this name in the clk_parent_data as the global clock
> parent. Removing this will cause driver broken.
It's not related.
Best regards,
Krzysztof
Powered by blists - more mailing lists