Documentation/i2c/gpio-fault-injection.rst

12 'i2c-fault-injector' subdirectory in the Kernel debugfs filesystem, usually
15 injection. They will be described now along with their intended use-cases.
21 -----
26 because the bus master under test will not be able to clock. It should detect
27 the condition of SCL being unresponsive and report an error to the upper
31 -----
36 master under test should detect this condition and trigger a bus recovery (see
48 there are I2C client devices which detect a stuck SDA on their side and release
50 device deglitching and monitoring the I2C bus. It could also detect a stuck SDA
56 --------------------------
63 above, the bus master under test should detect this condition and try a bus
68 -----------------------
81 register 0x00 (if it has registers) when further clock pulses happen on SCL.
82 This is why bus recovery (up to 9 clock pulses) must either check SDA or send
90 bus arbitration against another master in a multi-master setup.
93 ------------------
97 and wait for the next bus clock. The process is interruptible, though.
102 address sent out should have a lot of '1' bits to be able to detect corruption.
110   # i2cget -y <bus_to_test> 0x3f
122 --------------
126 The calling process will then sleep and wait for the next bus clock. The
133   # i2cget -y <bus_to_test> <some_address>