From: Pratik Rajesh Sampat <psampat@linux.ibm.com>
To: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
mpe@ellerman.id.au, mikey@neuling.org, npiggin@gmail.com,
vaidy@linux.ibm.com, ego@linux.vnet.ibm.com,
skiboot@lists.ozlabs.org, oohall@gmail.com,
psampat@linux.ibm.com, pratik.r.sampat@gmail.com
Subject: [RFC 0/3] cpuidle/powernv: Interface to handle idle-stop versioning
Date: Wed, 4 Mar 2020 21:31:20 +0530 [thread overview]
Message-ID: <cover.1583332695.git.psampat@linux.ibm.com> (raw)
A design patch series illuminates the idea of handling different
versions of idle-stop, the properties they support and the
quirks that need to be handled before entering or after exiting stop.
It also adds a functionality to identify firmware-enabled-stop and set
the according bits to encapsulate the support and corresponding handling
Corresponding RFC skiboot patch: https://lists.ozlabs.org/pipermail/skiboot/2020-March/016552.html
Pratik Rajesh Sampat (3):
Interface for an idle-stop dependency structure
Demonstration of handling an idle-stop quirk version
Introduce capability for firmware-enabled-stop
arch/powerpc/include/asm/processor.h | 19 +++++++++++++++++
arch/powerpc/kernel/dt_cpu_ftrs.c | 30 +++++++++++++++++++++++++++
arch/powerpc/platforms/powernv/idle.c | 25 ++++++++++++++++++----
drivers/cpuidle/cpuidle-powernv.c | 3 ++-
4 files changed, 72 insertions(+), 5 deletions(-)
--
2.24.1
next reply other threads:[~2020-03-04 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 16:01 Pratik Rajesh Sampat [this message]
2020-03-04 16:01 ` [RFC 1/3] Interface for an idle-stop dependency structure Pratik Rajesh Sampat
2020-03-05 0:43 ` kbuild test robot
2020-04-08 10:51 ` Gautham R Shenoy
2020-04-08 10:51 ` Gautham R Shenoy
2020-04-12 12:18 ` Pratik Sampat
2020-04-12 12:18 ` Pratik Sampat
2020-03-04 16:01 ` [RFC 2/3] Demonstration of handling an idle-stop quirk version Pratik Rajesh Sampat
2020-03-04 16:01 ` [RFC 3/3] Introduce capability for firmware-enabled-stop Pratik Rajesh Sampat
2020-04-08 10:54 ` Gautham R Shenoy
2020-04-08 10:54 ` 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=cover.1583332695.git.psampat@linux.ibm.com \
--to=psampat@linux.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oohall@gmail.com \
--cc=pratik.r.sampat@gmail.com \
--cc=skiboot@lists.ozlabs.org \
--cc=vaidy@linux.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 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.