summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-uniphier/ph1-ld4/clkrst_init.c
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.m@jp.panasonic.com>2015-02-27 02:26:52 +0900
committerMasahiro Yamada <yamada.m@jp.panasonic.com>2015-03-01 00:02:40 +0900
commitd3384bf77eb9a202d8218e1fe1da2f21af034aa7 (patch)
tree9cad48dc39695069846b887d77a86dc12486866f /arch/arm/mach-uniphier/ph1-ld4/clkrst_init.c
parent198a97a6abe7090109002baea0d2cb46070955aa (diff)
downloadtalos-obmc-uboot-d3384bf77eb9a202d8218e1fe1da2f21af034aa7.tar.gz
talos-obmc-uboot-d3384bf77eb9a202d8218e1fe1da2f21af034aa7.zip
ARM: UniPhier: reset NAND core in SPL for non-NAND boot mode
For all the UniPhier SoCs so far, the reset signal of the NAND core is automatically deasserted after the PLL gets stabled. (The bit 2 of SC_RSTCTRL is default to one.) This causes a fatal problem on the NAND controller of PH1-LD4. For that SoC, the NAND I/O pins are not set up yet at the power-on reset except the NAND boot mode. As a result, the NAND controller begins automatic device scanning with wrong I/O pins and finally hangs up. Actually, U-Boot dies after printing "NAND:" on the console unless the boot mode latch detected the NAND boot mode. To work around this problem, reset the NAND core in SPL for non-NAND boot modes. If CONFIG_NAND_DENALI is enabled, the reset signal is deasserted again in U-Boot proper. At this time, I/O pins have been correctly set up, the device scanning should succeed. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Diffstat (limited to 'arch/arm/mach-uniphier/ph1-ld4/clkrst_init.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud