From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Taniya Das <quic_tdas@quicinc.com>
Cc: linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH v2 1/2] clk: qcom: gpucc-sc7180: fix clk_dis_wait being programmed for CX GDSC
Date: Wed, 8 Feb 2023 20:22:51 -0800 [thread overview]
Message-ID: <167591660370.1230100.9603650327967651533.b4-ty@kernel.org> (raw)
In-Reply-To: <20230201172305.993146-1-dmitry.baryshkov@linaro.org>
On Wed, 1 Feb 2023 19:23:04 +0200, Dmitry Baryshkov wrote:
> The gdsc_init() function will rewrite the CLK_DIS_WAIT field while
> registering the GDSC (writing the value 0x2 by default). This will
> override the setting done in the driver's probe function.
>
> Set cx_gdsc.clk_dis_wait_val to 8 to follow the intention of the probe
> function.
>
> [...]
Applied, thanks!
[1/2] clk: qcom: gpucc-sc7180: fix clk_dis_wait being programmed for CX GDSC
commit: 658c82caffa042b351f5a1b6325819297a951a04
[2/2] clk: qcom: gpucc-sdm845: fix clk_dis_wait being programmed for CX GDSC
commit: cb81719e3c1165ef1bc33137dc628f750eed8ea4
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-02-09 4:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 17:23 [PATCH v2 1/2] clk: qcom: gpucc-sc7180: fix clk_dis_wait being programmed for CX GDSC Dmitry Baryshkov
2023-02-01 17:23 ` [PATCH v2 2/2] clk: qcom: gpucc-sdm845: " Dmitry Baryshkov
2023-02-01 18:27 ` Konrad Dybcio
2023-02-01 18:26 ` [PATCH v2 1/2] clk: qcom: gpucc-sc7180: " Konrad Dybcio
2023-02-09 4:22 ` 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=167591660370.1230100.9603650327967651533.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@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=sboyd@kernel.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