From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Rajendra Nayak <rnayak@codeaurora.org>,
sboyd@kernel.org, mturquette@baylibre.com
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
stanimir.varbanov@linaro.org, vivek.gautam@codeaurora.org
Subject: Re: [PATCH v2 1/3] clk: qcom: gdsc: Add support for ALWAYS_ON gdscs
Date: Fri, 25 May 2018 19:20:41 +0100 [thread overview]
Message-ID: <d0f36b0e-852d-c0b7-53f8-ac5ad9d34d9e@linaro.org> (raw)
In-Reply-To: <20180323082616.10142-2-rnayak@codeaurora.org>
On 23/03/18 08:26, Rajendra Nayak wrote:
> Some GDSCs might have software control to turn them off, but we might
> want to keep them enabled always, in some cases because of lack of
> support in kernel to handle a graceful turning off/on of such GDSCs.
> Most common instances would be the GDCSs which power up the noc/bus
> fabrics, which need bus drivers to handle them and atleast support for
> which is missing on all qcom SoCs.
>
> Signed-off-by: Rajendra Nayak<rnayak@codeaurora.org>
Tested-by: Srinivas Kandagatla<srinivas.kandagatla@linaro.org>
next prev parent reply other threads:[~2018-05-25 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 8:26 [PATCH v2 0/3] clk: qcom: msm8996: handle mmagic gdscs and clocks Rajendra Nayak
2018-03-23 8:26 ` [PATCH v2 1/3] clk: qcom: gdsc: Add support for ALWAYS_ON gdscs Rajendra Nayak
2018-05-25 18:18 ` Bjorn Andersson
2018-05-25 18:20 ` Srinivas Kandagatla [this message]
2018-06-01 18:05 ` Stephen Boyd
2018-03-23 8:26 ` [PATCH v2 2/3] clk: qcom: Register the gdscs before the clocks Rajendra Nayak
2018-05-25 18:18 ` Bjorn Andersson
2018-05-25 18:20 ` Srinivas Kandagatla
2018-06-01 18:06 ` Stephen Boyd
2018-03-23 8:26 ` [PATCH v2 3/3] clk: qcom: mmcc-msm8996: leave all mmagic gdscs and clocks always enabled Rajendra Nayak
2018-05-25 18:23 ` Bjorn Andersson
2018-06-01 18:06 ` Stephen Boyd
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=d0f36b0e-852d-c0b7-53f8-ac5ad9d34d9e@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=stanimir.varbanov@linaro.org \
--cc=vivek.gautam@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).