summaryrefslogtreecommitdiff
path: root/lib_avr32/bootm.c
diff options
context:
space:
mode:
authorWayne Zou <b36644@freescale.com>2011-09-06 13:43:00 +0800
committerWayne Zou <b36644@freescale.com>2011-09-06 14:20:30 +0800
commit3022105ecdeec0c6b10199bd1e1bc7e0ba9f0cee (patch)
treedaeb2f6ddf442b72d2681d40ecf8bb28f7eace6c /lib_avr32/bootm.c
parentaac855885f336cb9a7ed570247901c0704570871 (diff)
downloadu-boot-imx-3022105ecdeec0c6b10199bd1e1bc7e0ba9f0cee.zip
u-boot-imx-3022105ecdeec0c6b10199bd1e1bc7e0ba9f0cee.tar.gz
u-boot-imx-3022105ecdeec0c6b10199bd1e1bc7e0ba9f0cee.tar.bz2
ENGR00156098 mx53_smd/mx53_loco: DA9053 I2C SDA stuck low issue on bootup
For DA9053 I2C SDA stuck low issue: the I2C block in DA9053 may not correctly receive a Power On Reset and device is in unknown state during start-up. The only way to get the chip into known state before any communication with the Chip via I2C is to dummy clock the I2C and bring it in a state where I2C can communicate. Dialog suggested to provide 9 clock on SCL. Dialog don't know the exact reason for the fault and assume it is because some random noise or spurious behaviour. This has to been done in host platform specific I2C driver during start-up when the I2C is being configured at platform level to supply with dummy 9 clock on SCL. Dialog I2C driver has no control to provide dummy 9 clock on SCL. Signed-off-by: Wayne Zou <b36644@freescale.com>
Diffstat (limited to 'lib_avr32/bootm.c')
0 files changed, 0 insertions, 0 deletions