Signed-off-by: Przemyslaw Marczak <p.marc...@samsung.com>
Cc: Masahiro Yamada <yamada.masah...@socionext.com>
Cc: Mike Frysinger <vap...@gentoo.org>
Cc: Simon Glass <s...@chromium.org>
Cc: Heiko Schocher <h...@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 then
-         implemented by the SPI flash uclass. There is one standard
-         SPI flash driver which knows how to probe most chips
-         supported by U-Boot. The uclass interface is defined in
-         include/spi_flash.h, but is currently fully compatible
-         with the old interface to avoid confusion and duplication
-         during the transition parent. SPI and SPI flash must be
-         enabled together (it is not possible to use driver model
-         for 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 chip
+         device (bus child) info is kept as parent platdata. The interface
+         is defined in include/i2c.h. When i2c bus driver supports the i2c
+         uclass, but the device drivers not, then DM_I2C_COMPAT config can
+         be used as compatibility layer.
 
 config DM_I2C_COMPAT
        bool "Enable I2C compatibility layer"
-- 
1.9.1

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to