From: Eddie James <eajames@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
wsa@the-dreams.de, robh+dt@kernel.org,
gregkh@linuxfoundation.org, jk@ozlabs.org, joel@jms.id.au,
andrew@aj.id.au, eajames@linux.vnet.ibm.com,
cbostic@linux.vnet.ibm.com,
"Edward A. James" <eajames@us.ibm.com>
Subject: [PATCH v2 0/6] drivers/i2c: Add FSI-attached I2C master algorithm
Date: Mon, 10 Jul 2017 13:37:56 -0500 [thread overview]
Message-ID: <1499711882-12918-1-git-send-email-eajames@linux.vnet.ibm.com> (raw)
From: "Edward A. James" <eajames@us.ibm.com>
This series adds an algorithm for an I2C master physically located on an FSI
slave device. The I2C master has multiple ports, each of which may be connected
to an I2C slave. Access to the I2C master registers is achieved over FSI bus.
Due to the multi-port nature of the I2C master, the driver instantiates a new
I2C adapter for each port connected to a slave. The connected ports should be
defined in the device tree under the I2C master device.
Changes since v1:
* Switch "port" to "i2c-bus" for child nodes in the dt.
* Switch "port" to "reg" dt property.
* Add example device under i2c-bus node in docs.
* Set of_node of I2C adapter.
* Use dynamically allocated numbering for I2C adapters.
* Remove ida counters; unnecessary.
Edward A. James (6):
drivers/i2c: Add FSI-attached I2C master algorithm
drivers/i2c: Add port structure to FSI algorithm
drivers/i2c: Add transfer implementation for FSI algorithm
drivers/i2c: Add I2C master locking to FSI algorithm
drivers/i2c: Add bus recovery for FSI algorithm
dt-bindings: i2c: Add FSI-attached I2C master dt binding documentation
Documentation/devicetree/bindings/i2c/i2c-fsi.txt | 40 ++
drivers/i2c/busses/Kconfig | 11 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-fsi.c | 637 ++++++++++++++++++++++
4 files changed, 689 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-fsi.txt
create mode 100644 drivers/i2c/busses/i2c-fsi.c
--
1.8.3.1
next reply other threads:[~2017-07-10 18:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 18:37 Eddie James [this message]
[not found] ` <1499711882-12918-1-git-send-email-eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-07-10 18:37 ` [PATCH v2 1/6] drivers/i2c: Add FSI-attached I2C master algorithm Eddie James
2017-07-10 18:38 ` [PATCH v2 4/6] drivers/i2c: Add I2C master locking to FSI algorithm Eddie James
2017-07-10 18:37 ` [PATCH v2 2/6] drivers/i2c: Add port structure " Eddie James
2017-07-10 18:37 ` [PATCH v2 3/6] drivers/i2c: Add transfer implementation for " Eddie James
2017-07-10 18:38 ` [PATCH v2 5/6] drivers/i2c: Add bus recovery " Eddie James
2017-07-10 18:38 ` [PATCH v2 6/6] dt-bindings: i2c: Add FSI-attached I2C master dt binding documentation Eddie James
2017-07-14 16:05 ` Rob Herring
2017-07-17 14:11 ` [PATCH v2 0/6] drivers/i2c: Add FSI-attached I2C master algorithm Greg KH
2017-07-17 14:16 ` Joel Stanley
2017-07-17 14:20 ` Wolfram Sang
2017-07-17 14:26 ` Greg KH
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=1499711882-12918-1-git-send-email-eajames@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--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-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).