summaryrefslogtreecommitdiff
path: root/3rdparty
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2017-03-07 18:59:19 -0800
committerDuncan Laurie <dlaurie@chromium.org>2017-03-08 19:07:29 +0100
commit03df460af5f73bb2fbbe23caff5f0bb646e8f756 (patch)
tree6338da02eb812ece309115eb9f145d368184d350 /3rdparty
parentb854ae26494ca7cdb7a6804c7319f669e6c713dd (diff)
downloadcoreboot-03df460af5f73bb2fbbe23caff5f0bb646e8f756.tar.xz
google/eve: Configure GPIOs for new board
A new board revision is making use of two previously unused GPIOs to drive BOOT/RESET pins to an on-board MCU. The reset pin is open drain so it is set as input by default, and the boot pin is driven low by default. Since these are UART0 pins they also need to be set up again after executing FSP-S as it will change them back to native mode pins. BUG=b:36025702 BRANCH=none TEST=manual testing on reworked board, toggling GPIOs to put the MCU into programming mode. Change-Id: Id6f0ef2f863bc1e873b58e344446038786b59d25 Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://review.coreboot.org/18661 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins)
Diffstat (limited to '3rdparty')
0 files changed, 0 insertions, 0 deletions