Tim Wawrzynczak uploaded patch set #4 to this change.
fw_config: Default to undefined fw_config value
In order to support the use case of leaving runtime probing of
multi-sourced peripherals to the payload (or beyond) before a device is
provisioned, this change defaults the fw_config value to a magic
undefined value when a valid value can't be located.
In addition, the `fw_config_probe` function is modified to return true
if fw_config is undefined.
A new function `fw_config_probe_nodefault` is also added, which will
return false when fw_config is undefined. This can be useful for example
when fw_config probing is used to configure GPIOs differently; when
fw_config is undefined, it may be preferable to leave the GPIOs
configured in whatever previous state they had been in.
Signed-off-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
Change-Id: Ib3046233667e97a5f78961fabacbeb3099b3d442
---
M Documentation/lib/fw_config.md
M src/include/fw_config.h
M src/lib/fw_config.c
3 files changed, 67 insertions(+), 13 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/56/47956/4
To view, visit change 47956. To unsubscribe, or for help writing mail filters, visit settings.