From: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-pm@vger.kernel.org
Cc: rjw@rjwysocki.net, svaidy@linux.vnet.ibm.com,
ego@linux.vnet.ibm.com, npiggin@gmail.com, mpe@ellerman.id.au,
Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
Subject: [PATCH 0/3] powernv/cpuidle Device-tree parsing cleanup
Date: Tue, 19 Jun 2018 10:34:25 +0530 [thread overview]
Message-ID: <1529384668-27548-1-git-send-email-akshay.adiga@linux.vnet.ibm.com> (raw)
Device-tree parsed multiple time in powernv cpuidle and powernv
hotplug code.
First to identify supported flags, secondly, to identify deepest_state
and first deep state, Thirdly , during cpudidle init to find the available
idle states. Any change in device-tree format will lead to make changes in
these 3 places.
This series adds code to parse device tree once and save in global structure.
Akshay Adiga (3):
powernv/cpuidle: Parse dt idle properties into global structure
cpuidle/powernv: Change platform init to avoid reparsing dt
powernv/cpuidle: Use parsed device tree values for cpuidle_init
arch/powerpc/include/asm/cpuidle.h | 16 +++
arch/powerpc/platforms/powernv/idle.c | 214 +++++++++++++++++++++-------------
drivers/cpuidle/cpuidle-powernv.c | 49 +++++---
3 files changed, 182 insertions(+), 97 deletions(-)
--
2.5.5
next reply other threads:[~2018-06-19 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 5:04 Akshay Adiga [this message]
2018-06-19 5:04 ` [PATCH 1/3] powernv/cpuidle: Parse dt idle properties into global structure Akshay Adiga
2018-06-20 4:41 ` Gautham R Shenoy
2018-06-19 5:04 ` [PATCH 2/3] cpuidle/powernv: Change platform init to avoid reparsing dt Akshay Adiga
2018-06-20 4:52 ` Gautham R Shenoy
2018-06-19 5:04 ` [PATCH 3/3] powernv/cpuidle: Use parsed device tree values for cpuidle_init Akshay Adiga
2018-06-20 5:01 ` Gautham R Shenoy
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=1529384668-27548-1-git-send-email-akshay.adiga@linux.vnet.ibm.com \
--to=akshay.adiga@linux.vnet.ibm.com \
--cc=ego@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=npiggin@gmail.com \
--cc=rjw@rjwysocki.net \
--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).