Lines Matching refs:M2
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
224 through and be seen by the M2 adapter, thus closing M2 prematurely.
235 '--------' | | mux M1 |--. | mux M2 |--. .--------.
256 '--------' | | mux M1 |--. | mux M2 |--. .--------.
268 be avoided. The reason is that M2 probably assumes that there will
270 if there are, any such transfers might appear on the slave side of M2
274 The topology is especially troublesome if M2 is an auto-closing
275 mux. In that case, any interleaved accesses to D4 might close M2
278 But if M2 is not making the above stated assumption, and if M2 is not
290 '--------' | | mux M1 |--. | mux M2 |--. .--------.
320 '--------' | | mux M2 |--. .--------.
344 '--------' | | mux M2 |--. .--------.
368 '--------' | | mux M2 |--. .--------.