diff options
author | Patryk Duda <patrykd@google.com> | 2024-02-13 16:28:40 +0100 |
---|---|---|
committer | Subrata Banik <subratabanik@google.com> | 2024-02-17 17:05:09 +0000 |
commit | dea474624d25dd339c081762e516175beb27b8e1 (patch) | |
tree | d3117a9d27044df7b94bba1e2b9b19b3985fac15 /tests/console/Makefile.mk | |
parent | f33a7f71c30d4a46016273564fc7d9c4b8bd6718 (diff) |
mb/google/rex: Do not power on FPMCU in ramstage
When 'reset_gpio' and 'enable_gpio' properties are defined in
overridetree.cb, the kernel will power on the FPMCU. If the device was
previously enabled the kernel will reset it.
To avoid situation in which the FPMCU is powered on and reset later we
leave the FPMCU powered off in coreboot and started by the kernel. This
is exactly what other boards do (e.g. brya).
TEST=Boot the board (e.g. karis) and make sure the FPMCU was booted once
(e.g. examine FPMCU console logs)
Change-Id: I5df8d9385be2621c02ccee2d36511a4e80ab87d1
Signed-off-by: Patryk Duda <patrykd@google.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/80457
Reviewed-by: Subrata Banik <subratabanik@google.com>
Reviewed-by: Kapil Porwal <kapilporwal@google.com>
Reviewed-by: YH Lin <yueherngl@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'tests/console/Makefile.mk')
0 files changed, 0 insertions, 0 deletions