Lines Matching full:binding

22 is an existing binding for your device in an authoritative location, you should
23 try to replicate its properties when writing a Zephyr binding, and you must
28 - There is an existing binding in the mainline Linux kernel. See
32 - Your hardware vendor provides an official binding outside of the Linux
55 - For example, a binding for compatible ``vnd,foo`` must be named ``vnd,foo.yaml``.
56 - If the binding is bus-specific, you can append the bus to the file name;
57   for example, if the binding YAML has ``on-bus: bar``, you may name the file
64 submitting the binding.
101 this rule is if you are replicating a well-established binding from somewhere
113   If your binding describes hardware with a well known vendor from the list in
125   binding and a devicetree using the vendor prefix, and should ideally include
137 - If your binding is describing an abstract class of hardware with Zephyr
146 In any case where ``default:`` is used in a devicetree binding, the
156 There is a risk in using ``default:`` when the value in the binding may be
158 defaulting the capacity of the connected power cell in a charging IC binding
226   This channel binding is partially shared with an analogous Linux binding, and
231   binding. Though devicetree in general is a hardware description and
241 binding.