Searched refs:precedence (Results 1 – 25 of 35) sorted by relevance
12
| /Zephyr-latest/cmake/toolchain/cross-compile/ |
| D | generic.cmake | 18 # The env var has the lowest precedence.
|
| /Zephyr-latest/tests/cmake/zephyr_get/ |
| D | CMakeLists.txt | 103 # CMake cache value has the highest precedence.
107 # Environment value has the next highest precedence.
117 # Locally scoped value has the lowest precedence.
299 # Highest precedence scope always wins.
525 # Snippets have higher precedence than environment, but lower than CMake cache.
551 # Transitively, snippets have lower precedence than sysbuild-defined values.
|
| /Zephyr-latest/soc/intel/intel_adsp/common/ |
| D | CMakeLists.txt | 146 # ${WEST_SIGN_OPTS} like this has _higher_ precedence than `west config
148 # multiple places to avoid unexpected precedence rules.
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 199 ``ERROR`` or ``BLOCK`` status. As this takes precedence over all other Case statuses, all valid
203 Suite has at least one Case that did not meet its assertions. This takes precedence over
|
| D | pytest.rst | 101 present in both places, the one from the command line will take precedence.
|
| /Zephyr-latest/ |
| D | .gitlint | 5 # verbosity should be a value between 1 and 3, the commandline -v flags take precedence over this
|
| D | Kconfig.zephyr | 17 # Shield defaults should have precedence over board defaults, which should have
18 # precedence over SoC defaults, so include them in that order.
|
| /Zephyr-latest/doc/contribute/style/ |
| D | index.rst | 86 take precedence. If there is ambiguity between formatting tools and the
|
| /Zephyr-latest/subsys/net/l2/ethernet/gptp/ |
| D | Kconfig | 191 precedence. The default value is 255 if the device is non grand
204 precedence. The default value is 248.
|
| /Zephyr-latest/scripts/pylib/twister/ |
| D | expr_parser.py | 102 precedence = ( variable
|
| /Zephyr-latest/cmake/modules/ |
| D | FindBabbleSim.cmake | 17 # Note that what we find through the environment variables is meant to have precedence.
|
| D | kconfig.cmake | 47 # already in the CMakeCache.txt. This has precedence.
|
| D | dts.cmake | 89 # thus files specified by EXTRA_DTC_OVERLAY_FILE have higher precedence.
|
| D | extensions.cmake | 425 # the zephyr_library_* API then precedence will be given to the
532 # conflict. Compilers generally give precedence to flags given late
852 # precedence, except for arguments which can be given multiple times
870 # next, so they take precedence over the common runner file.
908 # next, so they take precedence over the common emu file.
3177 # not change the order of precedence in which the list itself is constructed.
3188 # The order of precedence for variables defined in multiple scopes:
3371 # scope. The scope is used on later zephyr_get() invocation for precedence
3422 # CLI has the highest precedence, then comes environment variables,
3429 # A user can ignore all the precedence rules if the same source is always used
[all …]
|
| /Zephyr-latest/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 | 856 configuration option has higher precedence than the ``manifest: group-filter:
1448 - name: hal_nordic # higher precedence
1455 import: true # imported projects have lower precedence
1466 - name: hal_nordic # lower precedence, values ignored
1620 precedence. For example, if :file:`01-libraries.yml` defines ``hal_nordic``,
1653 higher precedence than other definitions in :file:`my-repo/submanifests`,
2125 precedence over any extension commands with the same names added later on.
2134 Manifest files which appear earlier in the import order have higher precedence
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 196 no notion of precedence among partitions within a memory domain. Partitions
197 within a memory domain are assumed to have a higher precedence than any
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 28 The ``__ASSERT_ON`` method takes precedence over the kconfig option if both are
|
| /Zephyr-latest/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-latest/boards/nxp/imx93_evk/doc/ |
| D | index.rst | 135 automatically selected if certain board function is enabled, and takes precedence
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 131 undocumented rimage precedence rules it's best to use only one way at a time.
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 182 precedence.
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 277 in this setup, ``find_package(Zephyr)`` has the following order of precedence for selecting
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 54 Execution of ISRs takes precedence over thread execution,
|
| /Zephyr-latest/doc/project/ |
| D | project_roles.rst | 316 * Area maintainer gets precedence over parent-area maintainer
|
12
