From: Tony Lindgren <tony@atomide.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, "Tero Kristo" <kristo@kernel.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/5] ARM: dts: Add clock-output-names for omap4
Date: Sat, 12 Mar 2022 10:12:35 +0200 [thread overview]
Message-ID: <YixV85yYNy+xxYEE@atomide.com> (raw)
In-Reply-To: <20220311033439.15316C340EC@smtp.kernel.org>
Hi,
* Stephen Boyd <sboyd@kernel.org> [220311 03:33]:
> Quoting Tony Lindgren (2022-02-04 00:43:35)
> > To stop using the non-standard node name based clock naming, let's
> > first add the clock-output-names property. This allows us to stop using
> > the internal legacy clock naming and unify the naming for the TI SoCs in
> > the following patches.
> >
> > Note that we must wait on fixing the node naming issues until after the
> > internal clock names have been updated to avoid adding name translation
> > unnecessarily.
> >
> > Cc: Stephen Boyd <sboyd@kernel.org>
> > Cc: Tero Kristo <kristo@kernel.org>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> > ---
>
> I assume I don't merge this through clk tree.
AFAIK these won't conflict with other dts changes, so you could merge
them if you like and they look OK. Or we can also wait for v5.18-rc1 and
then I'll pick up the dts changes.
> > arch/arm/boot/dts/omap443x-clocks.dtsi | 1 +
> > arch/arm/boot/dts/omap446x-clocks.dtsi | 2 +
> > arch/arm/boot/dts/omap44xx-clocks.dtsi | 165 +++++++++++++++++++++++++
> > 3 files changed, 168 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/omap443x-clocks.dtsi b/arch/arm/boot/dts/omap443x-clocks.dtsi
> > --- a/arch/arm/boot/dts/omap443x-clocks.dtsi
> > +++ b/arch/arm/boot/dts/omap443x-clocks.dtsi
> > @@ -8,6 +8,7 @@ &prm_clocks {
> > bandgap_fclk: bandgap_fclk@1888 {
> > #clock-cells = <0>;
> > compatible = "ti,gate-clock";
> > + clock-output-names = "bandgap_fclk";
>
> At this point clock-output-names is basically a debug feature. It would
> be better to use clocks property in consumer nodes and then use
> clk_parent_data to link up the clk tree. Not sure if that matters here
> though? I can understand the desire to have "usable" names vs. some
> not very useful name be auto generated..
Well the use case here is to be able to rename bandgap_fclk@1888 node to
use the standard clock node name like the patches I've posted for am3/4
and dra7 are doing.
We can't do that quite yet rename the non-standard clock nodes for omap4/5,
first the TI clock driver internal clock naming needs to be unified to
follow am3/4 and dra7 to avoid adding yet more name translation code. I'll
post patches for those changes after v5.18-rc1.
I agree relying on the clock-output-names is not ideal, but currently the
TI clocks are still structured to match clock nodes to the clock data
based on the name. I think only the TI clkctrl clock currently maps the
devicetree nodes to clock data based on the IO address currently.
Probably best to fix the warnings first before tackling any further
driver changes :)
The TI SoCs produce over 70k unique_unit_address warnings with make W=1
and over 30k node_name_chars_strict warnings with make W=2, these are
all mostly for clocks..
Regards,
Tony
next prev parent reply other threads:[~2022-03-12 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:43 [PATCH 0/5] Unify omap4/5 clocks with clock-output-names Tony Lindgren
2022-02-04 8:43 ` [PATCH 1/5] ARM: dts: Add clock-output-names for omap4 Tony Lindgren
2022-03-11 3:34 ` Stephen Boyd
2022-03-12 8:12 ` Tony Lindgren [this message]
2022-03-15 21:25 ` Stephen Boyd
2022-02-04 8:43 ` [PATCH 2/5] ARM: dts: Drop custom clkctrl compatible and update omap4 l4per Tony Lindgren
2022-02-04 8:43 ` [PATCH 3/5] ARM: dts: Add clock-output-names for omap5 Tony Lindgren
2022-02-04 8:43 ` [PATCH 4/5] ARM: dts: Drop custom clkctrl compatible and update omap5 l4per Tony Lindgren
2022-02-04 8:43 ` [PATCH 5/5] clk: ti: Stop using legacy clkctrl names for omap4 and 5 Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YixV85yYNy+xxYEE@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).