Lines Matching refs:MUX

10 I2C topology can be complex because of the existence of I2C MUX
12 kernel abstracts the MUX channels into logical I2C bus numbers. However, there
13 is a gap of knowledge to map from the I2C bus physical number and MUX topology
32 2.  General knowledge of I2C, I2C MUX and I2C topology.
85 an abstraction of a channel behind an I2C MUX. In case it is an abstraction of a
86 MUX channel, whenever we access an I2C device via a such logical bus, the kernel
87 will switch the I2C MUX for you to the proper channel as part of the
109 MUX fanouts. For the following examples, we will assume that the physical I2C
123   `-- 7-0071 (4-channel I2C MUX at 0x71)
127       |   |-- 73-0070 (I2C MUX at 0x70, exists in DTS, but failed to probe)
128       |   `-- 73-0072 (8-channel I2C MUX at 0x72)
144 Reading this link will also tell you which I2C MUX device created
165 abstracts an I2C MUX channel under the parent bus.
174 ``i2c-73`` is a logical bus fanout by an I2C MUX under ``i2c-7``
177 switch the I2C MUX addressed 0x71 to the proper channel for you as part of the
184 representing certain I2C MUX channels based on the knowledge of physical
188 in DTS. There is a 4-channel MUX at address 0x71 on that bus. There is another
189 8-channel MUX at address 0x72 behind the channel 1 of the 0x71 MUX. Let us
191 of the 0x72 MUX.
202 There, we see the 0x71 MUX as ``7-0071``. Go inside it::
215 We find out that the channel 1 of 0x71 MUX on ``i2c-7`` is assigned
232 we can now find the 0x72 MUX and what logical I2C bus numbers
251 There, we find out the logical I2C bus number of the channel 3 of the 0x72 MUX
255 Tip: Once you understand the I2C topology with MUX, command
280 If not specified in DTS, when an I2C MUX driver is applied and the MUX device is
281 successfully probed, the kernel will assign the MUX channels with a logical bus
284 4-channel MUX is applied successfully, we will have ``i2c-16`` for the
285 MUX channel 0, and all the way to ``i2c-19`` for the MUX channel 3.
287 The kernel software developer is able to pin the fanout MUX channels to a static
292 In the above example, there is an 8-channel I2C MUX at address 0x70 on physical
293 I2C bus 2. The channel 2 of the MUX is defined as ``imux18`` in DTS,
299 can pin the fanout channels of a MUX on bus 3 to start at 30. So 30 will be the
300 logical bus number of the channel 0 of the MUX on bus 3, and 37 will be the
301 logical bus number of the channel 7 of the MUX on bus 3.
347 I2C MUX Device
350 While you may be already aware of this in previous sections, an I2C MUX device