]> git.sur5r.net Git - u-boot/commit
TI OMAP3 Use arm init sequence to initialize i2c
authorTom Rix <Tom.Rix@windriver.com>
Tue, 29 Sep 2009 14:19:49 +0000 (10:19 -0400)
committerTom Rix <Tom.Rix@windriver.com>
Sun, 4 Oct 2009 15:51:31 +0000 (10:51 -0500)
commit54737ba17a8444175fa94d758b83f120bbea3351
treeb608a76df86de828d25674ccff835c13ebee3c81
parent67c3d9fb36bd0e66bd5cbf2719564e01f6459433
TI OMAP3 Use arm init sequence to initialize i2c

This changes fixes an early i2c error.

It appears that I2C is working because once a read or write
error is detected, the omap24xx_i2c driver calls i2c_init
inside its error handling check.

While it is ok to attempt error handling this way, the boards
must not depend on this side effect to initialize it's i2c.

Instead of explicitly calling i2c_init for every board, use
the generic arm initialization in lib_arm/board.c. By defining
the config variable CONFIG_HARD_I2C, the omap3 i2c initialization
is included in the init_sequence table.

Run tested on Beagle.
Compile tested on the omap3's

Signed-off-by: Tom Rix <Tom.Rix@windriver.com>
Acked-by: Dirk Behme <dirk.behme@googlemail.com>
include/configs/devkit8000.h
include/configs/omap3_beagle.h
include/configs/omap3_evm.h
include/configs/omap3_overo.h
include/configs/omap3_pandora.h
include/configs/omap3_zoom1.h
include/configs/omap3_zoom2.h