All of lore.kernel.org
 help / color / mirror / Atom feed
From: christopher.lee.bostic@gmail.com
To: openbmc@lists.ozlabs.org
Cc: joel@jms.id.au, zahrens@us.ibm.com, xxpetri@de.ibm.com,
	Chris Bostic <cbostic@us.ibm.com>
Subject: [PATCH linux v5 18/18] Documenation: Add basic FSI text file
Date: Wed, 19 Oct 2016 18:09:46 -0500	[thread overview]
Message-ID: <1476918586-13475-19-git-send-email-christopher.lee.bostic@gmail.com> (raw)
In-Reply-To: <1476918586-13475-1-git-send-email-christopher.lee.bostic@gmail.com>

From: Chris Bostic <cbostic@us.ibm.com>

Add documentation explaining the basics of FSI and how to find
more information.

Signed-off-by: Chris Bostic <cbostic@us.ibm.com>
---
 Documentation/fsi.txt | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 Documentation/fsi.txt

diff --git a/Documentation/fsi.txt b/Documentation/fsi.txt
new file mode 100644
index 0000000..b8c94a0
--- /dev/null
+++ b/Documentation/fsi.txt
@@ -0,0 +1,36 @@
+The Flexible Support Interface (FSI) is a two wire bus consisting of
+a serial data line and a clock capable of running at up to 166 MHz.
+FSI features strong data integrity with CRC protection and is capable
+of very high fan out.
+
+The complete hardware specification[1] for FSI is publicly available on
+the OpenPower Foundation website:
+
+[1] http://openpowerfoundation.org/wp-content/uploads/resources/OpenFSI-spec/content/ch_preface.html
+
+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 / Configuration 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 contains, 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.
-- 
1.8.2.2

  parent reply	other threads:[~2016-10-19 23:10 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 23:09 [PATCH linux v5 00/18] FSI device driver introduction christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 01/18] fsi: Add empty fsi bus definitions christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 02/18] fsi: Add device & driver definitions christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 03/18] fsi: add driver to device matches christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 04/18] fsi: Add fsi master definition christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 05/18] fsi: Add fake master driver christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 06/18] fsi: enable debug christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 07/18] fsi: Add slave definition christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 08/18] fsi: Add empty master scan christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 09/18] fsi: Add crc4 helpers christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 10/18] fsi: Implement slave initialisation christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 11/18] fsi: scan slaves & register devices christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 12/18] fsi: Add device read/write/peek functions christopher.lee.bostic
2016-10-19 23:09 ` [PATCH linux v5 13/18] drivers/fsi: Set up links for slave communication christopher.lee.bostic
2016-10-19 23:39   ` Jeremy Kerr
2016-10-20  0:10     ` Joel Stanley
2016-10-20 14:16       ` Christopher Bostic
2016-10-21  5:28   ` Jeremy Kerr
2016-10-28 21:07     ` Christopher Bostic
2016-10-19 23:09 ` [PATCH linux v5 14/18] drivers/fsi: Set slave SMODE to init communications christopher.lee.bostic
2016-10-20  0:24   ` Jeremy Kerr
2016-10-19 23:09 ` [PATCH linux v5 15/18] drivers/fsi: Add GPIO FSI master christopher.lee.bostic
2016-10-20  1:26   ` Jeremy Kerr
2016-10-20 15:02     ` Christopher Bostic
2016-10-21  1:26       ` Jeremy Kerr
2016-10-30 21:29         ` Christopher Bostic
2016-10-31  0:59           ` Jeremy Kerr
2016-10-19 23:09 ` [PATCH linux v5 16/18] drivers/fsi: Add client driver register utilities christopher.lee.bostic
2016-10-20  1:29   ` Jeremy Kerr
2016-10-20 15:07     ` Christopher Bostic
2016-10-19 23:09 ` [PATCH linux v5 17/18] drivers/fsi: Add SCOM FSI client device driver christopher.lee.bostic
2016-10-20  3:27   ` Jeremy Kerr
2016-10-20 15:21     ` Christopher Bostic
2016-10-21  5:24       ` Jeremy Kerr
2016-10-28 19:25         ` Christopher Bostic
2016-10-20 20:11     ` Christopher Bostic
2016-10-19 23:09 ` christopher.lee.bostic [this message]
2016-10-20  2:17   ` [PATCH linux v5 18/18] Documenation: Add basic FSI text file Jeremy Kerr
2016-10-20 15:11     ` Christopher Bostic

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=1476918586-13475-19-git-send-email-christopher.lee.bostic@gmail.com \
    --to=christopher.lee.bostic@gmail.com \
    --cc=cbostic@us.ibm.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=xxpetri@de.ibm.com \
    --cc=zahrens@us.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 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.