Lines Matching refs:transfers

21 i2c transfers, and all adapters with a parent are part of an "i2c-mux"
75 select and/or deselect operations must use i2c transfers to complete
77 full transaction, unrelated i2c transfers may interleave the different
100      number (one, in most cases) of i2c transfers. Unrelated i2c transfers
127  4. M1 (presumably) does some i2c-transfers as part of its select.
128     These transfers are normal i2c-transfers that locks the parent
146 has to ensure that any and all i2c transfers through that parent
147 adapter during the transaction are unlocked i2c transfers (using e.g.
155      and the parent mux issus i2c-transfers as part of its select).
160      pinctrl, regmap or iio, it is essential that any i2c transfers
184  5. If M1 does any i2c-transfers (on this root adapter) as part of
185     its select, those transfers must be unlocked i2c-transfers so
223 issues any unlocked i2c transfers on the root adapter that may leak
269 be no i2c transfers during its calls to ->select and ->deselect, and
270 if there are, any such transfers might appear on the slave side of M2
271 as partial i2c transfers, i.e. garbage or worse. This might cause
276 prematurely, as might any i2c-transfers part of M1->select.