From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Sricharan R <sricharan@codeaurora.org>,
sboyd@codeaurora.org, mturquette@baylibre.com,
linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, rnayak@codeaurora.org,
stanimir.varbanov@linaro.org
Subject: Re: [PATCH 1/3] clk: qcom: gdsc: Add support for gdscs with HW control
Date: Tue, 25 Oct 2016 16:01:07 +0300 [thread overview]
Message-ID: <e7fe9301-e7ae-1ad3-571c-f5988c5970be@linaro.org> (raw)
In-Reply-To: <1477304297-5248-2-git-send-email-sricharan@codeaurora.org>
Hi Sricharan,
On 10/24/2016 01:18 PM, Sricharan R wrote:
> From: Rajendra Nayak <rnayak@codeaurora.org>
>
> Some GDSCs might support a HW control mode, where in the power
> domain (gdsc) is brought in and out of low power state (while
> unsued) without any SW assistance, saving power.
> Such GDSCs can be configured in a HW control mode when powered on
> until they are explicitly requested to be powered off by software.
>
> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
> ---
> drivers/clk/qcom/gdsc.c | 15 +++++++++++++++
> drivers/clk/qcom/gdsc.h | 1 +
> 2 files changed, 16 insertions(+)
>
> diff --git a/drivers/clk/qcom/gdsc.c b/drivers/clk/qcom/gdsc.c
> index f12d7b2..a5e1c8c 100644
> --- a/drivers/clk/qcom/gdsc.c
> +++ b/drivers/clk/qcom/gdsc.c
> @@ -55,6 +55,13 @@ static int gdsc_is_enabled(struct gdsc *sc, unsigned int reg)
> return !!(val & PWR_ON_MASK);
> }
>
> +static int gdsc_hwctrl(struct gdsc *sc, bool en)
> +{
> + u32 val = en ? HW_CONTROL_MASK : 0;
> +
> + return regmap_update_bits(sc->regmap, sc->gdscr, HW_CONTROL_MASK, val);
> +}
> +
> static int gdsc_toggle_logic(struct gdsc *sc, bool en)
> {
> int ret;
> @@ -164,6 +171,10 @@ static int gdsc_enable(struct generic_pm_domain *domain)
> */
> udelay(1);
>
> + /* Turn on HW trigger mode if supported */
> + if (sc->flags & HW_CTRL)
> + gdsc_hwctrl(sc, true);
Could you check gdsc_hwctrl() for an error.
<cut>
--
regards,
Stan
next prev parent reply other threads:[~2016-10-25 13:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 10:18 [PATCH 0/3] clk: qcom: Add support for hw controlled gdscs/clocks Sricharan R
2016-10-24 10:18 ` [PATCH 1/3] clk: qcom: gdsc: Add support for gdscs with HW control Sricharan R
2016-10-25 13:01 ` Stanimir Varbanov [this message]
2016-10-26 4:12 ` Sricharan
2016-11-02 0:18 ` Stephen Boyd
2016-11-02 6:50 ` Sricharan
2016-11-02 6:53 ` Sricharan
2016-11-02 17:59 ` 'Stephen Boyd'
2016-11-03 13:30 ` Sricharan
2016-11-03 20:05 ` 'Stephen Boyd'
2016-10-24 10:18 ` [PATCH 2/3] clk: qcom: Put venus core0/1 gdscs to hw control mode Sricharan R
2016-10-24 10:18 ` [PATCH 3/3] clk: qcom: Set BRANCH_HALT_DELAY flags for venus core0/1 clks Sricharan R
2016-11-03 20:34 ` Stephen Boyd
2016-11-04 9:09 ` Sricharan
2016-11-04 20:18 ` 'Stephen Boyd'
2016-11-07 5:48 ` Rajendra Nayak
2016-11-08 22:33 ` 'Stephen Boyd'
2016-11-09 16:56 ` Sricharan
2016-11-10 2:32 ` Rajendra Nayak
2016-11-10 3:28 ` Sricharan
2016-11-10 23:30 ` 'Stephen Boyd'
2016-11-14 3:51 ` Sricharan
2016-12-12 15:40 ` Stanimir Varbanov
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=e7fe9301-e7ae-1ad3-571c-f5988c5970be@linaro.org \
--to=stanimir.varbanov@linaro.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=rnayak@codeaurora.org \
--cc=sboyd@codeaurora.org \
--cc=sricharan@codeaurora.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).