Lines Matching refs:that

67 Each client structure has a special `data' field that can point to any
76 Note that starting with kernel 2.6.34, you don't have to set the `data' field
91 but many chips have some kind of register-value idea that can easily
121 that were more appropriate to SMBus (and PCs) than to I2C.  One of these
122 assumptions was that most adapters and devices drivers support the SMBUS_QUICK
123 protocol to probe device presence.  Another was that devices and their drivers
128 problematic.  Drivers for I2C devices that issue interrupts need more (and
130 that can't be distinguished by protocol probing, or which need some board
152 Remember that the i2c_driver does not create those client handles.  The
158 matches the device's name. It is passed the entry that was matched so
165 If you know for a fact that an I2C device is connected to a given I2C bus,
166 you can instantiate that device by simply filling an i2c_board_info
174 Sometimes you know that a device is connected to a given I2C bus, but you
178 that case, you can use the i2c_new_probed_device() variant, which is
179 similar to i2c_new_device(), except that it takes an additional list of
182 present in the address range, simply call i2c_new_probed_device() that
195 devices on a PC's SMBus.  In that case, you may want to let your driver
203 (or class) so that only I2C buses which may have that type of device
208 Note that the absence of matching classes does not prevent the use of
209 a device of that type on the given I2C adapter.  All it prevents is
212 Note that this mechanism is purely optional and not suitable for all
216 quickly.  Keep in mind that the I2C protocol doesn't include any
219 semantics associated to bus transfers, which means that the same
259 Note that some functions are marked by `__init'.  These functions can
281 activating a system wakeup mechanism -- do that by implementing the
399 Below all general purpose routines are listed, that were not mentioned