From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Abel Vesa <abel.vesa@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: qcom: Drop mmcx gdsc supply for dispcc and videocc
Date: Sat, 16 Jul 2022 23:21:54 -0500 [thread overview]
Message-ID: <YtOOYryxh9oEJXyg@builder.lan> (raw)
In-Reply-To: <20220713143200.3686765-1-abel.vesa@linaro.org>
On Wed 13 Jul 09:32 CDT 2022, Abel Vesa wrote:
> Both dispcc and videocc use mmcx power domain now.
> Lets drop the supply mmcx from every gdsc.
>
> Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Fixes: 266e5cf39a0f ("arm64: dts: qcom: sm8250: remove mmcx regulator")
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
This would break backwards compatibility with dtbs that used
mmcx-supply. We only ever used mmcx-supply in sm8250.dtsi upstream and
given that we only boot sm8250 off Android boot images it's unlikely
that anyone would use a new kernel with that old of a dtb...
So:
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Dmitry, what do you think?
Regards,
Bjorn
> ---
> drivers/clk/qcom/dispcc-sm8250.c | 1 -
> drivers/clk/qcom/videocc-sm8250.c | 4 ----
> 2 files changed, 5 deletions(-)
>
> diff --git a/drivers/clk/qcom/dispcc-sm8250.c b/drivers/clk/qcom/dispcc-sm8250.c
> index 39b344ebb049..709076f0f9d7 100644
> --- a/drivers/clk/qcom/dispcc-sm8250.c
> +++ b/drivers/clk/qcom/dispcc-sm8250.c
> @@ -1138,7 +1138,6 @@ static struct gdsc mdss_gdsc = {
> },
> .pwrsts = PWRSTS_OFF_ON,
> .flags = HW_CTRL,
> - .supply = "mmcx",
> };
>
> static struct clk_regmap *disp_cc_sm8250_clocks[] = {
> diff --git a/drivers/clk/qcom/videocc-sm8250.c b/drivers/clk/qcom/videocc-sm8250.c
> index 8617454e4a77..f28f2cb051d7 100644
> --- a/drivers/clk/qcom/videocc-sm8250.c
> +++ b/drivers/clk/qcom/videocc-sm8250.c
> @@ -277,7 +277,6 @@ static struct gdsc mvs0c_gdsc = {
> },
> .flags = 0,
> .pwrsts = PWRSTS_OFF_ON,
> - .supply = "mmcx",
> };
>
> static struct gdsc mvs1c_gdsc = {
> @@ -287,7 +286,6 @@ static struct gdsc mvs1c_gdsc = {
> },
> .flags = 0,
> .pwrsts = PWRSTS_OFF_ON,
> - .supply = "mmcx",
> };
>
> static struct gdsc mvs0_gdsc = {
> @@ -297,7 +295,6 @@ static struct gdsc mvs0_gdsc = {
> },
> .flags = HW_CTRL,
> .pwrsts = PWRSTS_OFF_ON,
> - .supply = "mmcx",
> };
>
> static struct gdsc mvs1_gdsc = {
> @@ -307,7 +304,6 @@ static struct gdsc mvs1_gdsc = {
> },
> .flags = HW_CTRL,
> .pwrsts = PWRSTS_OFF_ON,
> - .supply = "mmcx",
> };
>
> static struct clk_regmap *video_cc_sm8250_clocks[] = {
> --
> 2.34.3
>
next prev parent reply other threads:[~2022-07-17 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:32 [PATCH] clk: qcom: Drop mmcx gdsc supply for dispcc and videocc Abel Vesa
2022-07-17 4:21 ` Bjorn Andersson [this message]
2022-07-17 20:11 ` Dmitry Baryshkov
2022-07-19 4:47 ` (subset) " Bjorn Andersson
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=YtOOYryxh9oEJXyg@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.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