Lines Matching full:like
18 like this:
26 Descriptions which span multiple lines (like this) are OK,
45 # If the node describes bus hardware, like an SPI bus controller
46 # on an SoC, use 'bus:' to say which one, like this:
49 # If the node instead appears as a device on a bus, like an external
50 # SPI memory chip, use 'on-bus:' to say what type of bus, like this.
51 # Like 'compatible', this key also influences the way nodes match
75 :ref:`dt-binding-compat`. It should look like this in a binding file:
120 contain. For example, a binding for a UART peripheral might look something like
149 standard properties, like :ref:`reg <dt-important-props>`, whose meaning is
185 # Describes a property like 'current-speed = <115200>;'. We pretend that
192 # Describes an optional property like 'keys = "foo", "bar";'
197 # Describes an optional property like 'maximum-speed = "full-speed";'
208 # Describes an optional property like 'resolution = <16>;'
384 For example, this feature is not meant for cases like naming a property
413 You could then use the property in a devicetree like this:
451 Consider a binding for a PWM LED node like this one, where the child nodes are
468 The binding would look like this:
514 of bus. For example, a binding for a SPI peripheral on an SoC would look like
571 either an SPI or an I2C controller, like this:
625 property, like the PWM controllers ``pwm1`` and ``pwm2`` in this example:
644 the cells that appear in a PWM specifier using ``pwm-cells:``, like this:
665 like :c:macro:`DT_PWMS_CHANNEL_BY_NAME`.
681 string, like this:
694 like this:
720 Note that you can make a property defined in base.yaml obligatory like this,
728 This relies on the dictionary merge to fill in the other keys for ``reg``, like
748 filter out just the definitions you want by putting a mapping in the list, like
782 Finally, you can filter from a child binding like this: