From: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
To: stewart@linux.vnet.ibm.com, cyrilbur@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
ego@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com,
Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Subject: [PATCH V9 0/3] powernv : Add support for OPAL-OCC command/response interface
Date: Mon, 31 Jul 2017 13:06:02 +0530 [thread overview]
Message-ID: <1501486565-16079-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com> (raw)
In P9, OCC (On-Chip-Controller) supports shared memory based
commad-response interface. Within the shared memory there is an OPAL
command buffer and OCC response buffer that can be used to send
inband commands to OCC. The following commands are supported:
1) Set system powercap
2) Set CPU-GPU power shifting ratio
3) Clear min/max for OCC sensor groups
Changes from V9:
- Fixed return after erroring from mutex_lock_interruptible()
- Added documentation
Shilpasri G Bhat (3):
powernv: powercap: Add support for powercap framework
powernv: Add support to set power-shifting-ratio
powernv: Add support to clear sensor groups data
.../ABI/testing/sysfs-firmware-opal-powercap | 31 +++
Documentation/ABI/testing/sysfs-firmware-opal-psr | 18 ++
.../bindings/powerpc/opal/sensor-groups.txt | 23 ++
arch/powerpc/include/asm/opal-api.h | 8 +-
arch/powerpc/include/asm/opal.h | 9 +
arch/powerpc/include/uapi/asm/opal-occ.h | 23 ++
arch/powerpc/platforms/powernv/Makefile | 2 +-
arch/powerpc/platforms/powernv/opal-occ.c | 116 ++++++++++
arch/powerpc/platforms/powernv/opal-powercap.c | 244 +++++++++++++++++++++
arch/powerpc/platforms/powernv/opal-psr.c | 175 +++++++++++++++
arch/powerpc/platforms/powernv/opal-wrappers.S | 5 +
arch/powerpc/platforms/powernv/opal.c | 10 +
12 files changed, 662 insertions(+), 2 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-firmware-opal-powercap
create mode 100644 Documentation/ABI/testing/sysfs-firmware-opal-psr
create mode 100644 Documentation/devicetree/bindings/powerpc/opal/sensor-groups.txt
create mode 100644 arch/powerpc/include/uapi/asm/opal-occ.h
create mode 100644 arch/powerpc/platforms/powernv/opal-occ.c
create mode 100644 arch/powerpc/platforms/powernv/opal-powercap.c
create mode 100644 arch/powerpc/platforms/powernv/opal-psr.c
--
1.8.3.1
next reply other threads:[~2017-07-31 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 7:36 Shilpasri G Bhat [this message]
2017-07-31 7:36 ` [PATCH V9 1/3] powernv: powercap: Add support for powercap framework Shilpasri G Bhat
2017-07-31 7:36 ` [PATCH V9 2/3] powernv: Add support to set power-shifting-ratio Shilpasri G Bhat
2017-07-31 7:36 ` [PATCH V9 3/3] powernv: Add support to clear sensor groups data Shilpasri G Bhat
-- strict thread matches above, loose matches on Subject: below --
2017-07-31 2:24 [PATCH V9 0/3] powernv : Add support for OPAL-OCC command/response interface Shilpasri G Bhat
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=1501486565-16079-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com \
--to=shilpa.bhat@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=cyrilbur@gmail.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--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).