Lines Matching refs:can

5 some things can be done slightly or completely different. Use this as a
55 should match the module name (if the driver can be compiled as a module),
56 although you can use MODULE_ALIAS (passing "foo" in this example) to add
67 Each client structure has a special `data' field that can point to any
91 but many chips have some kind of register-value idea that can easily
124 can be sufficiently configured using only such probe primitives.
130 that can't be distinguished by protocol probing, or which need some board
166 you can instantiate that device by simply filling an i2c_board_info
170 If a driver supports different device types, you can specify the type you
171 want using the type field.  You can also specify an IRQ and platform data
178 that case, you can use the i2c_new_probed_device() variant, which is
215 otherwise misdetections are likely to occur and things can get wrong
220 transfer can be seen as a read operation by a chip and as a write
230 i2c_new_probed_device() can be unregistered by calling
233 device can't survive its parent in the device driver model.
255 The module_i2c_driver() macro can be used to reduce above code.
259 Note that some functions are marked by `__init'.  These functions can
286 would for any other driver stack.  The calls can sleep, and can use
300 would for any other driver stack:  the calls can sleep, and can use
316 to do this. You can find all of them in <linux/i2c.h>.
318 If you can choose between plain I2C communication and SMBus level
340 This sends a series of messages. Each message can be a read or write,
341 and they can be mixed in any way. The transactions are combined: no
346 You can read the file `i2c-protocol' for more information about the
392 You can read the file `smbus-protocol' for more information about the