Kconfig: i2c: fix help message related to dm i2c

Signed-off-by: Przemyslaw Marczak <p.marczak@samsung.com>
Acked-by: Simon Glass <sjg@chromium.org>

diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig
index 692810d057e4d3e57d6d570d0fa8271f7f6ca960..c83a98459ac262b9f020a1c57252ef7b23577755 100644 (file)
--- 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"