From: Eddie James <eajames@linux.vnet.ibm.com>
To: openbmc@lists.ozlabs.org
Cc: joel@jms.id.au, bradleyb@fuzziesquirrel.com,
cbostic@linux.vnet.ibm.com,
"Edward A. James" <eajames@us.ibm.com>
Subject: [PATCH linux dev-4.10 0/3] drivers: fsi: Add OCC driver with SBEFIFO in-kernel API
Date: Fri, 12 May 2017 14:38:17 -0500 [thread overview]
Message-ID: <1494617900-32369-1-git-send-email-eajames@linux.vnet.ibm.com> (raw)
From: "Edward A. James" <eajames@us.ibm.com>
This patch series adds a driver to communicate with the POWER processor
On-Chip Controller (OCC), from a service processor. Communication is performed
via the SBEFIFO driver, which required a new in-kernel API.
The patch series includes device-tree updates to instantiate devices for the
OCC driver from the SBEFIFO driver.
An application to test the OCC driver can be found at
https://github.com/eddiejames/occtest
Edward A. James (3):
drivers: fsi: sbefifo: Add in-kernel API
drivers: fsi: sbefifo: Add OCC driver
dts: aspeed: witherspoon: Add FSI devices
arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts | 46 ++
drivers/fsi/Kconfig | 9 +
drivers/fsi/Makefile | 1 +
drivers/fsi/fsi-sbefifo.c | 161 ++++--
drivers/fsi/occ.c | 625 +++++++++++++++++++++++
include/linux/fsi-sbefifo.h | 30 ++
6 files changed, 842 insertions(+), 30 deletions(-)
create mode 100644 drivers/fsi/occ.c
create mode 100644 include/linux/fsi-sbefifo.h
--
1.8.3.1
next reply other threads:[~2017-05-12 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 19:38 Eddie James [this message]
2017-05-12 19:38 ` [PATCH linux dev-4.10 1/3] drivers: fsi: sbefifo: Add in-kernel API Eddie James
2017-05-12 19:38 ` [PATCH linux dev-4.10 2/3] drivers: fsi: sbefifo: Add OCC driver Eddie James
2017-06-01 6:55 ` Jeremy Kerr
2017-06-01 15:18 ` Eddie James
2017-05-12 19:38 ` [PATCH linux dev-4.10 3/3] dts: aspeed: witherspoon: Add FSI devices Eddie James
2017-06-05 6:29 ` Joel Stanley
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=1494617900-32369-1-git-send-email-eajames@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=cbostic@linux.vnet.ibm.com \
--cc=eajames@us.ibm.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
/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.