Lines Matching refs:M1
132 '--------' | | mux M1 |--. .--------.
141 2. M1 locks muxes on its parent (the root adapter in this case).
142 3. M1 calls ->select to ready the mux.
143 4. M1 (presumably) does some I2C transfers as part of its select.
146 5. M1 feeds the I2C transfer from step 1 to its parent adapter as a
148 6. M1 calls ->deselect, if it has one.
150 8. M1 unlocks muxes on its parent.
192 '--------' | | mux M1 |--. .--------.
201 2. M1 locks muxes on its parent (the root adapter in this case).
202 3. M1 locks its parent adapter.
203 4. M1 calls ->select to ready the mux.
204 5. If M1 does any I2C transfers (on this root adapter) as part of
207 6. M1 feeds the I2C transfer from step 1 to the root adapter as an
210 7. M1 calls ->deselect, if it has one.
212 9. M1 unlocks its parent adapter.
213 10. M1 unlocks muxes on its parent.
231 '--------' | | mux M1 |--. | mux M2 |--. .--------.
239 and specifically when M2 requests its parent to lock, M1 passes
242 This topology is bad if M2 is an auto-closing mux and M1->select
255 '--------' | | mux M1 |--. | mux M2 |--. .--------.
262 full duration of the operation (muxes on the top child adapter of M1
276 '--------' | | mux M1 |--. | mux M2 |--. .--------.
283 for the full duration of the operation (M1 locks child muxes on the
296 prematurely, as might any I2C transfers part of M1->select.
310 '--------' | | mux M1 |--. | mux M2 |--. .--------.
317 duration of the operation (muxes on the top child adapter of M1
322 accesses, M1 locks the root adapter. For D4 accesses, the root
335 | | mux M1 |-----| dev D2 |
359 | | mux M1 |-----| dev D2 |
383 | | mux M1 |-----| dev D2 |