linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lina Iyer <lina.iyer@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: ulf.hansson@linaro.org, khilman@kernel.org, rjw@rjwysocki.net,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	geert@linux-m68k.org, k.kozlowski@samsung.com,
	msivasub@codeaurora.org, agross@codeaurora.org,
	linux-arm-msm@vger.kernel.org, lorenzo.pieralisi@arm.com,
	ahaslam@baylibre.com, mtitinger@baylibre.com,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [RFC v2 03/12] PM / cpu_domains: Setup PM domains for CPUs/clusters
Date: Tue, 1 Mar 2016 11:00:10 -0700	[thread overview]
Message-ID: <20160301180010.GK1440@linaro.org> (raw)
In-Reply-To: <20160226191016.GW28849@codeaurora.org>

On Fri, Feb 26 2016 at 12:10 -0700, Stephen Boyd wrote:
>On 02/12, Lina Iyer wrote:
>> diff --git a/drivers/base/power/cpu_domains.c b/drivers/base/power/cpu_domains.c
>> new file mode 100644
>> index 0000000..981592f
>> --- /dev/null
>> +++ b/drivers/base/power/cpu_domains.c
>> @@ -0,0 +1,267 @@
>> +
>> +/* List of CPU PM domains we care about */
>> +static LIST_HEAD(of_cpu_pd_list);
>> +static DEFINE_SPINLOCK(cpu_pd_list_lock);
>
>Can this be a mutex?
>
Yes, will change. The init function would not be called from atomic context.

>> +	genpd = kzalloc(sizeof(*(genpd)), GFP_KERNEL);
>
>Drop extra parenthesis
>

>> +	/* Register the CPU genpd */
>> +	pr_debug("adding %s as CPU PM domain.\n", pd->genpd->name);
>
>Drop the full stop?
>
OK

>> +	kfree(genpd);
>> +	kfree(genpd->name);
>
>Switch order so that name is freed first to avoid junk deref here.
>
Sounds good.

