summaryrefslogtreecommitdiff
path: root/Documentation/i2c/i2c-topology.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/i2c/i2c-topology.rst')
-rw-r--r--Documentation/i2c/i2c-topology.rst2
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.