From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Preeti U Murthy <preeti@linux.vnet.ibm.com>, mpe@ellerman.id.au
Cc: rafael.j.wysocki@intel.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH V3] cpuidle/powernv: Read target_residency value of idle states from DT if available
Date: Mon, 02 Feb 2015 17:09:17 +1100 [thread overview]
Message-ID: <m3fvaou9o2.fsf@oc8180480414.ibm.com> (raw)
In-Reply-To: <20150202050821.24581.56186.stgit@preeti.in.ibm.com>
Preeti U Murthy <preeti@linux.vnet.ibm.com> writes:
> The device tree now exposes the residency values for different idle states. Read
> these values instead of calculating residency from the latency values. The values
> exposed in the DT are validated for optimal power efficiency. However to maintain
> compatibility with the older firmware code which does not expose residency
> values, use default values as a fallback mechanism. While at it, use better
> APIs to parse the powermgmt device tree node so as to avoid endianness
> transformation.
>
> Signed-off-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>
Same acked-by as before, from perspective of "I merged the firmware side
of things" and things look godo in relation to firmware PoV.
Acked-by: Stewart Smith <stewart@linux.vnet.ibm.com>
next prev parent reply other threads:[~2015-02-02 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 5:10 [PATCH V3] cpuidle/powernv: Read target_residency value of idle states from DT if available Preeti U Murthy
2015-02-02 6:09 ` Stewart Smith [this message]
2015-02-02 6:39 ` Michael Ellerman
2015-02-02 8:55 ` Preeti U Murthy
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=m3fvaou9o2.fsf@oc8180480414.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).