diff options
author | Simon Glass <sjg@chromium.org> | 2017-05-12 21:09:49 -0600 |
---|---|---|
committer | Heiko Schocher <hs@denx.de> | 2017-05-15 06:17:09 +0200 |
commit | eb5ba3aefdf0f6cbd61684eeb61428f11fa7613c (patch) | |
tree | 89887dacbe56dc1b3cef048ce08c2ec3ef8f955b /README | |
parent | 22f3368e71321db1e0e15dfbf54b052367890ec7 (diff) | |
download | u-boot-eb5ba3aefdf0f6cbd61684eeb61428f11fa7613c.tar.gz |
i2c: Drop use of CONFIG_I2C_HARD
This option is pretty old. It predates CONFIG_SYS_I2C which is itself
deprecated in favour of driver model. Disable it for all boards.
Also drop I2C options which depend on this.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
-rw-r--r-- | README | 17 |
1 files changed, 2 insertions, 15 deletions
@@ -2213,22 +2213,9 @@ The following options need to be configured: - approved multibus support - better i2c mux support - ** Please consider updating your I2C driver now. ** + ** CONFIG_HARD_I2C is now being removed ** - These enable legacy I2C serial bus commands. Defining - CONFIG_HARD_I2C will include the appropriate I2C driver - for the selected CPU. - - This will allow you to use i2c commands at the u-boot - command line (as long as you set CONFIG_CMD_I2C in - CONFIG_COMMANDS) and communicate with i2c based realtime - clock chips. See common/cmd_i2c.c for a description of the - command line interface. - - CONFIG_HARD_I2C selects a hardware I2C controller. - - There are several other quantities that must also be - defined when you define CONFIG_HARD_I2C. +----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 |