summaryrefslogtreecommitdiff
path: root/src/mainboard/google/brya/variants/baseboard/include
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@google.com>2021-05-20 22:47:02 -0700
committerTim Wawrzynczak <twawrzynczak@chromium.org>2021-05-24 16:55:39 +0000
commit7f6ae79280eabce22f1df3c858617c6e890e3594 (patch)
tree7b15e6c75896b9c6f8b987db890bf232d5d6dd66 /src/mainboard/google/brya/variants/baseboard/include
parent665891e3a8daafe04494fd4ac2dba49a99840a3a (diff)
device: Consider fw_config probing in `is_dev_enabled()`
With the introduction of fw_config support in coreboot, it is possible for mainboards to control the state of a device (on/off) in ramstage using fw_config probe conditions. However, the device tree in immutable in all other stages and hence `is_dev_enabled()` does not really reflect the true state as in ramstage. This change adds a call to `fw_config_probe_dev()` in `is_dev_enabled()` when device tree is immutable (by checking DEVTREE_EARLY) to first check if device is disabled because of device probe conditions. If so, then it reports device as being disabled. Else, dev->enabled is used to report the device state. This allows early stages (bootblock, romstage) to use `is_dev_enabled()` to get the true state of the device by taking probe conditions into account and eliminates the need for each caller to perform their own separate probing. Change-Id: Ifede6775bda245cba199d3419aebd782dc690f2c Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/54752 Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org> Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Reviewed-by: EricR Lai <ericr_lai@compal.corp-partner.google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/google/brya/variants/baseboard/include')
0 files changed, 0 insertions, 0 deletions