summaryrefslogtreecommitdiffstats
path: root/arch/arm/cpu/arm926ejs/mb86r0x/reset.c
diff options
context:
space:
mode:
authorMarek Vasut <marex@denx.de>2013-04-28 14:17:45 +0000
committerStefano Babic <sbabic@denx.de>2013-05-06 10:20:33 +0200
commitdd3ecf020ec6e1932c473ef504e56a036b52bd4e (patch)
tree309a095354f1fa88015ee79171f2d2fecad8dde6 /arch/arm/cpu/arm926ejs/mb86r0x/reset.c
parent286a88cf34bcfec4a1051b5ee3553277e6c31e2e (diff)
downloadtalos-obmc-uboot-dd3ecf020ec6e1932c473ef504e56a036b52bd4e.tar.gz
talos-obmc-uboot-dd3ecf020ec6e1932c473ef504e56a036b52bd4e.zip
arm: mx23: Fix VDDMEM misconfiguration
The VDDMEM ramped up in very weird way as it was horribly misconfigured. Instead of setting up VDDMEM in one swipe, let it rise slowly the same way as VDDD and VDDA in spl_power_init.c and then only clear ILIMIT before memory gets inited. This makes sure the VDDMEM rises sanely, not jumps up and down as it did till now. The VDDMEM prior to this change did this: 2V0____ .--------2V5 | `--' 0V____| The VDDMEM now does this: 2V0_____,-----------2V5 / 0V__| Moreover, VDDIO on MX23 uses 25mV steps while MX28 uses 50mV steps, fix this difference too. Signed-off-by: Marek Vasut <marex@denx.de> Cc: Fabio Estevam <fabio.estevam@freescale.com> Cc: Otavio Salvador <otavio@ossystems.com.br> Cc: Stefano Babic <sbabic@denx.de>
Diffstat (limited to 'arch/arm/cpu/arm926ejs/mb86r0x/reset.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud