linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 linux 0/4] drivers/fsi: Add SBEFIFO and OCC drivers
Date: Wed, 21 Jun 2017 14:37:57 -0500	[thread overview]
Message-ID: <1498073881-3207-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 (to be sent to the lkml soon).

I previously sent up the first patch in the series independently, but decided
to split into the base driver and the addition of the in-kernel API, as it's
a little easier to digest. So, no v2, but I did include some fixes suggested by
Greg.

Edward A. James (4):
  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

 .../devicetree/bindings/fsi/ibm,p9-occ.txt         |  23 +
 drivers/fsi/Kconfig                                |  17 +
 drivers/fsi/Makefile                               |   2 +
 drivers/fsi/fsi-sbefifo.c                          | 921 +++++++++++++++++++++
 drivers/fsi/occ.c                                  | 790 ++++++++++++++++++
 include/linux/fsi-sbefifo.h                        |  30 +
 include/linux/occ.h                                |  27 +
 7 files changed, 1810 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/fsi/ibm,p9-occ.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

             reply	other threads:[~2017-06-21 19:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 19:37 Eddie James [this message]
2017-06-21 19:37 ` [PATCH linux 1/4] drivers/fsi: Add SBEFIFO FSI client device driver Eddie James
2017-06-21 19:37 ` [PATCH linux 2/4] drivers/fsi/sbefifo: Add in-kernel API Eddie James
2017-06-24 11:17   ` kbuild test robot
2017-06-21 19:38 ` [PATCH linux 3/4] drivers/fsi: Add On-Chip Controller (OCC) driver Eddie James
2017-06-23  9:10   ` kbuild test robot
2017-06-21 19:38 ` [PATCH linux 4/4] drivers/fsi/occ: Add in-kernel API Eddie James
2017-06-24 12:12   ` kbuild test robot
2017-06-26 18:35   ` 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=1498073881-3207-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;
as well as URLs for NNTP newsgroup(s).