Message ID | 20220808141708.1021103-7-luca.ceresoli@bootlin.com |
---|---|
State | Superseded |
Headers | show |
Series | docs: i2c: rework I2C documentation, part II | expand |
On Mon, Aug 08, 2022 at 04:17:05PM +0200, luca.ceresoli@bootlin.com wrote: > From: Luca Ceresoli <luca.ceresoli@bootlin.com> > > "Etc" here was never meant to be a heading, it became one while converting > to ReST. > > It would be easy to just convert it to plain text, but rather remove it and > add an introductory text before the list that conveys the same meaning but > with a better reading flow. > > Fixes: ccf988b66d69 ("docs: i2c: convert to ReST and add to driver-api bookset") > Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Peter, are you fine with this change?
diff --git a/Documentation/i2c/i2c-topology.rst b/Documentation/i2c/i2c-topology.rst index 7cb53819778e..1b11535c8946 100644 --- a/Documentation/i2c/i2c-topology.rst +++ b/Documentation/i2c/i2c-topology.rst @@ -5,6 +5,8 @@ I2C muxes and complex topologies There are a couple of reasons for building more complex I2C topologies than a straight-forward I2C bus with one adapter and one or more devices. +Some example use cases are: + 1. A mux may be needed on the bus to prevent address collisions. 2. The bus may be accessible from some external bus master, and arbitration @@ -14,9 +16,6 @@ than a straight-forward I2C bus with one adapter and one or more devices. from the I2C bus, at least most of the time, and sits behind a gate that has to be operated before the device can be accessed. -Etc -=== - These constructs are represented as I2C adapter trees by Linux, where each adapter has a parent adapter (except the root adapter) and zero or more child adapters. The root adapter is the actual adapter that issues