From Linux i2c Wiki
Linux i2c Subsystem
This is the home of the Linux i2c subsystem.
Theory of operation
- Driver Architecture
- I2C protocol summary
- SMBus protocol summary
- 10-bit addresses information
- /dev interface documentation
- I2C adapter functionalities
- I2C bus multiplexing
- Linux 2.6 I2C development FAQ
- Conventions for use of fault codes in the I2C/SMBus stack
- How to instantiate I2C devices
- Writing kernel drivers for I2C or SMBus devices
- Upgrading I2C chip drivers to the 2.6 driver model
- i2c-stub, a fake I2C/SMBus master driver for testing purpose
User-space tools for I2C/SMBus are being maintained in the i2c-tools git tree. Released versions can be downloaded from https://www.kernel.org/pub/software/utils/i2c-tools/.
Work in progress
- Legacy binding model code is being removed. Most of it is gone already, with the exception of the
i2c_drivermethods which are still used by three macintosh drivers (therm_pm72, therm_windtunnel and sound/ppc/keywest.) As soon as these remaining drivers are converted to the standard binding model, these methods can be removed.
- Fix the I2C core to report a proper OF Modalias uevent.
- The i2c-dev driver needs to be ported to the new i2c device driver binding model. See this discussion and this bug report.
- i2c_adapter.retries and i2c_adapter.timeout need to be clarified. Their original intent was not necessarily good nor clear, but they could still be useful, if fault codes returned by adapter drivers are also clarified.
- Exclusive access to bus segments or devices. The former can partly be done in-kernel since version 3.6 (i2c_lock_adapter / __i2c_transfer / i2c_unlock_adapter), but not using SMBus-level functions. Also the user-space case mentioned here is not supported yet.
- The kernel should be able to prevent probing of specific I2C bus segments from user-space. Either by exposing the class flags and hoping user-space will pay attention and be fair, or by defining one more class flag for user-space access and enforcing it.