Searched full:much (Results 1 – 25 of 252) sorted by relevance
1234567891011
12 # Note: this test depends too much on not having a high host load to pass.
7 # much CI time
18 apps won't require much time to reach an idle state
17 * To reuse as much as possible from the llvm.h header we only redefine the
11 Note: Currently Zephyr does not support multiple processes and therefore much of this option
8 # Enable optional features that are off by default to cover as much as
15 * arch_swap() itself does not do much.
7 with the option ``-fanalyzer``. This option performs a much more expensive and thorough
29 configuration doesn't make much sense as there's
8 that is not always needed. Another example is a PMIC, typically a much more
25 just one RAM region and doing this makes linking much simpler, as70 how much total memory can be used for page tables.130 retrieved from the backing store. This is much better for system
38 # to keep it that way as to stress the stack as much as possible.
29 but it may be more efficient for MCU to read as much data as
15 # The test will be terminated much earlier if it passes
19 too much resource requirements. The security is not top-notch (AES-128) but it
57 bool "Trim: Do not block, output as much as fits."
14 # all of zephyr's scripts/requirements.txt, which seems like too much
37 This section is freeform - you should describe your change in as much detail
22 # MBEDTLS is larger but much faster than TinyCrypt so choose wisely
114 value too much can result in spurious interrupts. Leaving it too150 This layer provides much of the groundwork for keeping track of
45 * usec_to_waste are spent in this context, irrespectively of how much more
35 * 32-bit of data. There's not much that can be done in this in rand_get()
70 be much less to be actually instantiated at runtime.
37 * post_write_cb, as there is not much that can be in led_on_off_cb()
