Lines Matching refs:transfers

23 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
86 select and/or deselect operations must use I2C transfers to complete
88 full transaction, unrelated I2C transfers may interleave the different
112      number (one, in most cases) of I2C transfers. Unrelated I2C transfers
143  4. M1 (presumably) does some I2C transfers as part of its select.
144     These transfers are normal I2C transfers that locks the parent
162 has to ensure that any and all I2C transfers through that parent
163 adapter during the transaction are unlocked I2C transfers (using e.g.
172      and the parent mux issues I2C transfers as part of its select).
177      pinctrl, regmap or iio, it is essential that any I2C transfers
204  5.  If M1 does any I2C transfers (on this root adapter) as part of
205      its select, those transfers must be unlocked I2C transfers so
243 issues any unlocked I2C transfers on the root adapter that may leak
289 be no I2C transfers during its calls to ->select and ->deselect, and
290 if there are, any such transfers might appear on the slave side of M2
291 as partial I2C transfers, i.e. garbage or worse. This might cause
296 prematurely, as might any I2C transfers part of M1->select.