mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
synced 2025-01-06 14:05:39 +00:00
92d5d6434d
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> |
||
---|---|---|
.. | ||
busses | ||
muxes | ||
dev-interface.rst | ||
dma-considerations.rst | ||
fault-codes.rst | ||
functionality.rst | ||
gpio-fault-injection.rst | ||
i2c_bus.svg | ||
i2c-protocol.rst | ||
i2c-stub.rst | ||
i2c-sysfs.rst | ||
i2c-topology.rst | ||
index.rst | ||
instantiating-devices.rst | ||
old-module-parameters.rst | ||
slave-eeprom-backend.rst | ||
slave-interface.rst | ||
slave-testunit-backend.rst | ||
smbus-protocol.rst | ||
summary.rst | ||
ten-bit-addresses.rst | ||
writing-clients.rst |