Lines Matching full:m1

116     '--------'  |  |  mux M1  |--.  .--------.
125  2. M1 locks muxes on its parent (the root adapter in this case).
126  3. M1 calls ->select to ready the mux.
127  4. M1 (presumably) does some i2c-transfers as part of its select.
130  5. M1 feeds the i2c-transfer from step 1 to its parent adapter as a
132  6. M1 calls ->deselect, if it has one.
134  8. M1 unlocks muxes on its parent.
172     '--------'  |  |  mux M1  |--.  .--------.
181  2. M1 locks muxes on its parent (the root adapter in this case).
182  3. M1 locks its parent adapter.
183  4. M1 calls ->select to ready the mux.
184  5. If M1 does any i2c-transfers (on this root adapter) as part of
187  6. M1 feeds the i2c-transfer from step 1 to the root adapter as an
190  7. M1 calls ->deselect, if it has one.
192  9. M1 unlocks its parent adapter.
193 10. M1 unlocks muxes on its parent.
211     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
219 and specifically when M2 requests its parent to lock, M1 passes
222 This topology is bad if M2 is an auto-closing mux and M1->select
235     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
242 full duration of the operation (muxes on the top child adapter of M1
256     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
263 for the full duration of the operation (M1 locks child muxes on the
276 prematurely, as might any i2c-transfers part of M1->select.
290     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
297 duration of the operation (muxes on the top child adapter of M1
302 accesses, M1 locks the root adapter. For D4 accesses, the root
315                 |  |  mux M1  |-----| dev D2 |
339                 |  |  mux M1  |-----| dev D2 |
363                 |  |  mux M1  |-----| dev D2 |