Home
last modified time | relevance | path

Searched refs:macros (Results 51 – 75 of 124) sorted by relevance

12345

/Zephyr-latest/include/zephyr/sys/
Dutil.h57 # error Missing required predefined macros for BITS_PER_LONG calculation
/Zephyr-latest/doc/build/cmake/
Dindex.rst85 :file:`*.overlay` files, and to expand macros in :file:`*.dts`,
92 preprocessor macros.
94 Source code should access preprocessor macros generated from devicetree by
/Zephyr-latest/doc/build/dts/
Dbindings-syntax.rst141 The build system uses bindings to generate C macros for devicetree properties
143 source code from these macros in :ref:`dt-from-c`. Generally speaking, the
144 build system only generates macros for properties listed in the ``properties:``
148 The one exception is that the build system will always generate macros for
314 - a catch-all for more complex types (no macros will be generated)
Dbindings-intro.rst16 contents and when generating macros for the node.
/Zephyr-latest/subsys/llext/
DKconfig87 made available to llexts via the standard DT_ / DEVICE_* macros.
/Zephyr-latest/doc/services/storage/flash_map/
Dflash_map.rst81 All :code:`FIXED_PARTITION_*` macros take DTS node labels as partition
/Zephyr-latest/tests/bsim/bluetooth/mesh/
DREADME.rst82 This includes ``PASS``/``FAIL`` macros and some common mesh actions, such as
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst16 Zephyr provides some macros to perform runtime assertions which may be
123 Zephyr provides two macros for performing build-time assertion checks.
/Zephyr-latest/doc/releases/
Dmigration-guide-3.6.rst116 * Various deprecated macros related to the deprecated devicetree label property
166 of the Devicetree macros now return the as-seen value in the devicetree instead of the Zephyr
211 ``negative``) to the common ``input``, making it possible to use the various ADC DT macros with TI
225 ``input``, making it possible to use the various ADC DT macros with Microchip MCP320x ADC devices.
256 along with their initializer macros.
Drelease-notes-2.3.rst14 * A new Devicetree API, based on hierarchical macros, has been introduced. This
111 * BT_LE_ADV_* macros, use BT_GAP_ADV_* enums instead
131 * The C macros generated from the devicetree in previous releases are now
135 * Use of the legacy macros now requires explicitly enabling
141 https://docs.zephyrproject.org/2.3.0/guides/dts/legacy-macros.html#dt-legacy-macros
167 and ETH_NET_DEVICE_INIT() macros changed and take a device power management
849 …thub:`25332` - lib: updatehub: Don't build after conversion from DT_FLASH_AREA to FLASH_AREA macros
951 * :github:`24645` - naming consistency for kernel object initializer macros
1019 * :github:`24241` - Build error when using MCHP ACPI HAL macros
1148 * :github:`23529` - Convert STM32 drivers to new DT macros
[all …]
Drelease-notes-3.2.rst107 * The following functions, macros, and structures related to the
166 * Flash Map API macros :c:macro:`FLASH_MAP_`, which have been using DTS node label
219 * Source files using multiple :c:macro:`SYS_INIT` macros with the
503 * Fixed :c:macro:`ADC_DT_SPEC_GET` and related macros to properly handle
974 * All devicetree macros now recursively expand their arguments. This means
987 * New API macros:
1016 * Deprecated macros:
1025 deprecated macros: if you need to access a devicetree node's label
1533 * Added ``FIXED_PARTITION_`` macros that move flash_map to use DTS node labels.
1550 * Flash Map API deprecates usage of :c:macro:`FLASH_AREA_` macros and replaces
[all …]
Drelease-notes-2.5.rst132 * The deprecated BT_LE_ADV_* macros have been removed,
341 macros to configure pins in pinmux.c files are tagged as deprecated.
406 * drivers are converted to use the new DEVICE_DT_* macros.
525 devicetree definitions. The previous C macros are now deprecated.
767 * Support for legacy devicetree macros via
775 * Enhanced support for enumerated property values via new macros:
781 * New hardware specific macros:
787 * Miscellaneous new node-related macros:
800 * Dependencies between nodes are now exposed via new macros:
1274 * :github:`30467` - replace device define macros with devicetree-based macro
[all …]
Drelease-notes-4.1.rst33 (replaced by :c:macro:`CAN_EXT_ID_MASK`) CAN API macros have been removed.
/Zephyr-latest/scripts/coccinelle/
Dint_ms_to_timeout.cocci8 // produced by specific constants and macros. Convert integer
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_if.rst22 :kconfig:option:`CONFIG_NET_VLAN` is enabled. These macros are typically used in
/Zephyr-latest/include/zephyr/arch/nios2/
Dlinker.ld23 /* This linker script requires the following macros to be defined in the
/Zephyr-latest/dts/arm/st/wb0/
Dstm32wb0.dtsi87 * macros in `include/drivers/clock_control/stm32_clock_control.h`
/Zephyr-latest/arch/posix/
DCMakeLists.txt103 # remove all operating system specific predefined macros,
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst153 States can be skipped by the ``pinctrl`` Devicetree macros if a definition named
417 :c:macro:`PINCTRL_DT_DEFINE` or :c:macro:`PINCTRL_DT_INST_DEFINE` macros
422 :c:macro:`PINCTRL_DT_INST_DEV_CONFIG_GET` macros.
/Zephyr-latest/doc/kernel/memory_management/
Dvirtual_memory.rst69 Note that the ``Z_*`` macros, which are used in code, may have different
/Zephyr-latest/doc/hardware/peripherals/
Dmspi.rst37 The usual device defining macros such as :c:macro:`DEVICE_DT_INST_DEFINE`
/Zephyr-latest/doc/services/logging/
Dcs_stm.rst181 Logging messages contains read-only format string used in the logging macros thus they cannot be
238 * Use optimized log macros (having up to 2 word size numeric arguments, like ``LOG_INF("%d %c", (in…
/Zephyr-latest/subsys/testsuite/ztest/
DKconfig75 The override header may now #define the various macros and strings in tc_util.h which are
/Zephyr-latest/doc/services/shell/
Dindex.rst226 Use the following macros for adding shell commands:
484 Function :c:func:`shell_fprintf` or the shell print macros:
494 The help for commands and subcommands can be created with respective macros:
/Zephyr-latest/soc/intel/intel_adsp/cavs/include/
Dxtensa-cavs-linker.ld33 * These macros will set up a segment start address correctly,

12345