diff options
author | Tim Wawrzynczak <twawrzynczak@chromium.org> | 2020-11-24 10:33:00 -0700 |
---|---|---|
committer | Tim Wawrzynczak <twawrzynczak@chromium.org> | 2020-12-11 16:59:35 +0000 |
commit | 473bc8c892c3acf6b1a222a09a53d5a190611bba (patch) | |
tree | 581540c8b2feabed18b775337b585c5ac78ddccb /src/lib/asan.c | |
parent | 5258f4f93e2d23e839765349a844d798f054da6a (diff) | |
download | coreboot-473bc8c892c3acf6b1a222a09a53d5a190611bba.tar.xz |
fw_config: Use UNDEFINED_FW_CONFIG to mean unprovisioned
A mainboard might want to configure some things differently when a
device is in an unprovisioned state. In the case when fw_config comes
from the Chromium EC, an unprovisioned device will not have a FW_CONFIG
tag in its CBI. This patch will set the fw_config value to
UNDEFINED_FW_CONFIG in the case of an error retrieving the value, as
well as adding a function, `fw_config_is_provisioned()` to indicate the
provisioning status.
BUG=none
TEST=remove fw_config from chromium EC CBI, add code to mainboard to
print return value of fw_config_is_provisioned() (`0`), add
fw_config back to CBI, run same test and see `1`.
Signed-off-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
Change-Id: Ib3046233667e97a5f78961fabacbeb3099b3d442
Reviewed-on: https://review.coreboot.org/c/coreboot/+/47956
Reviewed-by: Furquan Shaikh <furquan@google.com>
Reviewed-by: Nick Vaccaro <nvaccaro@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/lib/asan.c')
0 files changed, 0 insertions, 0 deletions