On 31 March 2015 at 21:17, Simon Glass sjg@chromium.org wrote:
On 31 March 2015 at 10:57, Przemyslaw Marczak p.marczak@samsung.com wrote:
Signed-off-by: Przemyslaw Marczak p.marczak@samsung.com Cc: Masahiro Yamada yamada.masahiro@socionext.com Cc: Mike Frysinger vapier@gentoo.org Cc: Simon Glass sjg@chromium.org Cc: Heiko Schocher hs@denx.de
Changes V2:
- add i2c uclass description
Changes v3:
- Kconfig: i2c-uclass: fix help message
drivers/i2c/Kconfig | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig index 692810d..c83a984 100644 --- a/drivers/i2c/Kconfig +++ b/drivers/i2c/Kconfig @@ -2,16 +2,13 @@ config DM_I2C bool "Enable Driver Model for I2C drivers" depends on DM help
Enable driver model for I2C. This SPI flash interface(spi_flash_probe(), spi_flash_write(), etc.) is thenimplemented by the SPI flash uclass. There is one standardSPI flash driver which knows how to probe most chipssupported by U-Boot. The uclass interface is defined ininclude/spi_flash.h, but is currently fully compatiblewith the old interface to avoid confusion and duplicationduring the transition parent. SPI and SPI flash must beenabled together (it is not possible to use driver modelfor one and not the other).
Enable driver model for I2C. The I2C uclass interface: probe, read,write and speed, is implemented with the bus drivers operations,which provide methods for bus setting and data transfer. Each chipdevice (bus child) info is kept as parent platdata. The interfaceis defined in include/i2c.h. When i2c bus driver supports the i2cuclass, but the device drivers not, then DM_I2C_COMPAT config canbe used as compatibility layer.config DM_I2C_COMPAT bool "Enable I2C compatibility layer" -- 1.9.1
Acked-by: Simon Glass sjg@chromium.org
Applied to u-boot-dm/next, thanks!