From: Stephen Boyd <sboyd@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Stephen Boyd <swboyd@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
patches@lists.linux.dev, linux-clk@vger.kernel.org,
Taniya Das <quic_tdas@quicinc.com>,
Amit Pundir <amit.pundir@linaro.org>
Subject: Re: [PATCH v2 2/2] clk: qcom: gcc-sm8550: Don't use shared clk_ops for QUPs
Date: Wed, 28 Aug 2024 10:13:26 -0700 [thread overview]
Message-ID: <00adff607d757702fa673942ed60c354.sboyd@kernel.org> (raw)
In-Reply-To: <1684855f-5901-459a-beb7-2569003b30ac@linaro.org>
Quoting Neil Armstrong (2024-08-28 05:22:37)
> On 28/08/2024 01:12, Stephen Boyd wrote:
> > diff --git a/drivers/clk/qcom/gcc-sm8550.c b/drivers/clk/qcom/gcc-sm8550.c
> > index 7944ddb4b47d..0244a05866b8 100644
> > --- a/drivers/clk/qcom/gcc-sm8550.c
> > +++ b/drivers/clk/qcom/gcc-sm8550.c
> > @@ -992,7 +992,7 @@ static struct clk_init_data gcc_qupv3_wrap2_s7_clk_src_init = {
> > .parent_data = gcc_parent_data_0,
> > .num_parents = ARRAY_SIZE(gcc_parent_data_0),
> > .flags = CLK_SET_RATE_PARENT,
> > - .ops = &clk_rcg2_shared_ops,
> > + .ops = &clk_rcg2_ops,
> > };
> >
> > static struct clk_rcg2 gcc_qupv3_wrap2_s7_clk_src = {
>
> I think you missed gcc_qupv3_wrap2_s7_clk_src
Nope. The diff header shows it is in gcc_qupv3_wrap2_s7_clk_src_init
which is assigned to the gcc_qupv3_wrap2_s7_clk_src clk's hw.init
pointer.
.clkr.hw.init = &gcc_qupv3_wrap2_s7_clk_src_init,
next prev parent reply other threads:[~2024-08-28 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 23:12 [PATCH v2 0/2] clk: qcom: gcc-sm8550: Fix shared clk parking breakage Stephen Boyd
2024-08-27 23:12 ` [PATCH v2 1/2] clk: qcom: dispcc-sc7180: Only park display clks at init Stephen Boyd
2024-08-28 12:22 ` Neil Armstrong
2024-08-28 17:03 ` Stephen Boyd
2024-08-27 23:12 ` [PATCH v2 2/2] clk: qcom: gcc-sm8550: Don't use shared clk_ops for QUPs Stephen Boyd
2024-08-28 12:22 ` Neil Armstrong
2024-08-28 17:13 ` Stephen Boyd [this message]
2024-08-29 8:39 ` Neil Armstrong
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=00adff607d757702fa673942ed60c354.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=patches@lists.linux.dev \
--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