diff options
author | Tom Rini <trini@konsulko.com> | 2022-10-29 03:26:54 +0300 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2022-11-10 17:45:53 +0300 |
commit | 9244b2fda9edbc5f1c2b9b9bb827022993663d4a (patch) | |
tree | b68c9fa94af2becba060931f6fc8bc1c4870052c /README | |
parent | 77b5cc2948f5d93fe3d275302f596ffd8701a875 (diff) | |
download | u-boot-9244b2fda9edbc5f1c2b9b9bb827022993663d4a.tar.xz |
Convert CONFIG_SYS_I2C_INIT_BOARD to Kconfig
This converts the following to Kconfig:
CONFIG_SYS_I2C_INIT_BOARD
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
-rw-r--r-- | README | 11 |
1 files changed, 0 insertions, 11 deletions
@@ -1052,17 +1052,6 @@ The following options need to be configured: You should define these to the GPIO value as given directly to the generic GPIO functions. - CONFIG_SYS_I2C_INIT_BOARD - - When a board is reset during an i2c bus transfer - chips might think that the current transfer is still - in progress. On some boards it is possible to access - the i2c SCLK line directly, either by using the - processor pin as a GPIO or by having a second pin - connected to the bus. If this option is defined a - custom i2c_init_board() routine in boards/xxx/board.c - is run early in the boot sequence. - CONFIG_I2C_MULTI_BUS This option allows the use of multiple I2C buses, each of which |