Lines Matching refs:properties

37    properties:
38      # Requirements for and descriptions of the properties that this
67 datasheets or example nodes or properties as well.
114 .. _dt-bindings-properties:
119 The ``properties:`` key describes properties that nodes which match the binding
127    properties:
141 The build system uses bindings to generate C macros for devicetree properties
144 build system only generates macros for properties listed in the ``properties:``
149 standard properties, like :ref:`reg <dt-important-props>`, whose meaning is
156 Property entries in ``properties:`` are written in this syntax:
175 .. _dt-bindings-example-properties:
184    properties:
252 The default setting is ``required: false``; that is, properties are optional by
262 about the ``phandle*`` type properties.
342    properties:
356 See :ref:`dt-bindings-example-properties` for examples. Putting ``default:`` on
357 any property type besides those used in :ref:`dt-bindings-example-properties`
365 is raised. See :ref:`dt-bindings-example-properties` for examples.
371 constraining the values of common properties for a particular piece of
381    It is an abuse of this feature to use it to name properties in
394 space ``foo``. As a special case, ``*-gpios`` properties have specifier space
406    properties:
436    properties:
447 properties. Each child gets the contents of ``child-binding`` as its binding,
477      properties:
490        properties:
606    properties:
707 a :ref:`property definition <dt-bindings-properties>` for which the included
716 definitions for many common properties. When writing a new binding, it is a
718 properties, and include it if it does.
742 When including multiple files, any overlapping ``required`` keys on properties
765 which properties are included.
795 All ``phandle-array`` type properties support mapping through ``*-map``
796 properties, e.g. ``gpio-map``, as defined by the Devicetree specification.