From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Taniya Das <quic_tdas@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: (subset) [PATCH 1/2] clk: qcom: mmcc-msm8974: use clk_rcg2_shared_ops for mdp_clk_src clock
Date: Tue, 20 Jun 2023 13:03:36 -0700 [thread overview]
Message-ID: <168729141436.721186.9010041163444104014.b4-ty@kernel.org> (raw)
In-Reply-To: <20230507175335.2321503-1-dmitry.baryshkov@linaro.org>
On Sun, 07 May 2023 20:53:34 +0300, Dmitry Baryshkov wrote:
> The mdp_clk_src clock should not be turned off. Instead it should be
> 'parked' to the XO, as most of other mdp_clk_src clocks. Fix that by
> using the clk_rcg2_shared_ops.
>
>
Applied, thanks!
[2/2] clk: qcom: mmcc-msm8974: fix MDSS_GDSC power flags
commit: 4e13c7a55cf752887f2b8d8008711dbbc64ea796
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-06-20 20:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 17:53 [PATCH 1/2] clk: qcom: mmcc-msm8974: use clk_rcg2_shared_ops for mdp_clk_src clock Dmitry Baryshkov
2023-05-07 17:53 ` [PATCH 2/2] clk: qcom: mmcc-msm8974: fix MDSS_GDSC power flags Dmitry Baryshkov
2023-05-08 8:27 ` Konrad Dybcio
2023-05-08 11:36 ` Dmitry Baryshkov
2023-05-08 20:47 ` Luca Weiss
2023-05-09 5:35 ` Rajendra Nayak
2023-05-09 5:50 ` Manivannan Sadhasivam
2023-05-09 11:20 ` Dmitry Baryshkov
2023-05-11 8:15 ` Manivannan Sadhasivam
2023-05-29 23:47 ` Dmitry Baryshkov
2023-06-14 6:05 ` Dmitry Baryshkov
2023-06-14 10:19 ` Konrad Dybcio
2023-05-08 7:55 ` [PATCH 1/2] clk: qcom: mmcc-msm8974: use clk_rcg2_shared_ops for mdp_clk_src clock Konrad Dybcio
2023-05-08 15:03 ` Dmitry Baryshkov
2023-05-08 20:45 ` Luca Weiss
2023-05-27 1:07 ` (subset) " Bjorn Andersson
2023-06-20 20:03 ` 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=168729141436.721186.9010041163444104014.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