Skip to content

Commit 49ed686

Browse files
krzkrobherring
authored andcommitted
docs: dt: writing-bindings: Rephrase typical fallback (superset) usage
When speaking about compatibles for new devices comparing to "prior implementations", usually we expect new device to come with more features, thus logically it is a superset, not subset, of "prior implementations". Suggested-by: Conor Dooley <conor@kernel.org> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/r/20250707095019.66792-4-krzysztof.kozlowski@linaro.org Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
1 parent fd8fca2 commit 49ed686

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

Documentation/devicetree/bindings/writing-bindings.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ Properties
4040
==========
4141

4242
- DO make 'compatible' properties specific. DON'T use wildcards in compatible
43-
strings. DO use fallback compatibles when devices are the same as or a subset
44-
of prior implementations. DO add new compatibles in case there are new
45-
features or bugs.
43+
strings. DO use fallback compatibles when devices are the same as or a
44+
superset of prior implementations. DO add new compatibles in case there are
45+
new features or bugs.
4646

4747
- DO use a vendor prefix on device-specific property names. Consider if
4848
properties could be common among devices of the same class. Check other

0 commit comments

Comments
 (0)