From: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, cyrilbur@gmail.com
Cc: linux-kernel@vger.kernel.org, benh@kernel.crashing.org,
paulus@samba.org, mpe@ellerman.id.au, svaidy@linux.vnet.ibm.com,
ego@linux.vnet.ibm.com,
Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Subject: [PATCH V3 0/2] Add support for OCC command/response interface
Date: Mon, 19 Jun 2017 11:44:30 +0530 [thread overview]
Message-ID: <1497852872-7985-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com> (raw)
In P9, OCC(On Chip Controller) can be sent commands inband via shared
memory based command response interface. This patch adds a platform
driver to support the OCC command-response interface.
The skiboot patch for the interface is posted here:
https://lists.ozlabs.org/pipermail/skiboot/2017-June/007705.html
Shilpasri G Bhat (2):
powerpc/powernv: Get a unique token for async completions
powerpc/powernv : Add support for OPAL-OCC command/response interface
arch/powerpc/include/asm/opal-api.h | 41 +++-
arch/powerpc/include/asm/opal.h | 4 +
arch/powerpc/platforms/powernv/Makefile | 2 +-
arch/powerpc/platforms/powernv/opal-async.c | 46 ++++
arch/powerpc/platforms/powernv/opal-occ.c | 307 +++++++++++++++++++++++++
arch/powerpc/platforms/powernv/opal-wrappers.S | 1 +
arch/powerpc/platforms/powernv/opal.c | 8 +
7 files changed, 407 insertions(+), 2 deletions(-)
create mode 100644 arch/powerpc/platforms/powernv/opal-occ.c
--
1.8.3.1
next reply other threads:[~2017-06-19 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 6:14 Shilpasri G Bhat [this message]
2017-06-19 6:14 ` [PATCH V3 1/2] powerpc/powernv: Get a unique token for async completions Shilpasri G Bhat
2017-06-19 6:14 ` [PATCH V3 2/2] powerpc/powernv : Add support for OPAL-OCC command/response interface Shilpasri G Bhat
2017-06-19 6:49 ` Cyril Bur
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=1497852872-7985-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=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).