From: Shawn Guo <shawn.guo@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Sivaprakash Murugesan <sivaprak@codeaurora.org>,
Benjamin Li <benl@squareup.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 2/4] clk: qcom: a53pll/mux: Use unique clock name
Date: Sat, 10 Jul 2021 15:34:53 +0800 [thread overview]
Message-ID: <20210710073449.GC11342@dragon> (raw)
In-Reply-To: <YOktbWmMKEw7g3+E@yoga>
On Sat, Jul 10, 2021 at 12:17:33AM -0500, Bjorn Andersson wrote:
> On Sat 03 Jul 21:40 CDT 2021, Shawn Guo wrote:
>
> > Different from MSM8916 which has only one a53pll/mux clock, MSM8939 gets
> > three for Cluster0 (little cores), Cluster1 (big cores) and CCI (Cache
> > Coherent Interconnect). That said, a53pll/mux clock needs to be named
> > uniquely. Append @unit-address of device node to the clock name, so
> > that a53pll/mux will be named like below on MSM8939.
> >
> > a53pll@b016000
> > a53pll@b116000
> > a53pll@b1d0000
> >
> > a53mux@b1d1000
> > a53mux@b011000
> > a53mux@b111000
> >
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > ---
> > drivers/clk/qcom/a53-pll.c | 8 +++++++-
> > drivers/clk/qcom/apcs-msm8916.c | 8 +++++++-
> > 2 files changed, 14 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/clk/qcom/a53-pll.c b/drivers/clk/qcom/a53-pll.c
> > index d6756bd777ce..96a118be912d 100644
> > --- a/drivers/clk/qcom/a53-pll.c
> > +++ b/drivers/clk/qcom/a53-pll.c
> > @@ -37,6 +37,7 @@ static const struct regmap_config a53pll_regmap_config = {
> > static int qcom_a53pll_probe(struct platform_device *pdev)
> > {
> > struct device *dev = &pdev->dev;
> > + struct device_node *np = dev->of_node;
> > struct regmap *regmap;
> > struct resource *res;
> > struct clk_pll *pll;
> > @@ -66,7 +67,12 @@ static int qcom_a53pll_probe(struct platform_device *pdev)
> > pll->status_bit = 16;
> > pll->freq_tbl = a53pll_freq;
> >
> > - init.name = "a53pll";
> > + /* Use an unique name by appending @unit-address */
> > + init.name = devm_kasprintf(dev, GFP_KERNEL, "a53pll%s",
> > + strchrnul(np->full_name, '@'));
>
> While the result is nice, this isn't...
>
> Is your dev_name() reasonable? What about "%s:a53pll", dev_name(dev) ?
dev_name() is somehow reasonable for a53pll.
b016000.clock-controller:a53pll
b116000.clock-controller:a53pll
b1d0000.clock-controller:a53pll
But I prefer to the existing names, because I would like to use the same
naming schema for both a53pll and a53mux. If using dev_name() on a53mux,
we will get the following which is less reasonable.
qcom-apcs-msm8916-clk.1.auto:a53mux
qcom-apcs-msm8916-clk.2.auto:a53mux
qcom-apcs-msm8916-clk.3.auto:a53mux
Shawn
next prev parent reply other threads:[~2021-07-10 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 2:40 [PATCH v2 0/4] Add MSM8939 APCS/A53PLL clock support Shawn Guo
2021-07-04 2:40 ` [PATCH v2 1/4] clk: qcom: apcs-msm8916: Flag a53mux instead of a53pll as critical Shawn Guo
2021-08-06 1:53 ` Stephen Boyd
2021-07-04 2:40 ` [PATCH v2 2/4] clk: qcom: a53pll/mux: Use unique clock name Shawn Guo
2021-07-10 5:17 ` Bjorn Andersson
2021-07-10 7:34 ` Shawn Guo [this message]
2021-08-06 1:53 ` Stephen Boyd
2021-07-04 2:40 ` [PATCH v2 3/4] dt-bindings: clock: Update qcom,a53pll bindings for MSM8939 support Shawn Guo
2021-07-12 14:58 ` Rob Herring
2021-08-06 1:53 ` Stephen Boyd
2021-07-04 2:40 ` [PATCH v2 4/4] clk: qcom: a53-pll: Add MSM8939 a53pll support Shawn Guo
2021-08-06 1:53 ` Stephen Boyd
2021-07-07 21:34 ` [PATCH v2 0/4] Add MSM8939 APCS/A53PLL clock support Vincent Knecht
2021-07-09 2:13 ` Shawn Guo
2021-08-04 8:47 ` Shawn Guo
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=20210710073449.GC11342@dragon \
--to=shawn.guo@linaro.org \
--cc=benl@squareup.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sivaprak@codeaurora.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).