summaryrefslogtreecommitdiff
path: root/board/ti/am3517crane
diff options
context:
space:
mode:
authorTom Rini <trini@ti.com>2013-08-30 16:28:46 -0400
committerTom Rini <trini@ti.com>2013-09-20 16:57:35 -0400
commit9721027aae63aab072de6ee8eae68d8e684b3af3 (patch)
tree8e04a61e54b6940f06985adf171e433511f9af27 /board/ti/am3517crane
parent5287946c0612e55f948b6ccbe2beaaffb78130ef (diff)
downloadu-boot-imx-9721027aae63aab072de6ee8eae68d8e684b3af3.zip
u-boot-imx-9721027aae63aab072de6ee8eae68d8e684b3af3.tar.gz
u-boot-imx-9721027aae63aab072de6ee8eae68d8e684b3af3.tar.bz2
am335x_evm: am33xx_spl_board_init function and scale core frequency
Add a am33xx_spl_board_init (and enable the PMICs) that we may see, depending on the board we are running on. In all cases, we see if we can rely on the efuse_sma register to tell us the maximum speed. In the case of Beaglebone White, we need to make sure we are on AC power, and are on later than rev A1, and then we can ramp up to the PG1.0 maximum of 720Mhz. In the case of Beaglebone Black, we are either on PG2.0 that supports 1GHz or PG2.1. As PG2.0 may or may not have efuse_sma set, we cannot rely on this probe. In the case of the GP EVM, EVM SK and IDK we need to rely on the efuse_sma if we are on PG2.1, and the defaults for PG1.0/2.0. Signed-off-by: Tom Rini <trini@ti.com>
Diffstat (limited to 'board/ti/am3517crane')
0 files changed, 0 insertions, 0 deletions