summaryrefslogtreecommitdiff
path: root/include/configs/x86-chromebook.h
diff options
context:
space:
mode:
authorNikita Kiryanov <nikita@compulab.co.il>2016-02-19 19:19:49 +0200
committerTom Rini <trini@konsulko.com>2016-02-24 18:44:09 -0500
commit43e568c4ae9a35e2458737c7d995b183e21b8a6f (patch)
treea76e705274d8cc2bce3ca9c6f7162b8bda0a7ae9 /include/configs/x86-chromebook.h
parente038e2a89b213640143d6ab1bbf73b134292e4dc (diff)
downloadu-boot-imx-43e568c4ae9a35e2458737c7d995b183e21b8a6f.zip
u-boot-imx-43e568c4ae9a35e2458737c7d995b183e21b8a6f.tar.gz
u-boot-imx-43e568c4ae9a35e2458737c7d995b183e21b8a6f.tar.bz2
arm: am437x: cm-t43: set MPU and CORE voltages on boot
During boot, U-Boot raises the CPU frequency but the CORE and MPU regulators are not updated. This is not a problem in cold boot since the default values that the pmic outputs are correct, but if Linux were to switch the module to a low power OPP, the new voltage values will be retained after a reboot and the module will likely hang once U-Boot raises the CPU frequency back up. Set both CORE and MPU regulators to to 1.1V on boot. Cc: Tom Rini <trini@konsulko.com> Cc: Albert Aribaud <albert.u.boot@aribaud.net> Cc: Igor Grinberg <grinberg@compulab.co.il> Signed-off-by: Nikita Kiryanov <nikita@compulab.co.il> Reviewed-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'include/configs/x86-chromebook.h')
0 files changed, 0 insertions, 0 deletions