Lines Matching refs:I2C

1 This is a small guide for those who want to write kernel drivers for I2C
26 driver model device node, and its I2C address.
119 The Linux I2C stack was originally written to support access to hardware
121 that were more appropriate to SMBus (and PCs) than to I2C.  One of these
126 As Linux and its I2C stack became more widely used in embedded systems
128 problematic.  Drivers for I2C devices that issue interrupts need more (and
138 boot firmware, reports what I2C devices exist.  For example, there may be
139 a table, in the kernel or from the boot loader, identifying I2C devices
142 create i2c_client objects for each I2C device.
144 I2C device drivers using this binding model work just like any other
165 If you know for a fact that an I2C device is connected to a given I2C bus,
174 Sometimes you know that a device is connected to a given I2C bus, but you
177 models, and I2C device addresses change from one model to the next.  In
180 possible I2C addresses to probe.  A device is created for the first
186 in the I2C bus driver. You may want to save the returned i2c_client
193 Sometimes you do not know in advance which I2C devices are connected to
194 a given I2C bus.  This is for example the case of hardware monitoring
203 (or class) so that only I2C buses which may have that type of device
206 needed would set its class to I2C_CLASS_HWMON, and only I2C adapters
209 a device of that type on the given I2C adapter.  All it prevents is
216 quickly.  Keep in mind that the I2C protocol doesn't include any
229 Each I2C device which has been created using i2c_new_device() or
232 called automatically before the underlying I2C bus itself is removed, as a
270 MODULE_DESCRIPTION("Driver for Barf Inc. Foo I2C devices");
279 If your I2C device needs special handling when entering a system low
287 I2C messaging to the device being suspended or resumed (since their
288 parent I2C adapter is active when these calls are issued, and IRQs
295 If your I2C device needs special handling when the system shuts down
301 I2C messaging.
318 If you can choose between plain I2C communication and SMBus level
320 commands, but only some of them understand plain I2C!
323 Plain I2C communication
347 actual I2C protocol.