Lines Matching full:m2

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
214 through and be seen by the M2 adapter, thus closing M2 prematurely.
225     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
248     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
260 be avoided. The reason is that M2 probably assumes that there will
262 if there are, any such transfers might appear on the slave side of M2
266 The topology is especially troublesome if M2 is an auto-closing
267 mux. In that case, any interleaved accesses to D4 might close M2
270 But if M2 is not making the above stated assumption, and if M2 is not
282     '--------'  |  |  mux M1  |--.  |  mux M2  |--.  .--------.
312     '--------'  |  |  mux M2  |--.  .--------.
336     '--------'  |  |  mux M2  |--.  .--------.
360     '--------'  |  |  mux M2  |--.  .--------.