From: Stephen Boyd <sboyd@kernel.org>
To: Tony Lindgren <tony@atomide.com>, linux-clk@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 8/8] clk: ti: Update component clocks to use ti_dt_clk_name()
Date: Thu, 10 Mar 2022 19:32:00 -0800 [thread overview]
Message-ID: <20220311033202.41D10C340EC@smtp.kernel.org> (raw)
In-Reply-To: <20220204071449.16762-9-tony@atomide.com>
Quoting Tony Lindgren (2022-02-03 23:14:49)
> Let's update all the TI component clocks to use ti_dt_clk_name() instead
> of devicetree node name if available.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2022-03-11 3:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 7:14 [PATCH 0/8] Clock changes for TI dts reg and node name issues Tony Lindgren
2022-02-04 7:14 ` [PATCH 1/8] clk: ti: Constify clkctrl_name Tony Lindgren
2022-03-11 3:30 ` Stephen Boyd
2022-02-04 7:14 ` [PATCH 2/8] clk: ti: Preserve node in ti_dt_clocks_register() Tony Lindgren
2022-03-11 3:31 ` Stephen Boyd
2022-02-04 7:14 ` [PATCH 3/8] clk: ti: Optionally parse IO address from parent clock node Tony Lindgren
2022-03-11 3:31 ` Stephen Boyd
2022-02-04 7:14 ` [PATCH 4/8] clk: ti: Add ti_find_clock_provider() to use clock-output-names Tony Lindgren
2022-03-11 3:31 ` Stephen Boyd
2022-02-04 7:14 ` [PATCH 5/8] clk: ti: Use clock-output-names for clkctrl Tony Lindgren
2022-03-11 3:31 ` Stephen Boyd
2022-02-04 7:14 ` [PATCH 6/8] clk: ti: Add ti_dt_clk_name() helper to use clock-output-names Tony Lindgren
2022-03-11 3:31 ` Stephen Boyd
2022-02-04 7:14 ` [PATCH 7/8] clk: ti: Update pll and clockdomain clocks to use ti_dt_clk_name() Tony Lindgren
2022-03-11 3:31 ` Stephen Boyd
2022-02-04 7:14 ` [PATCH 8/8] clk: ti: Update component " Tony Lindgren
2022-03-11 3:32 ` Stephen Boyd [this message]
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=20220311033202.41D10C340EC@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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).