nyan: Initialize the ARM architectural timer in the RAM stage.
This could be done much sooner in the generic timer initialization, but it's not used by coreboot and, if it's done in the RAM stage, it would be updateable when using early firmware selection. BUG=None TEST=Before setting up these timers, the Linux kernel behaved very poorly and would hang, trip the watchdog timer, and/or otherwise crash. After setting them up those problems were no longer noticeable. BRANCH=None Change-Id: I26e9dc6d5090a67c775e67f96cee13fad582803e Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://chromium-review.googlesource.com/174836 Reviewed-by: Gabe Black <gabeblack@chromium.org> Commit-Queue: Gabe Black <gabeblack@chromium.org> Tested-by: Gabe Black <gabeblack@chromium.org>
This commit is contained in:
parent
25a91fcf7e
commit
581f592c12
1 changed files with 2 additions and 0 deletions
|
|
@ -21,6 +21,7 @@
|
|||
#include <device/device.h>
|
||||
#include <boot/coreboot_tables.h>
|
||||
#include <soc/addressmap.h>
|
||||
#include <soc/clock.h>
|
||||
#include <soc/nvidia/tegra124/gpio.h>
|
||||
#include <soc/nvidia/tegra124/pmc.h>
|
||||
|
||||
|
|
@ -126,6 +127,7 @@ static void mainboard_init(device_t dev)
|
|||
{
|
||||
setup_pinmux();
|
||||
setup_kernel_info();
|
||||
clock_init_arm_generic_timer();
|
||||
}
|
||||
|
||||
static void mainboard_enable(device_t dev)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue