Searched refs:precedence (Results 1 – 25 of 36) sorted by relevance
12
/Zephyr-Core-3.5.0/cmake/toolchain/cross-compile/ |
D | generic.cmake | 18 # The env var has the lowest precedence.
|
/Zephyr-Core-3.5.0/soc/arm/nxp_imx/rt5xx/ |
D | Kconfig.defconfig.series | 21 # precedence:
|
/Zephyr-Core-3.5.0/soc/arm/nxp_imx/rt6xx/ |
D | Kconfig.defconfig.series | 22 # precedence:
|
/Zephyr-Core-3.5.0/cmake/modules/ |
D | configuration_files.cmake | 49 # in the CMakeCache.txt. This has precedence over the environment 68 # That value has precedence over anything else than a new
|
D | FindBabbleSim.cmake | 17 # Note that what we find through the environment variables is meant to have precedence.
|
D | dts.cmake | 83 # thus files specified by EXTRA_DTC_OVERLAY_FILE have higher precedence.
|
D | extensions.cmake | 391 # the zephyr_library_* API then precedence will be given to the 498 # conflict. Compilers generally give precedence to flags given late 803 # precedence, except for arguments which can be given multiple times 821 # next, so they take precedence over the common runner file. 2599 # not change the order of precedence in which the list itself is constructed. 2610 # The order of precedence for variables defined in multiple scopes: 2749 # scope. The scope is used on later zephyr_get() invocation for precedence 2799 # CLI has the highest precedence, then comes environment variables, 2806 # A user can ignore all the precedence rules if the same source is always used 2816 # used, as it has precedence. [all …]
|
D | kconfig.cmake | 63 # already in the CMakeCache.txt. This has precedence.
|
/Zephyr-Core-3.5.0/tests/cmake/zephyr_get/ |
D | CMakeLists.txt | 92 # CMake cache value has the highest precedence. 96 # Environment value has the next highest precedence. 106 # Locally scoped value has the lowest precedence. 288 # Highest precedence scope always wins. 513 # Snippets have higher precedence than environment, but lower than CMake cache. 539 # Transitively, snippets have lower precedence than sysbuild-defined values.
|
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/common/ |
D | CMakeLists.txt | 135 # ${WEST_SIGN_OPTS} like this has _higher_ precedence than `west config 137 # multiple places to avoid unexpected precedence rules.
|
/Zephyr-Core-3.5.0/ |
D | .gitlint | 5 # verbosity should be a value between 1 and 3, the commandline -v flags take precedence over this
|
D | Kconfig.zephyr | 15 # Shield defaults should have precedence over board defaults, which should have 16 # precedence over SoC defaults, so include them in that order.
|
/Zephyr-Core-3.5.0/subsys/net/l2/ethernet/gptp/ |
D | Kconfig | 206 precedence. The default value is 255 if the device is non grand 219 precedence. The default value is 248.
|
/Zephyr-Core-3.5.0/scripts/pylib/twister/ |
D | expr_parser.py | 102 precedence = ( variable
|
/Zephyr-Core-3.5.0/doc/develop/west/ |
D | workspaces.rst | 201 └── west.yml # This can be partially imported with lower precedence or ignored. 293 └── west.yml # This can be partially imported with lower precedence or ignored.
|
D | manifest.rst | 840 configuration option has higher precedence than the ``manifest: group-filter: 1432 - name: hal_nordic # higher precedence 1439 import: true # imported projects have lower precedence 1450 - name: hal_nordic # lower precedence, values ignored 1604 precedence. For example, if :file:`01-libraries.yml` defines ``hal_nordic``, 1637 higher precedence than other definitions in :file:`my-repo/submanifests`, 2109 precedence over any extension commands with the same names added later on. 2118 Manifest files which appear earlier in the import order have higher precedence
|
/Zephyr-Core-3.5.0/doc/kernel/usermode/ |
D | memory_domain.rst | 181 no notion of precedence among partitions within a memory domain. Partitions 182 within a memory domain are assumed to have a higher precedence than any
|
/Zephyr-Core-3.5.0/doc/kernel/services/other/ |
D | fatal.rst | 28 The ``__ASSERT_ON`` method takes precedence over the kconfig option if both are
|
/Zephyr-Core-3.5.0/doc/build/dts/ |
D | bindings-syntax.rst | 448 though an explicit ``compatible = ...`` on the child node takes precedence, if 708 file has ``required: false``. The ``required: true`` takes precedence, allowing
|
/Zephyr-Core-3.5.0/doc/build/kconfig/ |
D | setting.rst | 186 precedence.
|
/Zephyr-Core-3.5.0/doc/kernel/services/scheduling/ |
D | index.rst | 52 Execution of ISRs takes precedence over thread execution,
|
/Zephyr-Core-3.5.0/doc/build/ |
D | zephyr_cmake_package.rst | 277 in this setup, ``find_package(Zephyr)`` has the following order of precedence for selecting
|
/Zephyr-Core-3.5.0/doc/project/ |
D | project_roles.rst | 270 * Area maintainer gets precedence over parent-area maintainer
|
/Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/ |
D | intel_adsp_generic.rst | 144 undocumented rimage precedence rules it's best to use only one way at a time.
|
/Zephyr-Core-3.5.0/scripts/ |
D | spelling.txt | 818 precendence||precedence
|
12