summaryrefslogtreecommitdiff
path: root/src/soc/intel/alderlake/gpio.c
diff options
context:
space:
mode:
authorNick Vaccaro <nvaccaro@google.com>2021-10-12 17:26:52 -0700
committerNick Vaccaro <nvaccaro@google.com>2021-12-07 00:17:27 +0000
commitb6f29c9bf47724168a58c196aa1d2ec65302731e (patch)
treeb99e0d56d9dbfc04c9c6a62c0674e00328623e9c /src/soc/intel/alderlake/gpio.c
parenteb3260b9715842d5abda28ac920afde696afd88c (diff)
soc/intel/common: add generic gpio lock mechanism
For added security, there are some gpios that an SoC will want to lock once initially configured, such as gpios attached to non-host (x86) controllers, so that they can't be recofigured at a later point in time by rogue code. Likewise, a mainboard may have some gpios connected to secure busses and/or devices that they want to protect from being changed post initial configuration. This change adds a generic gpio locking mechanism that allows the SoC to export a list of GPIOs to be locked down and allows the mainboard to export a list of GPIOs that it wants locked down once initialization is complete. Use the SOC_INTEL_COMMON_BLOCK_SMM_LOCK_GPIO_PADS Kconfig option to enable this feature. BUG=b:201430600 TEST='emerge-brya coreboot chromeos-bootimage', flash and verify brya0 boots successfully to kernel. Signed-off-by: Nick Vaccaro <nvaccaro@google.com> Change-Id: I42979fb89567d8bcd9392da4fb8c4113ef427b14 Reviewed-on: https://review.coreboot.org/c/coreboot/+/58351 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
Diffstat (limited to 'src/soc/intel/alderlake/gpio.c')
0 files changed, 0 insertions, 0 deletions