schemas: core: Introduce "fail-needs-probe" status #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some components can not be absolutely determined to exist on a given device when the device tree is written or compiled. However such components can either be probed using I2C transfers, or determined to exist based on runtime information, such as GPIO or ADC strappings, or extra information passed over from boot firmware or read from some flash chip.
Such an arrangement of components are commonly seen in the consumer electronics world, where the manufacturer will swap out electrically compatible components due to inventory or price constraints. These components are commonly attached to the baseboard with a standardized ribbon cable, and the ribbon cable may contain strapping resistors if necessary.
Introduce a new "fail-needs-probe" status string that corresponds to devices or components that "might" exist. (The term "component" shall be used to avoid confusion with the actual "complete device".) This status signals that the implementation needs to do extra probing to determine the exact state of the component.