From: Michael Ellerman <mpe@ellerman.id.au>
To: Preeti U Murthy <preeti@linux.vnet.ibm.com>, rafael.j.wysocki@intel.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: cpuidle/powernv: Read target_residency value of idle states from DT if available
Date: Fri, 23 Jan 2015 15:59:06 +1100 (AEDT) [thread overview]
Message-ID: <20150123045906.D0086140297@ozlabs.org> (raw)
In-Reply-To: <54BE3B79.9070004@linux.vnet.ibm.com>
On Tue, 2015-20-01 at 11:26:49 UTC, Preeti U Murthy wrote:
> @@ -177,34 +178,39 @@ static int powernv_add_idle_states(void)
> return nr_idle_states;
> }
>
> - idle_state_latency = of_get_property(power_mgt,
> - "ibm,cpu-idle-state-latencies-ns", NULL);
> - if (!idle_state_latency) {
> + dt_idle_states = len_flags / sizeof(u32);
> +
> + latency_ns = kzalloc(sizeof(*latency_ns) * dt_idle_states, GFP_KERNEL);
> + rc = of_property_read_u32(power_mgt,
> + "ibm,cpu-idle-state-latencies-ns", latency_ns);
That's only reading the first value.
If you want to read the full property you need the _array version.
> + if (rc) {
> pr_warn("DT-PowerMgmt: missing ibm,cpu-idle-state-latencies-ns\n");
You missed my hint that "DT-PowerMgmt" is a weird and ugly prefix. Can you use
"cpuidle-powernv:" instead?
>
> - dt_idle_states = len_flags / sizeof(u32);
> + residency_ns = kzalloc(sizeof(*residency_ns) * dt_idle_states, GFP_KERNEL);
> + rc = of_property_read_u32(power_mgt,
> + "ibm,cpu-idle-state-residency-ns", residency_ns);
> + if (rc) {
> + pr_warn("DT-PowerMgmt: missing ibm,cpu-idle-state-residency-ns\n");
> + pr_warn("Falling back to default values\n");
I don't think this is worth a warning seeing as we know there are firmwares out
there which do not have the property.
> for (i = 0; i < dt_idle_states; i++) {
>
> flags = be32_to_cpu(idle_state_flags[i]);
> -
> - /* Cpuidle accepts exit_latency in us and we estimate
> - * target residency to be 10x exit_latency
> + /*
> + * Cpuidle accepts exit_latency and target_residency in us.
> + * Use default target_residency values if f/w does not expose it.
> */
> - latency_ns = be32_to_cpu(idle_state_latency[i]);
> if (flags & OPAL_PM_NAP_ENABLED) {
> /* Add NAP state */
> strcpy(powernv_states[nr_idle_states].name, "Nap");
> strcpy(powernv_states[nr_idle_states].desc, "Nap");
> powernv_states[nr_idle_states].flags = 0;
> - powernv_states[nr_idle_states].exit_latency =
> - ((unsigned int)latency_ns) / 1000;
> - powernv_states[nr_idle_states].target_residency =
> - ((unsigned int)latency_ns / 100);
> + powernv_states[nr_idle_states].target_residency = 100;
> powernv_states[nr_idle_states].enter = &nap_loop;
> - nr_idle_states++;
That looks wrong? Or do you mean to do that?
cheers
next prev parent reply other threads:[~2015-01-23 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 11:32 [PATCH] cpuidle/powernv: Read target_residency value of idle states from DT if available Preeti U Murthy
2015-01-20 5:45 ` Michael Ellerman
2015-01-20 11:26 ` Preeti U Murthy
2015-01-20 11:52 ` PowerMac G5 Quad Issue reporting luigi burdo
2015-01-21 6:39 ` Michel Dänzer
2015-01-21 8:13 ` luigi burdo
2015-01-23 4:59 ` Michael Ellerman [this message]
2015-01-27 4:02 ` cpuidle/powernv: Read target_residency value of idle states from DT if available Preeti U Murthy
2015-01-27 6:28 ` Michael Ellerman
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=20150123045906.D0086140297@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
/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).