diff options
| author | Luca Ceresoli <luca.ceresoli@bootlin.com> | 2022-08-24 10:31:02 +0200 |
|---|---|---|
| committer | Wolfram Sang <wsa@kernel.org> | 2022-08-29 12:28:13 +0200 |
| commit | 6292b4ba607de5bcf4ab0e57892a2f8068e6b997 (patch) | |
| tree | f7c72b97019217338773b3731d6f70393789cec4 /Documentation | |
| parent | b90cb1053190353cc30f0fef0ef1f378ccc063c5 (diff) | |
docs: i2c: i2c-topology: fix typo
"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>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/i2c/i2c-topology.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/i2c/i2c-topology.rst b/Documentation/i2c/i2c-topology.rst index 7cb53819778e..c9ed3b4d6085 100644 --- a/Documentation/i2c/i2c-topology.rst +++ b/Documentation/i2c/i2c-topology.rst @@ -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 address 0x42 behind mux-one may be interleaved with a similar 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, but mux-locked muxes do not guarantee that in all topologies. |