Searched refs:levels (Results 76 – 100 of 118) sorted by relevance
12345
/Zephyr-latest/arch/arm/core/cortex_m/ |
D | Kconfig | 331 int "Number of interrupt priority levels reserved for zero latency" 335 The amount of interrupt priority levels reserved for zero latency
|
/Zephyr-latest/boards/adi/max32690evkit/doc/ |
D | index.rst | 284 Logic levels are fixed to VDDIO (1.8V).
|
/Zephyr-latest/boards/adi/max32666evkit/doc/ |
D | index.rst | 296 Logic levels are fixed to VDDIOH (1.8V or 3.3V).
|
/Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
D | gap.rst | 310 When connected to a device, you can enable multiple levels of security, here is the list for 318 To enable security, use the :code:`bt security <level>` command. For levels requiring authentication
|
/Zephyr-latest/modules/trusted-firmware-m/ |
D | Kconfig.tfm | 130 As isolation levels 2 and 3 require PSA_API (TFM_IPC) support, 345 isolation levels 1, 2 and 3.
|
/Zephyr-latest/doc/develop/api/ |
D | terminology.rst | 159 or ``PRE_KERNEL_2`` initialization levels.
|
/Zephyr-latest/boards/adi/max32680evkit/doc/ |
D | index.rst | 327 Logic levels are set to 1.8V (VDDIO_AUX).
|
/Zephyr-latest/subsys/testsuite/ztest/ |
D | Kconfig | 57 Assertion verbosity levels:
|
/Zephyr-latest/doc/project/ |
D | project_roles.rst | 54 …managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organizatio… 90 * Responsibility to ensure the quality of the code to expected levels.
|
/Zephyr-latest/boards/adi/max32672evkit/doc/ |
D | index.rst | 325 Logic levels are set to 3V3 by default, but they can be set to 1.8V if TP5 (VDD_VDDA_EXT)
|
/Zephyr-latest/boards/adi/max78002evkit/doc/ |
D | index.rst | 270 Logic levels are fixed to VDDIO (1.8V).
|
/Zephyr-latest/doc/kernel/services/ |
D | interrupts.rst | 78 number, providing support for up to four interrupt levels using this arch, as 91 There are three interrupt levels shown here. 721 the total bits used between all levels must sum to be less than or equal to 32-bits,
|
/Zephyr-latest/cmake/modules/ |
D | yaml.cmake | 325 # Several levels of keys can be given, for example:
|
/Zephyr-latest/modules/hostap/ |
D | Kconfig | 72 available levels and functions for emitting the messages. Note that
|
/Zephyr-latest/boards/adi/max32675evkit/doc/ |
D | index.rst | 377 Logic levels are set to 3V3 by default, but they can be set to 1.8V if TP5 (VDD_VDDA_EXT)
|
/Zephyr-latest/arch/arc/ |
D | Kconfig | 141 int "Number of supported interrupt priority levels"
|
/Zephyr-latest/doc/services/logging/ |
D | index.rst | 45 There are four severity levels available in the system: error, warning, info 68 lower module logging levels that were previously set higher. It is also possible 71 is set to info, it means that errors, warnings and info levels are present but
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | index.rst | 257 The kernel supports a virtually unlimited number of thread priority levels. 260 levels for each class of thread, resulting in the following usable priority
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-le-host.rst | 124 there are four possible security levels that can be reached:
|
/Zephyr-latest/doc/develop/languages/cpp/ |
D | index.rst | 131 incompatibilities`_. C is not just a C++ subset. Standard levels (e.g.:
|
/Zephyr-latest/doc/contribute/ |
D | contributor_expectations.rst | 169 The Zephyr community is a diverse group of individuals, with different levels of
|
/Zephyr-latest/boards/intel/adsp/doc/ |
D | intel_adsp_generic.rst | 85 the cAVS and ACE boards. However, users seeking greater levels of optimization
|
/Zephyr-latest/doc/safety/ |
D | safety_overview.rst | 62 measures needed to reduce those risks to acceptable levels.
|
/Zephyr-latest/doc/kernel/drivers/ |
D | index.rst | 347 initialization levels:
|
/Zephyr-latest/doc/kernel/usermode/ |
D | memory_domain.rst | 15 There are a few different levels on how memory access is configured when
|
12345