public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Stephen Boyd <sboyd@kernel.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 2/2] clk: qcom: mmcc-msm8974: fix MDSS_GDSC power flags
Date: Thu, 11 May 2023 13:45:04 +0530	[thread overview]
Message-ID: <20230511081504.GA12021@thinkpad> (raw)
In-Reply-To: <CAA8EJpoJr6gK=7fmwmF4+Xi5Ch_-+8L1q1WHkfVOOg+6qj=P3w@mail.gmail.com>

On Tue, May 09, 2023 at 02:20:07PM +0300, Dmitry Baryshkov wrote:
> On Tue, 9 May 2023 at 08:50, Manivannan Sadhasivam
> <manivannan.sadhasivam@linaro.org> wrote:
> >
> > On Sun, May 07, 2023 at 08:53:35PM +0300, Dmitry Baryshkov wrote:
> > > Using PWRSTS_RET on msm8974's MDSS_GDSC causes display to stop working.
> > > The gdsc doesn't fully come out of retention mode. Change it's pwrsts
> > > flags to PWRSTS_OFF_ON.
> > >
> >
> > What does "stop working" implies? Does it work during boot and randomly stopped
> > working or it stopped working after resume from suspend?
> 
> It stops working during the boot. I observed the MDP not starting up
> properly. Mea culpa, I did not look deep enough into the details, just
> stomped upon this change which fixes the problem for me.
> 

IIUC, GDSC will be transitioned to retention mode only if the parent domain goes
to low power mode. So if the MDSS GDSC goes to retention mode during boot, then
it suggests that the parent domain is not voted properly. Unless I misunderstood
something...

Or is the GDSC behavior changes between RPM and RPMh?

- Mani

> >
> > Even though reverting to non-retention mode works, I think the issue might be
> > somewhere else. Like the vote might be missing to get the GDSC out of retention
> > mode.
> 
> I don't think there is a vote missing. The driver votes on MDSS_GDSC
> before enabling access to any of the registers from the MDSS region.
> 
> >
> > - Mani
> >
> > > Fixes: d399723950c4 ("clk: qcom: gdsc: Fix the handling of PWRSTS_RET support")
> > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > > ---
> > >  drivers/clk/qcom/mmcc-msm8974.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/clk/qcom/mmcc-msm8974.c b/drivers/clk/qcom/mmcc-msm8974.c
> > > index aa29c79fcd55..277ef0065aae 100644
> > > --- a/drivers/clk/qcom/mmcc-msm8974.c
> > > +++ b/drivers/clk/qcom/mmcc-msm8974.c
> > > @@ -2401,7 +2401,7 @@ static struct gdsc mdss_gdsc = {
> > >       .pd = {
> > >               .name = "mdss",
> > >       },
> > > -     .pwrsts = PWRSTS_RET_ON,
> > > +     .pwrsts = PWRSTS_OFF_ON,
> > >  };
> > >
> > >  static struct gdsc camss_jpeg_gdsc = {
> > > --
> > > 2.39.2
> > >
> >
> > --
> > மணிவண்ணன் சதாசிவம்
> 
> 
> 
> -- 
> With best wishes
> Dmitry

-- 
மணிவண்ணன் சதாசிவம்

  reply	other threads:[~2023-05-11  8:15 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 [this message]
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

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=20230511081504.GA12021@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@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