From: Rajendra Nayak <rnayak@codeaurora.org>
To: Douglas Anderson <dianders@chromium.org>,
Andy Gross <andy.gross@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
linux-arm-msm@vger.kernel.org,
David Brown <david.brown@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: rpmhpd: Set 'active_only' for active only power domains
Date: Fri, 15 Feb 2019 08:02:40 +0530 [thread overview]
Message-ID: <69c46e02-f6b7-c6b3-5dc1-8c9ecd88b14d@codeaurora.org> (raw)
In-Reply-To: <20190214173633.211000-1-dianders@chromium.org>
On 2/14/2019 11:06 PM, Douglas Anderson wrote:
> The 'active_only' attribute was accidentally never set to true for any
> power domains meaning that all the code handling this attribute was
> dead.
>
> NOTE that the RPM power domain code (as opposed to the RPMh one) gets
> this right.
>
> Fixes: 279b7e8a62cc ("soc: qcom: rpmhpd: Add RPMh power domain driver")
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
Thanks for catching this. I seem to have introduced this bug when I moved
away from using the macros to define these static structs and failed to add
the property :/
Acked-by: Rajendra Nayak <rnayak@codeaurora.org>
> ---
>
> drivers/soc/qcom/rpmhpd.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/soc/qcom/rpmhpd.c b/drivers/soc/qcom/rpmhpd.c
> index 5741ec3fa814..51850cc68b70 100644
> --- a/drivers/soc/qcom/rpmhpd.c
> +++ b/drivers/soc/qcom/rpmhpd.c
> @@ -93,6 +93,7 @@ static struct rpmhpd sdm845_mx = {
>
> static struct rpmhpd sdm845_mx_ao = {
> .pd = { .name = "mx_ao", },
> + .active_only = true,
> .peer = &sdm845_mx,
> .res_name = "mx.lvl",
> };
> @@ -107,6 +108,7 @@ static struct rpmhpd sdm845_cx = {
>
> static struct rpmhpd sdm845_cx_ao = {
> .pd = { .name = "cx_ao", },
> + .active_only = true,
> .peer = &sdm845_cx,
> .parent = &sdm845_mx_ao.pd,
> .res_name = "cx.lvl",
>
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2019-02-15 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 17:36 Douglas Anderson
2019-02-14 18:23 ` Stephen Boyd
2019-02-15 2:32 ` Rajendra Nayak [this message]
2019-11-18 16:19 ` Doug Anderson
2019-11-20 1:36 ` 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=69c46e02-f6b7-c6b3-5dc1-8c9ecd88b14d@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®