Searched refs:met (Results 1 – 25 of 30) sorted by relevance
12
| /Zephyr-latest/subsys/rtio/ |
| D | Kconfig | 15 thread for each completion queue event until the wait count is met. This
27 calling thread for each completion queue event until the wait count is met.
|
| /Zephyr-latest/samples/boards/nordic/clock_control/ |
| D | Kconfig | 32 before a clock request can be met.
|
| /Zephyr-latest/cmake/modules/ |
| D | FindDtc.cmake | 47 # DTC was found but version requirement is not met, or dtc was not working.
|
| /Zephyr-latest/tests/drivers/can/timing/ |
| D | Kconfig | 11 impose limits on which bitrates can be met due to limitations in the CAN core clock
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 248 * Zephyr : Requirement met.
253 * Zephyr : Requirements met.
258 * Zephyr : Requirement met. System tick rate = 100 Hz.
263 * Zephyr : Requirement met.
269 * Zephyr : Requirement met. See irq_offload().
|
| /Zephyr-latest/soc/nordic/nrf52/ |
| D | Kconfig | 87 that anomaly conditions are not met. Delay should be long enough to ensure
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 120 * Other formats are accepted as long as the characteristics of a requirement from above are met.
|
| /Zephyr-latest/doc/project/ |
| D | tsc.rst | 169 met, the default voting mechanism will be a verbal motion to determine if
177 requirements have been met, the Chair may call for a roll call vote
|
| D | release_process.rst | 100 The main motivation is to clearly have the criteria in place that must be met
112 Below is the high level criteria to be met for each release:
187 met.
482 When all final release criteria has been met and the final release notes
|
| D | project_roles.rst | 363 * All :ref:`pr_requirements` must be met.
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | events.rst | 33 match conditions have been met are made active at the same time.
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 204 all other Case statuses, given that the conditions for an ERROR status have not been met.
|
| D | ztest.rst | 440 conditions are met and the execution has completed, an execution report is printed
453 the timeout is configured to complete after 10 seconds if those conditions are not met.
|
| /Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/ |
| D | index.rst | 148 Once the above prerequisites are met, applications for the ``_cc3220sf_launchxl``
|
| /Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/ |
| D | index.rst | 151 Once the above prerequisites are met, applications for the ``_cc3235sf_launchxl``
|
| /Zephyr-latest/doc/kernel/services/ |
| D | polling.rst | 37 its state is changed to signal the requested condition has been met.
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 174 met:
478 still used, but there are additional constraints which must be met or the
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 14 requirements and dependencies may not be met by your package manager. In that
|
| /Zephyr-latest/boards/arm/v2m_musca_s1/doc/ |
| D | index.rst | 389 description are met before building.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 50 call APIs, several conditions must be met on how the kernel object is declared:
|
| D | syscalls.rst | 534 The following constraints need to be met:
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 668 these assumptions are met by the hardware and the application, a
677 assumptions on the application. If these are met, the final
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | main.rst | 54 This condition is met as soon as one or both of these is assigned.
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 286 can be updated independently if dependency requirements are met.
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 124 To make a good faith effort to ensure licensing criteria are met, the Zephyr
|
12
