From: Tony Lindgren <tony@atomide.com>
To: 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: [PATCH 0/8] Clock changes for TI dts reg and node name issues
Date: Fri, 4 Feb 2022 09:14:41 +0200 [thread overview]
Message-ID: <20220204071449.16762-1-tony@atomide.com> (raw)
Hi all,
Here are TI clock changes that allow us to update the devicetree files to
use clock-output-names instead of non-standard node names for clocks.
The related devicetree binding changes have been sent and are the
folloing patches:
[PATCHv2] dt-bindings: clock: Add binding for TI clksel
[PATCH 1/3] dt-bindings: omap: Add clock-output-names and #clock-cells
In addition to these changes, also devicetree changes are needed. Some
SoCs also need patches to unify the internal clock names. I'll be
sending those out separately.
Regards,
Tony
Tony Lindgren (8):
clk: ti: Constify clkctrl_name
clk: ti: Preserve node in ti_dt_clocks_register()
clk: ti: Optionally parse IO address from parent clock node
clk: ti: Add ti_find_clock_provider() to use clock-output-names
clk: ti: Use clock-output-names for clkctrl
clk: ti: Add ti_dt_clk_name() helper to use clock-output-names
clk: ti: Update pll and clockdomain clocks to use ti_dt_clk_name()
clk: ti: Update component clocks to use ti_dt_clk_name()
drivers/clk/ti/apll.c | 13 ++++--
drivers/clk/ti/autoidle.c | 2 +-
drivers/clk/ti/clk-dra7-atl.c | 6 ++-
drivers/clk/ti/clk.c | 86 +++++++++++++++++++++++++++++++----
drivers/clk/ti/clkctrl.c | 24 ++++++++--
drivers/clk/ti/clock.h | 1 +
drivers/clk/ti/clockdomain.c | 2 +-
drivers/clk/ti/composite.c | 6 ++-
drivers/clk/ti/divider.c | 6 ++-
drivers/clk/ti/dpll.c | 8 ++--
drivers/clk/ti/fapll.c | 11 +++--
drivers/clk/ti/fixed-factor.c | 2 +-
drivers/clk/ti/gate.c | 4 +-
drivers/clk/ti/interface.c | 4 +-
drivers/clk/ti/mux.c | 4 +-
15 files changed, 143 insertions(+), 36 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-04 7:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 7:14 Tony Lindgren [this message]
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
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=20220204071449.16762-1-tony@atomide.com \
--to=tony@atomide.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.