From: Stephen Boyd <sboyd@kernel.org>
To: "Benoît Cousson" <bcousson@baylibre.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Tero Kristo" <kristo@kernel.org>,
"Tony Lindgren" <tony@atomide.com>
Cc: Andreas Kemnade <andreas@kemnade.info>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/4] clk: ti: Handle possible address in the node name
Date: Wed, 21 Feb 2024 21:11:54 -0800 [thread overview]
Message-ID: <1c1cf894cab0b81ed2af953ec30890ed.sboyd@kernel.org> (raw)
In-Reply-To: <20240213105730.5287-2-tony@atomide.com>
Quoting Tony Lindgren (2024-02-13 02:56:41)
> In order to use #address-cells = <1> and start making use of the
> standard reg property, let's prepare things to ignore the possible
> address in the clock node name.
>
> Unless the clock-output-names property is used, the legacy clocks still
> fall back to matching the clock data based on the node name.
>
> We use cleanup.h to simplify the return path for freeing tmp.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2024-02-22 5:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 10:56 [PATCH 0/4] Use reg instead of ti,bit-shift for clksel Tony Lindgren
2024-02-13 10:56 ` [PATCH 1/4] clk: ti: Handle possible address in the node name Tony Lindgren
2024-02-22 5:11 ` Stephen Boyd [this message]
2024-02-13 10:56 ` [PATCH 2/4] clk: ti: Improve clksel clock bit parsing for reg property Tony Lindgren
2024-02-22 5:11 ` Stephen Boyd
2024-02-13 10:56 ` [PATCH 3/4] ARM: dts: am3: Update clksel clocks to use reg instead of ti,bit-shift Tony Lindgren
2024-02-13 10:56 ` [PATCH 4/4] ARM: dts: omap3: " Tony Lindgren
2024-02-13 23:11 ` [PATCH 0/4] Use reg instead of ti,bit-shift for clksel Andreas Kemnade
2024-02-14 5:40 ` Tony Lindgren
2024-02-29 7:06 ` Tony Lindgren
2024-03-02 19:18 ` Andreas Kemnade
2024-03-08 9:00 ` 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=1c1cf894cab0b81ed2af953ec30890ed.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=andreas@kemnade.info \
--cc=bcousson@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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 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.