[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bf6cd1c9-d60a-4ef1-89f3-5d28e003ce2d@kernel.org>
Date: Thu, 25 Jul 2024 08:21:00 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: "sunyeal.hong" <sunyeal.hong@...sung.com>, 'Rob Herring' <robh@...nel.org>
Cc: 'Sylwester Nawrocki' <s.nawrocki@...sung.com>,
'Chanwoo Choi' <cw00.choi@...sung.com>,
'Alim Akhtar' <alim.akhtar@...sung.com>,
'Michael Turquette' <mturquette@...libre.com>,
'Stephen Boyd' <sboyd@...nel.org>, 'Conor Dooley' <conor+dt@...nel.org>,
linux-samsung-soc@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/4] dt-bindings: clock: add ExynosAuto v920 SoC CMU
bindings
On 25/07/2024 05:03, sunyeal.hong wrote:
> - dts
> cmu_misc: clock-controller@...20000 {
> compatible = "samsung,exynosautov920-cmu-misc";
> reg = <0x10020000 0x8000>;
> #clock-cells = <1>;
>
> clocks = <&xtcxo>,
> <&cmu_top DOUT_CLKCMU_MISC_NOC>;
> clock-names = "oscclk",
> "noc";
> };
>
> In this case, can you tell me how to handle it?
> And if a new clock item is added and a new cmu block uses only the clock item added and oscclk, a problem may occur.
The same problem was in your original version, so why suddenly it appeared?
Anyway, why clock would be missing? You just wrote in the bindings that
there is such input clock.
Best regards,
Krzysztof
Powered by blists - more mailing lists