5 comments:
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
hmm... i'm not sure i followed that.
are you basically trying to distinguish between the case
where fw_config hasn't been set and assumed to be 0
vs. explicitly set to 0? we get away with that because
in most? cases the sub-fields are defined so that a value
of 0 means no device.
please update Documentation/lib/fw_config.md to match.
can we simply start with
fw_config_value = UNDEFINED_FW_CONFIG
?
Patch Set #3, Line 75: bool fw_config_probe(const struct fw_config *match)
is there ever a case where we would still want to use this version?
Patch Set #3, Line 132: fw_config_probe
fw_config_probe_nodefault
To view, visit change 47956. To unsubscribe, or for help writing mail filters, visit settings.