Lines Matching full:m1

63     '--------'  |  |  mux M1  |--.  .--------.
72  2. M1 locks muxes on its parent (the root adapter in this case).
73  3. M1 calls ->select to ready the mux.
74  4. M1 (presumably) does some I2C transfers as part of its select.
77  5. M1 feeds the I2C transfer from step 1 to its parent adapter as a
79  6. M1 calls ->deselect, if it has one.
81  8. M1 unlocks muxes on its parent.
142     '--------'  |  |  mux M1  |--.  .--------.
151  2.  M1 locks muxes on its parent (the root adapter in this case).
152  3.  M1 locks its parent adapter.
153  4.  M1 calls ->select to ready the mux.
154  5.  If M1 does any I2C transfers (on this root adapter) as part of
157  6.  M1 feeds the I2C transfer from step 1 to the root adapter as an
160  7.  M1 calls ->deselect, if it has one.
162  9.  M1 unlocks its parent adapter.
163  10. M1 unlocks muxes on its parent.
201     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
209 and specifically when M2 requests its parent to lock, M1 passes
212 This topology is bad if M2 is an auto-closing mux and M1->select
225     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
232 full duration of the operation (muxes on the top child adapter of M1
248     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
255 for the full duration of the operation (M1 locks child muxes on the
268 prematurely, as might any I2C transfers part of M1->select.
282     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
289 duration of the operation (muxes on the top child adapter of M1
294 accesses, M1 locks the root adapter. For D4 accesses, the root
307                 |  |  mux M1  |-----| dev D2 |
331                 |  |  mux M1  |-----| dev D2 |
355                 |  |  mux M1  |-----| dev D2 |