Lines Matching +full:clock +full:- +full:master

5 The GPIO based I2C bus master driver can be configured to provide fault
7 which is driven by the I2C bus master driver under test. The GPIO fault
9 master driver should handle gracefully.
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
31 -----
36 master under test should detect this condition and trigger a bus recovery (see
52 in a bus master driver, make sure you checked your hardware setup for such
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
89 Here, we want to simulate the condition where the master under test loses the
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.
99 Arbitration lost is achieved by waiting for SCL going down by the master under
110   # i2cget -y <bus_to_test> 0x3f
115 This fault injector will create a Kernel panic once the master under test
116 started a transfer. This usually means that the state machine of the bus master
122 --------------
126 The calling process will then sleep and wait for the next bus clock. The
129 Start of a transfer is detected by waiting for SCL going down by the master
133   # i2cget -y <bus_to_test> <some_address>