[PATCH linux v3 00/18] FSI device driver introduction
christopher.lee.bostic at gmail.com
christopher.lee.bostic at gmail.com
Wed Oct 12 08:39:45 AEDT 2016
From: Chris Bostic <cbostic at us.ibm.com>
Patch Descriptions:
Patches 01-13 have been provided by Jeremy Kerr as an example of
how FSI function should be phased in. This includes the basic framework
to add FSI extensions to the Linux bus and device models. Patch 13
is a beginning definition of a GPIO controlled master controlled in
firmware.
Patch 14 contains minimal text formatting changes to deal with
checkpatch and git am warnings.
Patch 15 covers minor recommended changes to Jeremy's patches 01-13.
Patch 16 adds function to set up read/write access to a given CFAM.
Patch 17 covers implementation of the FSI GPIO master.
Patch 18 defines the SCOM FSI device driver client.
General Information:
Introduction of the IBM 'Flexible Support Interface' (FSI) bus device
driver. FSI is a high fan out serial bus consisting of a clock and a serial
data line capable of running at speeds up to 166 MHz.
This set provides the basic framework to add FSI extensions to the
Linux bus and device models. Master specific implementations are
defined to utilize the core FSI function.
This patch set does not include extended FSI function such as:
* Hub master support
* Cascaded master support
* Application layer hot plug notification
* Application layer FSI bus status interface
Common FSI terminology:
* Master
Controller of the FSI bus. Only the master is allowed to control the
clock line and is the initiator of all transactions on a bus.
* Slave
The receiver or target of a master initiated transaction. The slave
cannot initiate communications on a bus and must respond to any
master requests for data.
* CFAM
Stands for Common Field replaceable unit Access Macro. A CFAM is an
ASIC residing in any device requiring FSI communications. CFAMs
consist of an array of hardware 'engines' used for various purposes.
I2C masters, UARTs, General Purpose IO hardware are common types of
these engines.
* Configuration Space / Table
A table contained at the beginning of each CFAM address space.
This table lists information such as the CFAM's ID, which engine types
and versions it has available, as well as its addressing range.
* FSI Client driver
A device driver that registers with the FSI core so that it can access
devices it owns on an FSI bus.
Chris Bostic (5):
drivers/fsi: Fix some text formatting
drivers/fsi: Revisions to existing patch set
drivers/fsi: Set up CFAMs for communication
drivers/fsi: Add GPIO master functionality
drivers/fsi: Add SCOM FSI client device driver
Jeremy Kerr (13):
fsi: Add empty fsi bus definitions
fsi: Add device & driver definitions
fsi: add driver to device matches
fsi: Add fsi master definition
fsi: Add fake master driver
fsi: enable debug
fsi: Add slave defintion
fsi: Add empty master scan
fsi: Add crc4 helpers
fsi: Implement slave initialisation
fsi: scan slaves & register devices
fsi: Add device read/write/peek functions
fsi: Add GPIO master driver
.../devicetree/bindings/fsi/fsi-master-gpio.txt | 8 +
drivers/Kconfig | 2 +
drivers/Makefile | 1 +
drivers/fsi/Kconfig | 36 ++
drivers/fsi/Makefile | 5 +
drivers/fsi/fsi-cfam.h | 63 +++
drivers/fsi/fsi-core.c | 432 +++++++++++++++++++
drivers/fsi/fsi-master-fake.c | 97 +++++
drivers/fsi/fsi-master-gpio.c | 457 +++++++++++++++++++++
drivers/fsi/fsi-master.h | 39 ++
drivers/fsi/fsi-scom.c | 62 +++
drivers/fsi/fsi-slave.h | 62 +++
include/linux/fsi.h | 63 +++
13 files changed, 1327 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fsi/fsi-master-gpio.txt
create mode 100644 drivers/fsi/Kconfig
create mode 100644 drivers/fsi/Makefile
create mode 100644 drivers/fsi/fsi-cfam.h
create mode 100644 drivers/fsi/fsi-core.c
create mode 100644 drivers/fsi/fsi-master-fake.c
create mode 100644 drivers/fsi/fsi-master-gpio.c
create mode 100644 drivers/fsi/fsi-master.h
create mode 100644 drivers/fsi/fsi-scom.c
create mode 100644 drivers/fsi/fsi-slave.h
create mode 100644 include/linux/fsi.h
--
1.8.2.2
More information about the openbmc
mailing list