diff options
author | Vincent Palatin <vpalatin@chromium.org> | 2017-03-15 15:37:51 +0100 |
---|---|---|
committer | Duncan Laurie <dlaurie@chromium.org> | 2017-03-15 19:54:47 +0100 |
commit | 08824ec8d4d68ffa9edf1212e7f7e281da4d779f (patch) | |
tree | 5e3b91e1321a4a7a2456b9161e4b0b7fede8344a /payloads/Kconfig | |
parent | 57e9e3be5fe3a68c8ccedc85e673f091aaf8ff58 (diff) |
google/eve: Update MCU GPIOs configuration
Keep the BOOT0 pin triggering the MCU bootloader as an input,
so the Servo debug board doesn't have to fight with the PCH to program
it, the net already has an external pull-down to ensure that the MCU is
in normal mode at boot.
By default, do not drive the FP sensor reset from the PCH, the MCU is
now managing the reset line (but the PCH still has a connection on the
current boards).
BRANCH=none
BUG=b:36025702
TEST=manual testing, program the MCU through a Servo v2 board, and use
the FP sensor through the MCU and verify it is not stuck under reset.
Change-Id: I19113b5d78013d0ab6ec5a72c6f71dd4c67a88e8
Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-on: https://review.coreboot.org/18830
Tested-by: build bot (Jenkins)
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Diffstat (limited to 'payloads/Kconfig')
0 files changed, 0 insertions, 0 deletions