Lines Matching refs:I2C

1 This is a small guide for those who want to write kernel drivers for I2C
24 routines, a client structure specific information like the actual I2C
135 be encapsulated. Also, some chips have both ISA and I2C interfaces, and
210      A list of I2C addresses which should normally be examined.
212      A list of pairs of I2C addresses, each pair being an inclusive range of
215      A list of pairs. The first value is a bus number (-1 for any I2C bus), 
219      A list of triples. The first value is a bus number (-1 for any I2C bus), 
223      A list of pairs. The first value is a bus number (-1 for any I2C bus), 
224      the second is the I2C address. These addresses are never probed. 
227      A list of triples. The first value is a bus number (-1 for any I2C bus), 
229      I2C addresses that are never probed.
232      A list of pairs. The first value is a bus number (-1 for any I2C bus),
233      the second is the I2C address. A device is blindly assumed to be on
256 As well as I2C addresses, we have to cope with ISA addresses. Also, we
262      A list of I2C addresses which should normally be examined.
265      A list of pairs of I2C addresses, each pair being an inclusive range of
277      the ISA bus, -1 for any I2C bus), the second is the address. These
282      the ISA bus, -1 for any I2C bus), the second and third are addresses. 
287      the ISA bus, -1 for any I2C bus), the second is the I2C address. These
293      the ISA bus, -1 for any I2C bus), the second and third are addresses. 
294      These form an inclusive range of I2C addresses that are never probed.
302      -1 for any I2C bus), the second is the address. 
638   MODULE_DESCRIPTION("Driver for Barf Inc. Foo I2C devices");