diff options
| author | Guennadi Liakhovetski <lg@denx.de> | 2009-02-13 09:23:36 +0100 |
|---|---|---|
| committer | Heiko Schocher <hs@denx.de> | 2009-02-14 10:00:51 +0100 |
| commit | e7de18afe8ecf96a51ef981d06066eeb6b1254e7 (patch) | |
| tree | 7bea693fa69e5ed7cab9d1fe7ae96c6c31ece3eb /m68k_config.mk | |
| parent | 15208ac9eae1c340c4bc11f70cbf5c9da78a57ba (diff) | |
| download | u-boot-imx-e7de18afe8ecf96a51ef981d06066eeb6b1254e7.zip u-boot-imx-e7de18afe8ecf96a51ef981d06066eeb6b1254e7.tar.gz u-boot-imx-e7de18afe8ecf96a51ef981d06066eeb6b1254e7.tar.bz2 | |
i.MX31: Start the I2C clock on driver initialisation
i.MX31 powers on with most clocks running, so, after a power on this explicit
clock start up is not required. However, as Linux boots it disables most clocks
to save power. This includes the I2C clock. If we then soft reboot from Linux
the I2C clock stays off. This breaks the phycore, which has its environment in
I2C EEPROM. Fix the problem by explicitly starting the clock in I2C driver
initialisation routine.
Signed-off-by: Guennadi Liakhovetski <lg@denx.de>
Ack-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Diffstat (limited to 'm68k_config.mk')
0 files changed, 0 insertions, 0 deletions