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>, Pavel 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,
Jagadeesh Kona <quic_jkona@quicinc.com>
Subject: Re: [PATCH v2 4/6] clk: qcom: Use HW_CTRL_TRIGGER flag to switch video GDSC to HW mode
Date: Wed, 23 Aug 2023 13:41:23 +0300 [thread overview]
Message-ID: <ZOXiUzxfs1cj3SWT@linaro.org> (raw)
In-Reply-To: <2fc0d771-cee2-4826-a62a-56ed4bfad3a2@linaro.org>
On 23-08-16 19:56:46, Konrad Dybcio wrote:
> On 16.08.2023 16:57, Abel Vesa wrote:
> > From: Jagadeesh Kona <quic_jkona@quicinc.com>
> >
> > The current HW_CTRL flag switches the video GDSC to HW control mode as
> > part of GDSC enable itself, instead of that use HW_CTRL_TRIGGER flag to
> > give consumer drivers more control and switch the GDSC mode as and when
> > required.
> >
> > HW_CTRL_TRIGGER flag allows consumer drivers to switch the video GDSC to
> > HW/SW control modes at runtime using dev_pm_genpd_set_hwmode API.
> >
> > Signed-off-by: Jagadeesh Kona <quic_jkona@quicinc.com>
> > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > ---
> Do we have any use for the HW_CTRL flag?
>
> Perhaps it should be renamed to HW_CTRL_ALWAYS?
>
> Or even better, *if and only if* that is necessary, add a common
> property like "always_hw_managed" to the genpd code?
The HW_CTRL flag is still needed for the consumers that expect the GDSC
to be have the HW control bit set right after it gets enabled.
AFAIU, for the HW_CTRL_TRIGGER, the switch to HW control will only be
done by the consumer (not on enable).
>
> Konrad
next prev parent reply other threads:[~2023-08-23 10:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 14:57 [PATCH v2 0/6] PM: domains: Add control for switching back and forth to HW control Abel Vesa
2023-08-16 14:57 ` [PATCH v2 1/6] PM: domains: Allow devices attached to genpd to be managed by HW Abel Vesa
2023-08-16 14:57 ` [PATCH v2 2/6] PM: domains: Add the domain HW-managed mode to the summary Abel Vesa
2023-08-16 17:54 ` Konrad Dybcio
2023-08-17 9:46 ` Ulf Hansson
2023-08-16 14:57 ` [PATCH v2 3/6] clk: qcom: gdsc: Add set and get hwmode callbacks to switch GDSC mode Abel Vesa
2023-08-16 17:55 ` Konrad Dybcio
2023-08-16 14:57 ` [PATCH v2 4/6] clk: qcom: Use HW_CTRL_TRIGGER flag to switch video GDSC to HW mode Abel Vesa
2023-08-16 17:56 ` Konrad Dybcio
2023-08-23 10:41 ` Abel Vesa [this message]
2023-08-26 10:47 ` Konrad Dybcio
2023-08-28 6:48 ` Jagadeesh Kona
2023-08-28 7:30 ` Abel Vesa
2023-09-02 11:59 ` Konrad Dybcio
2023-09-02 12:03 ` Konrad Dybcio
2023-09-04 9:27 ` Jagadeesh Kona
2023-09-04 16:02 ` Konrad Dybcio
2023-09-07 5:55 ` Jagadeesh Kona
2023-09-07 7:36 ` Konrad Dybcio
2023-09-11 12:47 ` Jagadeesh Kona
2023-08-16 14:57 ` [PATCH v2 5/6] clk: qcom: videocc-sm8550: Use HW_CTRL_TRIGGER instead of HW_CTRL for GDSC Abel Vesa
2023-08-16 17:57 ` Konrad Dybcio
2023-08-16 14:57 ` [PATCH v2 6/6] venus: pm_helpers: Use dev_pm_genpd_set_hwmode to switch GDSC mode Abel Vesa
2023-08-16 17:58 ` Konrad Dybcio
2023-09-02 12:17 ` Konrad Dybcio
2023-08-22 20:15 ` [PATCH v2 0/6] PM: domains: Add control for switching back and forth to HW control Rafael J. Wysocki
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=ZOXiUzxfs1cj3SWT@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=quic_jkona@quicinc.com \
--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;
as well as URLs for NNTP newsgroup(s).