diff options
author | Luca Ceresoli <luca.ceresoli@bootlin.com> | 2022-08-24 10:31:04 +0200 |
---|---|---|
committer | Wolfram Sang <wsa@kernel.org> | 2022-08-29 12:28:13 +0200 |
commit | 92d5d6434d285510a3563ebace24306e240615e1 (patch) | |
tree | 65083dd82943190da1c7e5cccef9153ff82e60e2 /Documentation/i2c/busses | |
parent | docs: i2c: i2c-topology: fix incorrect heading (diff) | |
download | linux-92d5d6434d285510a3563ebace24306e240615e1.tar.xz linux-92d5d6434d285510a3563ebace24306e240615e1.zip |
docs: i2c: i2c-topology: reorder sections more logically
The sequence of sections is a bit confusing here:
* we list the mux locking scheme for existing drivers before introducing
what mux locking schemes are
* we list the caveats for each locking scheme (which are tricky) before
the example of the simple use case
Restructure it entirely with the following logic:
* Intro ("I2C muxes and complex topologies")
* Locking
- mux-locked
- example
- caveats
- parent-locked
- example
- caveats
* Complex examples
* Mux type of existing device drivers
While there, also apply some other improvements:
* convert the caveat list from a table (with only one column carrying
content) to a bullet list.
* add a small introductory text to bridge the gap from listing the use
cases to telling about the hardware components to handle them and then
the device drivers that implement those.
* make empty lines usage more uniform
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Acked-by: Peter Rosin <peda@axentia.se>
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Diffstat (limited to 'Documentation/i2c/busses')
0 files changed, 0 insertions, 0 deletions