>> +	kfree(pd);
>> +	return ERR_PTR(ret);
>> +}
>> +
>> +static struct generic_pm_domain *of_get_cpu_domain(struct device_node *dn,
>> +		const struct cpu_pd_ops *ops, int cpu)
>> +{

>> +	genpd = of_genpd_get_from_provider(&args);
>> +	if (!IS_ERR(genpd))
>> +		goto skip_parent;
>
>Why not just return genpd and drop the goto?
>
Ok

>> +	genpd = of_init_cpu_pm_domain(dn, ops);
>> +	if (IS_ERR(genpd))
>> +		return genpd;
>> +
>> +	/* Is there a domain provider for this domain? */
>> +	ret = of_parse_phandle_with_args(dn, "power-domains",
>> +			"#power-domain-cells", 0, &args);
>> +	of_node_put(dn);
>
>Shouldn't this be of_node_put(args.np)? I suppose it's the same
>so this isn't too important.
>
>> +	if (ret < 0)
>> +		goto skip_parent;
>> +
>> +	/* Find its parent and attach this domain to it, recursively */
>> +	parent = of_get_cpu_domain(args.np, ops, cpu);
>
>Except that we use the np here. So perhaps move the of_node_put()
>down to the skip_parent goto?
>
Ok

>> +	if (IS_ERR(parent)) {
>> +		struct cpu_pm_domain *cpu_pd, *parent_cpu_pd;
>> +
>> +		ret = pm_genpd_add_subdomain(genpd, parent);
>
>parent is an error pointer here... isn't this always going to
>fail? Maybe that should be if (!IS_ERR(parent)) up there?
>
Good catch. Yes, it should be.

>> +		/*
>> +		 * Reference parent domain for easy access.
>> +		 * Note: We could be attached to a domain that is not a
>> +		 * CPU PM domain in that case dont reference the parent.
>
>s/dont/don't/
>
Done.

>> +	dn = of_get_cpu_node(cpu, NULL);
>> +	if (!dn)
>> +		return -ENODEV;
>> +
>> +	dn = of_parse_phandle(dn, "power-domains", 0);
>> +	if (!dn)
>> +		return -ENODEV;
>> +	of_node_put(dn);
>
>This should be put after of_get_cpu_domain().
>
Thanks for this review, Stephen.

Thanks,
Lina

>> +
>> +	/* Find the genpd for this CPU, create if not found */
>> +	genpd = of_get_cpu_domain(dn, ops, cpu);
>> +	if (IS_ERR(genpd))
>> +		return PTR_ERR(genpd);
>> +
>> +	return cpu_pd_attach_cpu(cpu);
>> +}
>> +EXPORT_SYMBOL(of_setup_cpu_pd_single);
>
>-- 
>Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>a Linux Foundation Collaborative Project

  reply	other threads:[~2016-03-01 18:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 20:50 [RFC v2 00/12] PM: SoC idle support using PM domains Lina Iyer
2016-02-12 20:50 ` [RFC v2 01/12] PM / Domains: Abstract genpd locking Lina Iyer
2016-02-26 18:08   ` Stephen Boyd
2016-03-01 16:55     ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 02/12] PM / Domains: Support IRQ safe PM domains Lina Iyer
2016-02-26 18:17   ` Stephen Boyd
2016-03-01 17:44     ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 03/12] PM / cpu_domains: Setup PM domains for CPUs/clusters Lina Iyer
2016-02-17 23:38   ` Lina Iyer
2016-02-18 17:29   ` [BUG FIX] PM / cpu_domains: Check for NULL callbacks Lina Iyer
2016-02-18 17:46     ` Rafael J. Wysocki
2016-02-18 22:51       ` Lina Iyer
2016-02-26 19:10   ` [RFC v2 03/12] PM / cpu_domains: Setup PM domains for CPUs/clusters Stephen Boyd
2016-03-01 18:00     ` Lina Iyer [this message]
2016-02-12 20:50 ` [RFC v2 04/12] ARM: cpuidle: Add runtime PM support for CPUs Lina Iyer
2016-02-26 18:24   ` Stephen Boyd
2016-03-01 18:36     ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 05/12] timer: Export next wake up of a CPU Lina Iyer
2016-02-12 20:50 ` [RFC v2 06/12] PM / cpu_domains: Record CPUs that are part of the domain Lina Iyer
2016-02-26 19:20   ` Stephen Boyd
2016-03-01 19:24     ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 07/12] PM / cpu_domains: Add PM Domain governor for CPUs Lina Iyer
2016-02-26 19:33   ` Stephen Boyd
2016-03-01 19:32     ` Lina Iyer
2016-03-01 19:35       ` Stephen Boyd
2016-02-12 20:50 ` [RFC v2 08/12] Documentation / cpu_domains: Describe CPU PM domains setup and governor Lina Iyer
2016-02-26 19:43   ` Stephen Boyd
2016-03-01 19:36     ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 09/12] drivers: firmware: psci: Allow OS Initiated suspend mode Lina Iyer
2016-02-12 20:50 ` [RFC v2 10/12] ARM64: psci: Support cluster idle states for OS-Initiated Lina Iyer
2016-02-12 20:50 ` [RFC v2 11/12] ARM64: dts: Add PSCI cpuidle support for MSM8916 Lina Iyer
2016-02-12 20:50 ` [RFC v2 12/12] ARM64: dts: Define CPU power domain " Lina Iyer
2016-02-26 19:50   ` Stephen Boyd
2016-03-01 19:41     ` Lina Iyer

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=20160301180010.GK1440@linaro.org \
    --to=lina.iyer@linaro.org \
    --cc=agross@codeaurora.org \
    --cc=ahaslam@baylibre.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=geert@linux-m68k.org \
    --cc=k.kozlowski@samsung.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=msivasub@codeaurora.org \
    --cc=mtitinger@baylibre.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --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).