public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
	nm@ti.com, sboyd@kernel.org, linux-pm@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] OPP: Fix handling of multiple power domains
Date: Tue, 12 Mar 2019 10:36:06 +0100	[thread overview]
Message-ID: <1695972.KL8iO62iuq@aspire.rjw.lan> (raw)
In-Reply-To: <20190308043712.3aca6lygz2oya3lc@vireshk-i7>

On Friday, March 8, 2019 5:37:12 AM CET Viresh Kumar wrote:
> On 06-03-19, 09:37, Rajendra Nayak wrote:
> > We seem to rely on the number of phandles specified in the
> > 'required-opps' property to identify cases where a device is
> > associated with multiple power domains and hence would have
> > multiple virtual devices that have to be dealt with.
> > 
> > In cases where we do have devices with multiple power domains
> > but with only one of them being scalable, this logic seems to
> > fail.
> > 
> > Instead read the number of power domains from DT to identify
> > such cases.
> > 
> > Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> > ---
> >  drivers/opp/of.c | 16 ++++++++++++++--
> >  1 file changed, 14 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/opp/of.c b/drivers/opp/of.c
> > index 06f0f632ec47..443c305ae100 100644
> > --- a/drivers/opp/of.c
> > +++ b/drivers/opp/of.c
> > @@ -172,7 +172,7 @@ static void _opp_table_alloc_required_tables(struct opp_table *opp_table,
> >  	struct opp_table **required_opp_tables;
> >  	struct device **genpd_virt_devs = NULL;
> >  	struct device_node *required_np, *np;
> > -	int count, i;
> > +	int count, count_pd, i;
> >  
> >  	/* Traversing the first OPP node is all we need */
> >  	np = of_get_next_available_child(opp_np, NULL);
> > @@ -185,7 +185,19 @@ static void _opp_table_alloc_required_tables(struct opp_table *opp_table,
> >  	if (!count)
> >  		goto put_np;
> >  
> > -	if (count > 1) {
> > +	/*
> > +	 * Check the number of power-domains to know if we need to deal
> > +	 * with virtual devices. In some cases we have devices with multiple
> > +	 * power domains but with only one of them being scalable, hence
> > +	 * 'count' could be 1, but we still have to deal with multiple genpds
> > +	 * and virtual devices.
> > +	 */
> > +	count_pd = of_count_phandle_with_args(dev->of_node, "power-domains",
> > +					      "#power-domain-cells");
> > +	if (!count_pd)
> > +		goto put_np;
> > +
> > +	if (count_pd > 1) {
> >  		genpd_virt_devs = kcalloc(count, sizeof(*genpd_virt_devs),
> >  					GFP_KERNEL);
> >  		if (!genpd_virt_devs)
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> 
> @Rafael, please pick this up for 5.1-rc2 directly. Thanks.

Done, thanks!

      reply	other threads:[~2019-03-12  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  4:07 [PATCH] OPP: Fix handling of multiple power domains Rajendra Nayak
2019-03-06 18:02 ` Stephen Boyd
2019-03-08  4:37 ` Viresh Kumar
2019-03-12  9:36   ` Rafael J. Wysocki [this message]

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=1695972.KL8iO62iuq@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rnayak@codeaurora.org \
    --cc=sboyd@kernel.org \
    --cc=viresh.kumar@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