All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
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: [V2] cpuidle/powernv: Read target_residency value of idle states from DT if available
Date: Fri, 30 Jan 2015 14:56:52 +1100 (AEDT)	[thread overview]
Message-ID: <20150130035652.3C252140277@ozlabs.org> (raw)
In-Reply-To: <20150128021044.11166.81418.stgit@preeti.in.ibm.com>

On Wed, 2015-28-01 at 02:13:06 UTC, Preeti U Murthy wrote:
> 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, handle some
> cleanups.
> 
> Signed-off-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>
> Acked-by: Stewart Smith <stewart@linux.vnet.ibm.com>

This looks good to me.

Acked-by: Michael Ellerman <mpe@ellerman.id.au>

I'm assuming Rafael will take it.

cheers

      parent reply	other threads:[~2015-01-30  3:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  2:13 [PATCH V2] cpuidle/powernv: Read target_residency value of idle states from DT if available Preeti U Murthy
2015-01-28  2:13 ` Preeti U Murthy
2015-01-28  9:15 ` Stewart Smith
2015-01-28  9:15   ` Stewart Smith
2015-01-28  9:50   ` Preeti U Murthy
2015-01-28  9:50     ` Preeti U Murthy
2015-01-28 22:24     ` Stewart Smith
2015-01-28 22:24       ` Stewart Smith
2015-01-30  3:56 ` Michael Ellerman [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=20150130035652.3C252140277@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.