[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aJ7nCL0PS0DX8rtk@stanley.mountain>
Date: Fri, 15 Aug 2025 10:51:36 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Peng Fan <peng.fan@....nxp.com>
Cc: Peng Fan <peng.fan@....com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Sudeep Holla <sudeep.holla@....com>,
Cristian Marussi <cristian.marussi@....com>,
Marco Felsch <m.felsch@...gutronix.de>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
arm-scmi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/3] clk: conf: Support assigned-clock-sscs
On Fri, Aug 15, 2025 at 04:50:42PM +0800, Peng Fan wrote:
> >> + if (modfreq_hz || spread_bp || method) {
> >> + rc = of_parse_phandle_with_args(node, "assigned-clocks",
> >> + "#clock-cells", index, &clkspec);
> >> + if (rc < 0) {
> >> + /* skip empty (null) phandles */
> >> + if (rc == -ENOENT)
> >> + continue;
> >> + else
> >> + return rc;
> >> + }
> >> +
> >> + if (clkspec.np == node && !clk_supplier) {
> >
> >Could you add a comment for this condition? It's strange to me that we
> >don't iterate through the whole array.
>
> I just follow the logic in __set_clk_parents and __set_clk_rates, nothing
> special here.
>
> It is just like to phase out cases as below:
> node-x {
> /* node-x is not a clk provider, but assigned-clocks uses node-x phandle */
> assigned-clocks = <&node-x XYZ>;
> }
>
Ah. Great. Thanks.
regards,
dan carpenter
Powered by blists - more mailing lists