From: Eddie James <eajames@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
bradleyb@fuzziesquirrel.com, jk@ozlabs.org,
cbostic@linux.vnet.ibm.com, joel@jms.id.au, andrew@aj.id.au,
eajames@linux.vnet.ibm.com,
"Edward A. James" <eajames@us.ibm.com>
Subject: [PATCH v2 0/5] drivers/fsi: Add SBEFIFO and OCC drivers
Date: Wed, 5 Jul 2017 16:36:52 -0500 [thread overview]
Message-ID: <1499290617-2598-1-git-send-email-eajames@linux.vnet.ibm.com> (raw)
From: "Edward A. James" <eajames@us.ibm.com>
This series adds two FSI-based device drivers. The OCC driver is dependent on
the SBEFIFO driver, as a user of it's in-kernel API. The in-kernel API provided
by the OCC driver will be used by a hwmon driver (on the lkml as "Add On-Chip
Controller (OCC) hwmon driver").
Changes since v1:
* Split bindings into separate patch and added SBEFIFO device binding
* Fixed #includes
* Fix SBEFIFO race condition between write() and poll_timer().
* Followed Rob's suggestion to just create one platform device for hwmon
driver, instead of using the device tree.
* Also check for "command in progress" response from OCC and try a while
Edward A. James (5):
drivers/fsi: Add SBEFIFO FSI client device driver
drivers/fsi/sbefifo: Add in-kernel API
drivers/fsi: Add On-Chip Controller (OCC) driver
drivers/fsi/occ: Add in-kernel API
Documentation/devicetree/bindings: Add FSI device documentation
.../devicetree/bindings/fsi/ibm,p9-occ.txt | 15 +
.../devicetree/bindings/fsi/ibm,p9-sbefifo.txt | 20 +
drivers/fsi/Kconfig | 17 +
drivers/fsi/Makefile | 2 +
drivers/fsi/fsi-sbefifo.c | 932 +++++++++++++++++++++
drivers/fsi/occ.c | 803 ++++++++++++++++++
include/linux/fsi-sbefifo.h | 30 +
include/linux/occ.h | 41 +
8 files changed, 1860 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt
create mode 100644 Documentation/devicetree/bindings/fsi/ibm,p9-sbefifo.txt
create mode 100644 drivers/fsi/fsi-sbefifo.c
create mode 100644 drivers/fsi/occ.c
create mode 100644 include/linux/fsi-sbefifo.h
create mode 100644 include/linux/occ.h
--
1.8.3.1
next reply other threads:[~2017-07-05 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 21:36 Eddie James [this message]
2017-07-05 21:36 ` [PATCH v2 1/5] drivers/fsi: Add SBEFIFO FSI client device driver Eddie James
2017-07-05 21:36 ` [PATCH v2 2/5] drivers/fsi/sbefifo: Add in-kernel API Eddie James
2017-07-12 17:24 ` kbuild test robot
2017-07-05 21:36 ` [PATCH v2 3/5] drivers/fsi: Add On-Chip Controller (OCC) driver Eddie James
2017-07-05 21:36 ` [PATCH v2 4/5] drivers/fsi/occ: Add in-kernel API Eddie James
2017-07-05 21:36 ` [PATCH v2 5/5] Documentation/devicetree/bindings: Add FSI device documentation Eddie James
2017-07-10 1:24 ` Rob Herring
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=1499290617-2598-1-git-send-email-eajames@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--cc=bradleyb@fuzziesquirrel.com \
--cc=cbostic@linux.vnet.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=eajames@us.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox