Lines Matching refs:which
6 level. Instead, the software must know which devices are connected on each
16 for many embedded systems. On such systems, each I2C bus has a number which
18 which live on this bus.
54 additional properties which might be needed to set up the device, please refer
62 which is currently located at :doc:`../firmware-guide/acpi/enumeration`.
71 struct i2c_board_info which is registered by calling
129 The above code instantiates 1 I2C device on the I2C bus which is on the
133 present or not (for example for an optional feature which is not present
159 The above code instantiates up to 1 I2C device on the I2C bus which is on
164 The driver which instantiated the I2C device is responsible for destroying
175 chips on PC mainboards. There are several dozen models, which can live
188 * The I2C device driver must implement the detect() method, which
190 * Only buses which are likely to have a supported device and agree to be
198 destroyed automatically when the driver which detected them is removed,
210 * I2C buses must now explicitly say which I2C driver classes can probe
212 probed by default back then. The default is an empty class which means
224 In general, the kernel should know which I2C devices are connected and
227 interface is made of 2 attribute files which are created in every I2C bus