Lines Matching refs:devices

1 How to instantiate I2C devices
4 Unlike PCI or USB devices, I2C devices are not enumerated at the hardware
5 level. Instead, the software must know which devices are connected on each
6 I2C bus segment, and what address these devices are using. For this
7 reason, the kernel code must instantiate I2C devices explicitly. There are
11 Method 1a: Declare the I2C devices by bus number
17 devices which live on this bus. This is done with an array of struct
45 The above code declares 3 devices on I2C bus 1, including their respective
47 question is registered, the I2C devices will be instantiated automatically
50 The devices will be automatically unbound and destroyed when the I2C bus
54 Method 1b: Declare the I2C devices via devicetree
58 devices is here done via devicetree as subnodes of the master controller.
79 Here, two devices are attached to the bus using a speed of 100kHz. For
84 Method 1c: Declare the I2C devices via ACPI
87 ACPI can also describe I2C devices. There is special documentation for this
91 Method 2: Instantiate the devices explicitly
99 you can instantiate your I2C devices explicitly. This is done by filling
158 Method 3: Probe an I2C bus for certain devices
170 In that case, I2C devices are neither declared nor instantiated
171 explicitly. Instead, i2c-core will probe for such devices as soon as their
184 I2C devices instantiated as a result of such a successful probe will be
192 * Probing is only one way to instantiate I2C devices now, while it was the
210 In general, the kernel should know which I2C devices are connected and
223 device. As no two devices can live at the same address on a given I2C
228 # echo eeprom 0x50 > /sys/bus/i2c/devices/i2c-3/new_device
232 * The I2C driver usually detects devices (method 3 above) but the bus
235 * The I2C driver usually detects devices, but your device lives at an
237 * The I2C driver usually detects devices, but your device is not detected,