Searched full:named (Results 1 – 25 of 210) sorted by relevance
123456789
| /Zephyr-Core-3.5.0/include/zephyr/llext/ |
| D | symbol.h | 24 * @brief Constant symbols are unchangeable named memory addresses
26 * Symbols may be named function or global objects that have been exported
39 * @brief Symbols are named memory addresses
41 * Symbols may be named function or global objects that have been exported
|
| /Zephyr-Core-3.5.0/arch/riscv/ |
| D | Kconfig.isa | 31 which is named "M" and contains instructions that multiply or divide
50 floating-point, which is named "F" and adds single-precision
61 which is named "D" and adds double-precision floating-point
86 quad-precision binary floatingpoint instruction subset is named "Q".
93 RISC-V standard compressed instruction set extension, named "C",
|
| /Zephyr-Core-3.5.0/include/zephyr/devicetree/ |
| D | pwms.h | 78 * @return the node identifier for the PWM controller in the named element
179 * @return the cell value in the specifier at the named element
197 * This macro only works for PWM specifiers with cells named "channel".
213 * This macro only works for PWM specifiers with cells named "channel".
221 * @return the channel cell value in the specifier at the named element
238 * This macro only works for PWM specifiers with cells named "period".
254 * This macro only works for PWM specifiers with cells named "period".
262 * @return the period cell value in the specifier at the named element
279 * This macro expects PWM specifiers with cells named "flags".
296 * This macro expects PWM specifiers with cells named "flags".
[all …]
|
| D | dma.h | 77 * @return the node identifier for the DMA controller in the named element
111 * @return the node identifier for the DMA controller in the named element
217 * @return the cell value in the specifier at the named element
229 * @return the cell value in the specifier at the named element
254 * @brief Does a dmas property have a named element?
258 * @return 1 if the dmas property has the named element, 0 otherwise
264 * @brief Does a DT_DRV_COMPAT instance's dmas property have a named element?
268 * @return 1 if the dmas property has the named element, 0 otherwise
|
| D | io-channels.h | 76 * @return the node identifier for the node referenced at the named element
109 * @return the node identifier for the node referenced at the named element
127 * This macro only works for io-channels specifiers with cells named
167 * This macro only works for io-channels specifiers with cells named
200 * @return the input cell in the specifier at the named element
230 * @return the input cell in the specifier at the named element
|
| D | mbox.h | 48 * @return the node identifier for the MBOX controller in the named element
84 * @return the channel value in the specifier at the named element or 0 if no
|
| D | reset.h | 152 * @return the cell value in the specifier at the named element
199 * the named element
223 * @return the cell value in the specifier at the named element
241 * This macro only works for Reset Controller specifiers with cells named "id".
|
| D | pinctrl.h | 75 * @param node_id node with a named pinctrl property
77 * @param idx index into the value of the named pinctrl property
100 * @param node_id node identifier with a named pinctrl property
274 * This expands to 1 if the named pinctrl property exists.
340 * @param idx index into the value of the named pinctrl property
|
| /Zephyr-Core-3.5.0/include/zephyr/sys/ |
| D | device_mmio.h | 162 * Example for a driver named "foo":
211 * Example for a driver named "foo":
309 * @defgroup device-mmio-named Named MMIO region macros
327 * Multiple named regions may be declared.
333 * Example for a driver named "foo":
356 * @brief Return a pointer to the RAM storage for a device's named MMIO address
375 * What gets stored here varies considerably by configuration. Multiple named
386 * Example for a driver named "foo":
417 * @brief Initialize a named DEVICE_MMIO_NAMED_ROM member
423 * that will have two regions named 'corge' and 'grault':
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/ |
| D | syscall.h | 39 * named k_foo():
41 * - The handler function will be named z_vrfy_k_foo(). Handler
45 * more information. - The implementation function will be named
|
| /Zephyr-Core-3.5.0/doc/build/snippets/ |
| D | writing.rst | 10 Snippets are defined using YAML files named :file:`snippet.yml`.
41 For example, if your snippet is named ``foo-bar``, write your devicetree
70 :file:`snippet.yml` files underneath a subdirectory named :file:`snippets/`,
86 For example, in a zephyr module named ``baz``, you can add this to your
|
| D | using.rst | 17 To use a snippet named ``foo`` when building an application ``app``:
|
| /Zephyr-Core-3.5.0/subsys/net/l2/ |
| D | Kconfig | 67 console via a shell module named "net_bt".
130 exposing a shell module named "wifi".
|
| /Zephyr-Core-3.5.0/doc/build/dts/ |
| D | intro-syntax-structure.rst | 46 #. A node named ``a-node``, which is a child of the root node
47 #. A node named ``a-sub-node``, which is a child of ``a-node``
70 Node ``a-sub-node`` has a property named ``foo``, whose value is a cell with
174 For example, the node named ``i2c@40003000`` represents an I2C controller
188 For example, a node named ``memory@2000000`` represents RAM starting at
193 For example, a node named ``flash@8000000`` represents a flash device
212 The node named ``partition@0`` has offset 0 from the start of its flash
214 the node named ``partition@20000`` is 0x8020000.
|
| /Zephyr-Core-3.5.0/dts/bindings/pwm/ |
| D | fsl,imx27-pwm.yaml | 6 The compatible string is named "imx27" because the hardware module is the
|
| /Zephyr-Core-3.5.0/doc/develop/west/ |
| D | install.rst | 32 West's code is distributed via PyPI in a Python package named ``west``.
33 This distribution includes a launcher executable, which is also named
|
| /Zephyr-Core-3.5.0/samples/sensor/soc_voltage/ |
| D | README.rst | 16 ``SENSOR_CHAN_VOLTAGE`` and create an alias named ``volt-sensor0`` to link to the node.
|
| /Zephyr-Core-3.5.0/samples/sensor/die_temp_polling/ |
| D | README.rst | 16 and create an alias named ``die-temp0`` to link to the node.
|
| /Zephyr-Core-3.5.0/boards/arm/mec172xevb_assy6906/support/ |
| D | spi_cfg.txt | 10 ; BoardID is used by a Boot-ROM feature named PlatformID. By default PlatformID
|
| /Zephyr-Core-3.5.0/boards/arm/mec172xmodular_assy6930/support/ |
| D | spi_cfg.txt | 10 ; BoardID is used by a Boot-ROM feature named PlatformID. By default PlatformID
|
| D | spi_cfg_4MBit.txt | 10 ; BoardID is used by a Boot-ROM feature named PlatformID. By default PlatformID
|
| /Zephyr-Core-3.5.0/samples/drivers/audio/dmic/ |
| D | README.rst | 19 label named ``dmic_dev``.
|
| /Zephyr-Core-3.5.0/doc/hardware/pinctrl/ |
| D | index.rst | 13 parameters such as pin direction, pull-up/down resistors, etc. are named **pin
25 parameters are controlled by a single hardware block (typically named pinmux),
128 custom state identifiers named as ``PINCTRL_STATE_{STATE_NAME}``, where
130 to be supported, a definition named ``PINCTRL_STATE_MYSTATE`` needs to be
152 States can be skipped by the ``pinctrl`` Devicetree macros if a definition named
376 ``pinctrl_soc_pin_t``. This type needs to be defined in a header named
379 needs to define a macro named ``Z_PINCTRL_STATE_PINS_INIT`` that accepts two
425 The way an instance of :c:struct:`pinctrl_dev_config` is named for a
|
| /Zephyr-Core-3.5.0/samples/bluetooth/ |
| D | bluetooth.rst | 15 QEMU or Native POSIX), those are named accordingly with an "HCI" prefix in the
|
| /Zephyr-Core-3.5.0/samples/sensor/qdec/ |
| D | README.rst | 22 * add a new alias property named ``qdec0`` and make it point to the decoder
|
123456789
