iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: i2c: i2c-topology: fix typo

Browse Source 
"intension" should have probably been "intention", however "intent" seems
even better.

Reported-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Acked-by: Peter Rosin <peda@axentia.se>
Signed-off-by: Wolfram Sang <wsa@kernel.org>
This commit is contained in:
Luca Ceresoli 2022-08-24 10:31:02 +02:00 committed by Wolfram Sang
parent b90cb10531
commit 6292b4ba60
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/i2c/i2c-topology.rst
View File

@ -103,7 +103,7 @@ ML2. It is not safe to build arbitrary topologies with two (or more)
I.e. the select-transfer-deselect transaction targeting e.g. device I.e. the select-transfer-deselect transaction targeting e.g. device
address 0x42 behind mux-one may be interleaved with a similar address 0x42 behind mux-one may be interleaved with a similar
operation targeting device address 0x42 behind mux-two. The operation targeting device address 0x42 behind mux-two. The
intension with such a topology would in this hypothetical example intent with such a topology would in this hypothetical example
be that mux-one and mux-two should not be selected simultaneously, be that mux-one and mux-two should not be selected simultaneously,
but mux-locked muxes do not guarantee that in all topologies. but mux-locked muxes do not guarantee that in all topologies.