summaryrefslogtreecommitdiff
path: root/doc/feature-removal-schedule.txt
diff options
context:
space:
mode:
authorAnson Huang <b20788@freescale.com>2011-12-13 14:48:51 +0800
committerAnson Huang <b20788@freescale.com>2011-12-20 20:14:54 +0800
commit3568732ec72b2d792aeb3f780b0d1f32d86f36ec (patch)
tree6627be5c2a0b4baa04f79c4a9cf7932b8eaccf3f /doc/feature-removal-schedule.txt
parent14dab831e8e93a7ee03de2c7cca00d4b81e00cdc (diff)
downloadu-boot-imx-3568732ec72b2d792aeb3f780b0d1f32d86f36ec.zip
u-boot-imx-3568732ec72b2d792aeb3f780b0d1f32d86f36ec.tar.gz
u-boot-imx-3568732ec72b2d792aeb3f780b0d1f32d86f36ec.tar.bz2
ENGR00160621 [MX6]Workaround for reset issue
Add workaround for POR/wdog reset issue, we need to do a CORE LDO reset everytime POR/wdog reset, otherwise kernel will crash or hang when we booting more than 2 cores. Root cause is still under investigation, it is analog/power related issue, may take long time to identify the root cause, we need to add workaround to make function ready first. The flow of workaround is as below: 1. Check CORE LDO reset flag, currently stored in SNVS_LPGPR[0]; 2. If it is there, clear it, go on boot up system; If not, Set the flag, configure wdog to timeout in 0.5 seconds, then disable CORE LDO and wait for wdog timeout; This workaround will bring 0.5~1 seconds delay of booting. Signed-off-by: Anson Huang <b20788@freescale.com>
Diffstat (limited to 'doc/feature-removal-schedule.txt')
0 files changed, 0 insertions, 0 deletions