| /Zephyr-Core-3.7.0/doc/build/dts/ |
| D | phandles.rst | 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``.
[all …]
|
| D | bindings-syntax.rst | 173 specifier-space: <space-name>
374 .. _dt-bindings-specifier-space:
376 specifier-space
385 ``my-pin``, then assigning it to the "gpio" specifier space using this
389 This property, if present, manually sets the specifier space associated with a
392 Normally, the specifier space is encoded implicitly in the property name. A
393 property named ``foos`` with type ``phandle-array`` implicitly has specifier
394 space ``foo``. As a special case, ``*-gpios`` properties have specifier space
395 "gpio", so that ``foo-gpios`` will have specifier space "gpio" rather than
398 You can use ``specifier-space`` to manually provide a space if
[all …]
|
| D | api-usage.rst | 271 the index of an individual interrupt specifier in the property. The ``val``
272 argument is the name of a cell within the interrupt specifier. To use this
314 Another common use case is accessing specifier values in a phandle array. The
322 check if a specifier value is present in a phandle property.
|
| D | intro-syntax-structure.rst | 293 of one or more *interrupt specifiers*. Each interrupt specifier has some
298 an interrupt specifier.
|
| D | macros.bnf | 306 ; - related to phandle specifier names ("foo-names")
313 ; - _IDX_<DIGIT>_VAL_<dt-name>: values of individual specifier
|
| /Zephyr-Core-3.7.0/lib/os/ |
| D | cbprintf_complete.c | 260 unsigned char specifier; member
518 conv->specifier = *sp; in extract_specifier()
521 switch (conv->specifier) { in extract_specifier()
536 if (conv->specifier == 'c') { in extract_specifier()
580 conv->specifier_a = (conv->specifier == 'a') in extract_specifier()
581 || (conv->specifier == 'A'); in extract_specifier()
656 conv->specifier = *sp; in extract_conversion()
763 static inline size_t conversion_radix(char specifier) in conversion_radix() argument
765 switch (specifier) { in conversion_radix()
795 bool upcase = isupper((int)conv->specifier) != 0; in encode_uint()
[all …]
|
| D | Kconfig.cbprintf | 173 candidate is used for %p format specifier. Check cannot be performed
|
| /Zephyr-Core-3.7.0/samples/net/wpan_serial/src/ |
| D | main.c | 313 uint8_t specifier; in rx_thread() local
323 specifier = net_buf_pull_u8(buf); in rx_thread()
324 switch (specifier) { in rx_thread()
332 LOG_ERR("Unknown message specifier %c", specifier); in rx_thread()
|
| /Zephyr-Core-3.7.0/scripts/build/ |
| D | gen_relocate_app.py | 313 specifier = f"_{kind}"
314 if specifier in memory_region:
316 memory_region = memory_region.replace(specifier, "")
|
| /Zephyr-Core-3.7.0/cmake/compiler/clang/ |
| D | compiler_flags.cmake | 114 -Wno-format-invalid-specifier
|
| /Zephyr-Core-3.7.0/doc/hardware/porting/ |
| D | shields.rst | 171 …ac80eaca45b4babf5299452a951008a5d864/source/devicetree-basics.rst#nexus-nodes-and-specifier-mapping
222 specifier. Then the ``gpio-map-pass-thru`` specifies that the low 6
|
| /Zephyr-Core-3.7.0/doc/services/ |
| D | formatted_output.rst | 169 things the ``%n`` specifier, most format flags, precision control, and
178 * It is recommended to cast any character pointer used with ``%p`` format specifier to
|
| /Zephyr-Core-3.7.0/cmake/compiler/arcmwdt/ |
| D | compiler_flags.cmake | 102 -Wno-format-invalid-specifier
|
| /Zephyr-Core-3.7.0/doc/_scripts/ |
| D | gen_devicetree_rest.py | 533 for specifier, cells in binding.specifier2cells.items():
|
| /Zephyr-Core-3.7.0/scripts/dts/python-devicetree/tests/ |
| D | test.dts | 116 // Child unit specifier: 00000007 0000000E 00000007 0000000E
|
| /Zephyr-Core-3.7.0/doc/services/logging/ |
| D | index.rst | 762 format specifier and it points to a constant string.
764 format specifier and it points to a transient string.
766 (e.g., ``void *``) when it is used with ``%p`` format specifier.
|
| /Zephyr-Core-3.7.0/scripts/ |
| D | checkpatch.pl | 6213 my $specifier;
6221 $specifier = $1;
6227 $bad_specifier = $specifier;
|
| /Zephyr-Core-3.7.0/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_0.rst | 764 | "format" | Format specifier of returned response, fields are appended in |
|
| /Zephyr-Core-3.7.0/doc/releases/ |
| D | release-notes-1.6.rst | 126 * libc: Added support for 'z' length specifier.
|
| D | release-notes-2.6.rst | 1526 * :github:`33814` - [Coverity CID: 220422] Extra argument to printf format specifier in tests/lib/s…
1535 * :github:`33805` - [Coverity CID: 220431] Extra argument to printf format specifier in tests/lib/s…
1539 * :github:`33801` - [Coverity CID: 220435] Extra argument to printf format specifier in tests/lib/s…
1557 * :github:`33783` - [Coverity CID: 220453] Extra argument to printf format specifier in tests/lib/s…
|
| D | release-notes-3.5.rst | 1162 * specifier cells for space "reset" are now named: ['id'] (old value: None)
1163 * specifier cells for space "clock" are now named: None (old value: ['reset_id'])
|
| D | release-notes-2.4.rst | 1116 * :github:`27643` - [Coverity CID :212427] Invalid type in argument to printf format specifier in s…
1273 * :github:`26985` - [Coverity CID :211476] Extra argument to printf format specifier in arch/x86/ze…
|
| D | release-notes-3.1.rst | 810 PWM specifier should contain a channel, period, and flags cell, in that
931 * Added ``PRIx{FAST,LEAST}N`` and ``PRIxMAX`` format specifier macros in
|
| D | release-notes-3.3.rst | 1533 …- specifier cells for space "pwm" are now named: ['channel', 'period', 'flags'] (old value: ['chan…
1561 … - specifier cells for space "dma" are now named: ['channel', 'config'] (old value: ['channel'])
1707 …- specifier cells for space "pwm" are now named: ['channel', 'period', 'flags'] (old value: ['chan…
|
| /Zephyr-Core-3.7.0/doc/build/kconfig/ |
| D | tips.rst | 75 An alternative applicable to device drivers is to define a GPIO specifier with
|
