summaryrefslogtreecommitdiff
path: root/src/mainboard/google/rush/chromeos.c
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2014-08-05 13:30:38 -0500
committerPatrick Georgi <pgeorgi@google.com>2015-03-25 22:31:54 +0100
commit44e5e4ce73153ae17442daae11e89b40815a4c90 (patch)
treea6ded87289b1512e1db0cb93107a5372f3bda75f /src/mainboard/google/rush/chromeos.c
parent5d98f51b254f665e385a875798be09451d2a47d9 (diff)
downloadcoreboot-44e5e4ce73153ae17442daae11e89b40815a4c90.tar.xz
tegra132: use pre-existing reset API
coreboot already has a reset API. Utilize it by selecting HAVE_HARD_RESET. The tegra132 boards have to provide the hard_reset() implementation as that involves board-specific bits. The tegra132 code then provides a cpu_reset() routine that just promotes that call to a hard_reset(). For the existing tegra132 boards remove the unnecessary files from the build. BUG=chrome-os-partner:30784 BRANCH=None TEST=Ensured hard_reset() does something on Ryu. Change-Id: I6d5aa928fec95b361175e35e0a26812829ffdfc3 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: 31edd4ff7486ded87d2525cd360d48959b6aef7c Original-Change-Id: I1e1b014062dafb5d81fb9da40006c5405073a95d Original-Signed-off-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/211131 Original-Reviewed-by: Tom Warren <twarren@nvidia.com> Original-Reviewed-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: http://review.coreboot.org/8911 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'src/mainboard/google/rush/chromeos.c')
0 files changed, 0 insertions, 0 deletions