Lines Matching refs:physical

13 is a gap of knowledge to map from the I2C bus physical number and MUX topology
16 the concept of logical I2C buses in the kernel, by knowing the physical I2C
41 start with ``i2c-`` are I2C buses, which may be either physical or logical. The
63 physical I2C bus controllers. The controllers are hardware and physical, and the
73 For each physical I2C bus controller, the system vendor may assign a physical
82 written upon virtual memory space, instead of physical memory space.
84 Each logical I2C bus may be an abstraction of a physical I2C bus controller, or
93 If the logical I2C bus is a direct abstraction of a physical I2C bus controller,
94 let us call it a physical I2C bus.
99 This may be a confusing part for people who only know about the physical I2C
100 design of a board. It is actually possible to rename the I2C bus physical number
106 bus physical number the same as their corresponding logical I2C bus number,
108 users. These physical I2C buses can be served as good starting points for I2C
109 MUX fanouts. For the following examples, we will assume that the physical I2C
110 bus has a number same as their I2C bus physical number.
122   i2c-7 (physical I2C bus controller 7)
138 One simple way to distinguish between a physical I2C bus and a logical I2C bus,
148 physical I2C bus, directly abstracting a physical I2C bus controller. For
156 In this case, ``i2c-7`` is a physical I2C bus, so it does not have the symbolic
158 follows the common practice by not renaming physical I2C buses, this should also
159 mean the physical I2C bus controller 7 of the system.
163 by the link is the parent bus which may be either a physical I2C bus or a
184 representing certain I2C MUX channels based on the knowledge of physical
187 In this example, we have a system which has a physical I2C bus 7 and not renamed
292 In the above example, there is an 8-channel I2C MUX at address 0x70 on physical