struct_i2c_driver - represent an I2C device driver
2. SYNOPSIS ▲
*, pm_message_t mesg);
3. MEMBERS ▲
What kind of i2c device we instantiate (for detect)
Callback for bus addition (deprecated)
Callback for device binding
Callback for device unbinding
Callback for device shutdown
Callback for device suspend
Callback for device resume
Alert callback, for example for the SMBus alert protocol
Callback for bus-wide signaling (optional)
Device driver model driver
List of I2C devices supported by this driver
Callback for device detection
The I2C addresses to probe (for detect)
List of detected clients we created (for i2c-core use only)
4. DESCRIPTION ▲
The driver.owner field should be set to the module owner of this driver. The driver.name field should be set to the name of this driver.
For automatic device detection, both detect and address_list must be defined. class should also be set, otherwise only devices forced with module parameters will be created. The detect function must fill at least the name field of the i2c_board_info structure it is handed upon successful detection, and possibly also the flags field.
If detect is missing, the driver will still work fine for enumerated devices. Detected devices simply wonAqt be supported. This is expected for the many I2C/SMBus devices which canAqt be detected reliably, and the ones which can always be enumerated in practice.
The i2c_client structure which is handed to the detect callback is not a real i2c_client. It is initialized just enough so that you can call i2c_smbus_read_byte_data and friends on it. DonAqt do anything else with it. In particular, calling dev_dbg and friends on it is not allowed.
5. COPYRIGHT ▲