Lines Matching +full:driver +full:- +full:bar
1 .. _dt-writing-bindings:
21 Zephyr aims for devicetree :ref:`dt-source-compatibility`. Therefore, if there
24 justify any Zephyr-specific divergences.
28 - There is an existing binding in the mainline Linux kernel. See
32 - Your hardware vendor provides an official binding outside of the Linux
48 https://docs.kernel.org/devicetree/bindings/writing-bindings.html
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
58 ``vnd,foo-bar.yaml``.
63 All recommendations in :ref:`dt-bindings-default` are requirements when
77 .. code-block:: yaml
84 .. code-block:: yaml
92 multi-line descriptions. This in turn makes these long strings
100 uppercase. Use dashes (``-``) instead of underscores. (The one exception to
101 this rule is if you are replicating a well-established binding from somewhere
108 <dt-important-props>` properties.
110 - If your device is manufactured by a specific vendor, then its compatible
114 :zephyr_file:`dts/bindings/vendor-prefixes.txt`, you must use that vendor
117 - If your device is not manufactured by a specific hardware vendor, do **not**
123 - Do not submit additions to Zephyr's :file:`dts/bindings/vendor-prefixes.txt`
126 a device driver handling that compatible.
129 :file:`dts/bindings/vendor-prefixes.txt` file to any directory in your
134 - We sometimes synchronize Zephyr's vendor-prefixes.txt file with the Linux
137 - If your binding is describing an abstract class of hardware with Zephyr
141 .. _dt-bindings-default-rules:
162 Driver developers should use their best judgment as to whether a value can be
165 - delays that would be different only under unusual conditions
167 - configuration for devices that have a standard initial configuration (such as
169 - defaults which match the vendor-specified power-on reset value
174 .. code-block:: yaml
177 cs-interval:
183 hold-time-ms:
194 .. code-block:: yaml
205 bar:
208 description: bar size; default is 2
223 - Zephyr-specific extensions to bindings we share with upstream Linux. One
224 example is the ``zephyr,vref-mv`` ADC channel property which is common to ADC
225 controllers defined in :zephyr_file:`dts/bindings/adc/adc-controller.yaml`.
227 Zephyr-specific extensions are marked as such with the prefix.
229 - Configuration values that are specific to a Zephyr device driver. One example
230 is the ``zephyr,lazy-load`` property in the :dtcompatible:`ti,bq274xx`
232 configuration language, it is Zephyr's only mechanism for configuring driver
239 :dtcompatible:`zephyr,ipc-openamp-static-vrings`. In this case, it's permitted