From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Michael Turquette <mturquette@baylibre.com>,
Taniya Das <quic_tdas@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: a53-pll: convert to use parent_data rather than parent_names
Date: Mon, 18 Jul 2022 21:39:03 -0500 [thread overview]
Message-ID: <YtYZR9tsfNw8OwvO@builder.lan> (raw)
In-Reply-To: <20220620010643.1533531-1-dmitry.baryshkov@linaro.org>
On Sun 19 Jun 20:06 CDT 2022, Dmitry Baryshkov wrote:
> Change a53-pll driver to use clk_parent_data rather than always looking
> up the xo clock in the system clock list.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/clk/qcom/a53-pll.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/qcom/a53-pll.c b/drivers/clk/qcom/a53-pll.c
> index 329d2c5356d8..f9c5e296dba2 100644
> --- a/drivers/clk/qcom/a53-pll.c
> +++ b/drivers/clk/qcom/a53-pll.c
> @@ -127,7 +127,9 @@ static int qcom_a53pll_probe(struct platform_device *pdev)
> if (!init.name)
> return -ENOMEM;
>
> - init.parent_names = (const char *[]){ "xo" };
> + init.parent_data = &(const struct clk_parent_data){
> + .fw_name = "xo", .name = "xo_board",
This used to look up the globally named clock "xo", now it picked up
"xo_board". If this is intentional, could you please update the commit
message to cover this part?
Thanks,
Bjorn
> + };
> init.num_parents = 1;
> init.ops = &clk_pll_sr2_ops;
> pll->clkr.hw.init = &init;
> --
> 2.35.1
>
prev parent reply other threads:[~2022-07-19 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 1:06 [PATCH] clk: qcom: a53-pll: convert to use parent_data rather than parent_names Dmitry Baryshkov
2022-07-19 2:39 ` Bjorn Andersson [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=YtYZR9tsfNw8OwvO@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=swboyd@chromium.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