From: Gautham R Shenoy <ego@linux.vnet.ibm.com>
To: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-pm@vger.kernel.org, rjw@rjwysocki.net,
stewart@linux.vnet.ibm.com, benh@kernel.crashing.org,
svaidy@linux.vnet.ibm.com, ego@linux.vnet.ibm.com,
npiggin@gmail.com, mpe@ellerman.id.au
Subject: Re: [PATCH v3 1/2] powernv/cpuidle: Parse dt idle properties into global structure
Date: Tue, 3 Jul 2018 15:16:36 +0530 [thread overview]
Message-ID: <20180703094636.GA24693@in.ibm.com> (raw)
In-Reply-To: <1530609656-13301-2-git-send-email-akshay.adiga@linux.vnet.ibm.com>
Hi Akshay,
On Tue, Jul 03, 2018 at 02:50:55PM +0530, Akshay Adiga wrote:
> Device-tree parsing happens twice, once while deciding idle state to be
> used for hotplug and once during cpuidle init. Hence, parsing the device
> tree and caching it will reduce code duplication. Parsing code has been
> moved to pnv_parse_cpuidle_dt() from pnv_probe_idle_states(). In addition
> to the properties in the device tree the number of available states is
> also required.
>
> Signed-off-by: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
Looks good.
Reviewed-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
next prev parent reply other threads:[~2018-07-03 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 9:20 [PATCH v3 0/2] powernv/cpuidle Device-tree parsing cleanup Akshay Adiga
2018-07-03 9:20 ` [PATCH v3 1/2] powernv/cpuidle: Parse dt idle properties into global structure Akshay Adiga
2018-07-03 9:46 ` Gautham R Shenoy [this message]
2018-07-03 9:20 ` [PATCH v3 2/2] powernv/cpuidle: Use parsed device tree values for cpuidle_init Akshay Adiga
2018-07-03 9:47 ` Gautham R Shenoy
2018-07-04 10:54 ` [PATCH v3 0/2] powernv/cpuidle Device-tree parsing cleanup Rafael J. Wysocki
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=20180703094636.GA24693@in.ibm.com \
--to=ego@linux.vnet.ibm.com \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=stewart@linux.vnet.ibm.com \
--cc=svaidy@linux.vnet.ibm.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).