From: Abel Vesa <abel.vesa@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>, avel Machek <pavel@ucw.cz>,
Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Taniya Das <tdas@qti.qualcomm.com>,
linux-pm@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] clk: qcom: gdsc: Add support for set_hwmode_dev
Date: Tue, 27 Jun 2023 14:38:23 +0300 [thread overview]
Message-ID: <ZJrKL5+JHzOgHQl5@linaro.org> (raw)
In-Reply-To: <666f7313-f0a2-6a94-f591-eb354df083dd@linaro.org>
On 23-06-27 12:47:24, Konrad Dybcio wrote:
> On 27.06.2023 12:40, Abel Vesa wrote:
> > Implement the GDSC specific genpd set_hwmode_dev callback in order to
> > switch the HW control on or off. For any GDSC that supports HW control
> > set this callback in order to allow its consumers to control it.
> >
> > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > ---
> Currently all GDSCs with flags & HW_CTRL enable hw ctrl mode implicilty.
> I didn't get any cover letter with these patches.. are you planning on
> retiring that behavior? Presumably after adding a matching pair of set_hwmode
> in venus!
I didn't think a cover letter was needed here. After a chat offline with
Taniya about this and it seems there is at least one consumer driver
that needs to switch back and forth the HW control bit. For the rest of
the consumers, the safest way is to assume that they expect their GDSC
to be in HW control mode from the moment it is enabled until it gets
disabled. One example of this is venus.
>
> fwiw this patch lgtm
>
> Konrad
> > drivers/clk/qcom/gdsc.c | 22 ++++++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> >
> > diff --git a/drivers/clk/qcom/gdsc.c b/drivers/clk/qcom/gdsc.c
> > index 5358e28122ab..9a04bf2e4379 100644
> > --- a/drivers/clk/qcom/gdsc.c
> > +++ b/drivers/clk/qcom/gdsc.c
> > @@ -314,6 +314,26 @@ static int gdsc_enable(struct generic_pm_domain *domain)
> > return 0;
> > }
> >
> > +static int gdsc_set_hwmode_dev(struct generic_pm_domain *domain,
> > + struct device *dev, bool enable)
> > +{
> > + int ret = gdsc_hwctrl(domain_to_gdsc(domain), enable);
> > +
> > + if (ret)
> > + goto out;
> > +
> > + /*
> > + * Wait for the GDSC to go through a power down and
> > + * up cycle. In case there is a status polling going on
> > + * before the power cycle is completed it might read an
> > + * wrong status value.
> > + */
> > + udelay(1);
> > +
> > +out:
> > + return ret;
> > +}
> > +
> > static int gdsc_disable(struct generic_pm_domain *domain)
> > {
> > struct gdsc *sc = domain_to_gdsc(domain);
> > @@ -451,6 +471,8 @@ static int gdsc_init(struct gdsc *sc)
> > sc->pd.power_off = gdsc_disable;
> > if (!sc->pd.power_on)
> > sc->pd.power_on = gdsc_enable;
> > + if (sc->flags & HW_CTRL)
> > + sc->pd.set_hwmode_dev = gdsc_set_hwmode_dev;
> >
> > ret = pm_genpd_init(&sc->pd, NULL, !on);
> > if (ret)
next prev parent reply other threads:[~2023-06-27 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 10:40 [RFC PATCH 1/2] PM: domains: Allow devices attached to genpd to be managed by HW Abel Vesa
2023-06-27 10:40 ` [RFC PATCH 2/2] clk: qcom: gdsc: Add support for set_hwmode_dev Abel Vesa
2023-06-27 10:47 ` Konrad Dybcio
2023-06-27 11:38 ` Abel Vesa [this message]
2023-06-27 10:46 ` [RFC PATCH 1/2] PM: domains: Allow devices attached to genpd to be managed by HW Greg Kroah-Hartman
2023-06-27 10:54 ` Abel Vesa
2023-06-27 11:02 ` Greg Kroah-Hartman
2023-06-27 11:48 ` Abel Vesa
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=ZJrKL5+JHzOgHQl5@linaro.org \
--to=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=tdas@qti.qualcomm.com \
--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