i2c: Finish dropping use of CONFIG_I2C_HARD
Drop use of this long-deprecated option.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
diff --git a/README b/README
index 86f0814..11fa84c 100644
--- a/README
+++ b/README
@@ -2204,7 +2204,9 @@
If you do not have i2c muxes on your board, omit this define.
-- Legacy I2C Support: CONFIG_HARD_I2C
+----under removal:
+
+- Legacy I2C Support: CONFIG_SOFT_I2C
NOTE: It is intended to move drivers to CONFIG_SYS_I2C which
provides the following compelling advantages:
@@ -2213,14 +2215,12 @@
- approved multibus support
- better i2c mux support
- ** CONFIG_HARD_I2C is now being removed **
+ ** CONFIG_SOFT_I2C is now being removed **
-----under removal:
-
- In both cases you will need to define CONFIG_SYS_I2C_SPEED
- to be the frequency (in Hz) at which you wish your i2c bus
- to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie
- the CPU's i2c node address).
+ With CONFIG_SOFT_I2C you will need to define
+ CONFIG_SYS_I2C_SPEED to be the frequency (in Hz) at which you
+ wish your i2c bus to run and CONFIG_SYS_I2C_SLAVE to be the
+ address of this node (ie the CPU's i2c node address).
Now, the u-boot i2c code for the mpc8xx
(arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node