Lines Matching refs:specifier

131 the resource you are interested in. The specifier describes the resource
193 specifier spaces before moving on to some information about devicetree
196 .. _dt-specifier-spaces:
204 We'll start with an abstract, high level description of how specifier spaces
221 The cells that follow each phandle are called a *specifier*. In this example,
227 Every phandle-array property has an associated *specifier space*. This sounds
229 follow each phandle in a hardware specific way. Every specifier space has a
233 Devicetree nodes encode the number of cells that must appear in a specifier, by
235 ``phandle-array-prop``\ 's specifier space is named ``baz``. Then we would need
249 to validate the number of cells in each specifier in ``phandle-array-prop``.
255 A single node can also have different numbers of cells in different specifier
266 With that, if ``phandle-array-prop-2`` has specifier space ``bob``, we could
281 Example specifier space: gpio
284 From the above example, you're already familiar with how one specifier space
300 Associating properties with specifier spaces
305 - each phandle-array property has an associated specifier space
306 - specifier spaces are identified by name
308   configure the number of cells which must appear in a specifier
310 In this section, we explain how phandle-array properties get their specifier
317 specifier space ``foo``. For example:
327 The ``dmas`` property's specifier space is "dma". The ``pwms`` property's
328 specifier space is ``pwm``.
339 You can manually specify the specifier space for any ``phandle-array``
340 property. See :ref:`dt-bindings-specifier-space`.
342 Naming the cells in a specifier
345 You should name the cells in each specifier space your hardware supports when
349 in a specifier by name using devicetree APIs like these:
372 - :ref:`dt-bindings-specifier-space`: how to manually specify a phandle-array
373   property's specifier space