Skip to content

Commit e5974f7

Browse files
ulfalizergalak
authored andcommitted
dts: binding-template.yaml: Fix 'parent/child: bus:' description
'child: bus:' should be in the binding for the bus node, and 'parent: bus:' in the binding for devices that appear on the bus. The description accidentally swapped them. Fix it. Fixes: #18821 Signed-off-by: Ulf Magnusson <[email protected]>
1 parent 0d766c6 commit e5974f7

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

dts/bindings/binding-template.yaml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,17 +16,17 @@ inherits:
1616
!include other.yaml # or [other1.yaml, other2.yaml]
1717

1818
# If the node describes a bus, then the bus type should be given, like below
19-
parent:
19+
child:
2020
bus: <string describing bus type, e.g. "i2c">
2121

2222
# If the node appears on a bus, then the bus type should be given, like below.
2323
#
2424
# When looking for a binding for a node, the code checks if the binding for the
25-
# parent node contains 'parent: bus: <bus type>'. If it does, then only
26-
# bindings with a matching 'child: bus: <bus type>' are considered. This allows
27-
# the same type of device to have different bindings depending on what bus it
25+
# parent node contains 'child: bus: <bus type>'. If it does, then only bindings
26+
# with a matching 'parent: bus: <bus type>' are considered. This allows the
27+
# same type of device to have different bindings depending on what bus it
2828
# appears on.
29-
child:
29+
parent:
3030
bus: <string describing bus type, e.g. "i2c">
3131

3232
# 'sub-node' is used to simplify cases where a node has children that can all

0 commit comments

Comments
 (0)