Lines Matching refs:which

5 level. Instead, the software must know which devices are connected on each
16 which is known in advance. It is thus possible to pre-declare the I2C
17 devices which live on this bus. This is done with an array of struct
18 i2c_board_info which is registered by calling i2c_register_board_info().
80 additional properties which might be needed to set up the device, please refer
88 which is currently located at Documentation/acpi/enumeration.txt.
117 The above code instantiates 1 I2C device on the I2C bus which is on the
121 present or not (for example for an optional feature which is not present
147 The above code instantiates up to 1 I2C device on the I2C bus which is on
152 The driver which instantiated the I2C device is responsible for destroying
163 chips on PC mainboards. There are several dozen models, which can live
175 * The I2C device driver must implement the detect() method, which
177 * Only buses which are likely to have a supported device and agree to be
185 destroyed automatically when the driver which detected them is removed,
196 * I2C buses must now explicitly say which I2C driver classes can probe
198   probed by default back then. The default is an empty class which means
210 In general, the kernel should know which I2C devices are connected and
213 interface is made of 2 attribute files which are created in every I2C bus