Lines Matching refs:transfers

25 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
49 select and/or deselect operations must use I2C transfers to complete
51 full transaction, unrelated I2C transfers may interleave the different
74  4. M1 (presumably) does some I2C transfers as part of its select.
75     These transfers are normal I2C transfers that locks the parent
114   number (one, in most cases) of I2C transfers. Unrelated I2C transfers
130 has to ensure that any and all I2C transfers through that parent
131 adapter during the transaction are unlocked I2C transfers (using e.g.
154  5.  If M1 does any I2C transfers (on this root adapter) as part of
155      its select, those transfers must be unlocked I2C transfers so
178   and the parent mux issues I2C transfers as part of its select).
184   pinctrl, regmap or iio, it is essential that any I2C transfers
213 issues any unlocked I2C transfers on the root adapter that may leak
261 be no I2C transfers during its calls to ->select and ->deselect, and
262 if there are, any such transfers might appear on the slave side of M2
263 as partial I2C transfers, i.e. garbage or worse. This might cause
268 prematurely, as might any I2C transfers part of M1->select.