Searched full:optimal (Results 1 – 25 of 69) sorted by relevance
123
/Zephyr-latest/dts/bindings/lora/ |
D | st,stm32wl-subghz-radio.yaml | 32 however, for optimal performance, it is advisable to align the value with 48 however, for optimal performance, it is advisable to align the value with
|
/Zephyr-latest/samples/net/zperf/src/ |
D | nrf5340_cpu_boost.c | 23 /* For optimal performance, the CPU frequency should be set to 128 MHz */ in nrf53_cpu_boost()
|
/Zephyr-latest/tests/subsys/fs/fat_fs_api/src/ |
D | test_fat_fs.c | 22 TC_PRINT("Optimal transfer block size = %lu\n", stat.f_bsize); in test_statvfs()
|
/Zephyr-latest/tests/subsys/fs/fat_fs_dual_drive/src/ |
D | test_fat_fs.c | 27 TC_PRINT("Optimal transfer block size = %lu\n", stat.f_bsize); in test_statvfs()
|
/Zephyr-latest/soc/microchip/mec/common/reg/ |
D | mec_peci.h | 108 /* Optimal Bit Time LSB register. */ 112 /* Optimal Bit Time MSB register. */
|
/Zephyr-latest/lib/utils/ |
D | Kconfig | 17 For optimal performance, use buffer sizes that are a power of 2.
|
/Zephyr-latest/lib/libc/minimal/include/sys/ |
D | types.h | 53 * The mem_word_t should match the optimal memory access word width
|
/Zephyr-latest/drivers/disk/nvme/ |
D | nvme_namespace.h | 72 /** Namespace Optimal IO Boundary */ 90 /** Namespace Optimal Write Size */
|
/Zephyr-latest/samples/net/sockets/dumb_http_server/src/ |
D | response_big.html.bin | 31 …supports multiple architectures, developers are able to easily tailor an optimal solution to meet …
|
/Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
D | response_big.html.bin | 31 …supports multiple architectures, developers are able to easily tailor an optimal solution to meet …
|
/Zephyr-latest/doc/kernel/services/smp/ |
D | smp.rst | 236 with an optimal set of threads) that can be scheduled on the N CPUs and a 240 When CPU masking is not in play, the optimal set of threads is the same 242 may be more than one valid set--one of which may be optimal. 247 then this set is is both valid and optimal. However, if CPU0 is executing 248 T1 and CPU1 is idling, then this too would be valid though not optimal.
|
/Zephyr-latest/soc/ambiq/apollo3x/ |
D | power.c | 86 /* For optimal Deep Sleep current, configure cache to be powered-down in deepsleep. */ in ambiq_power_init()
|
/Zephyr-latest/modules/mbedtls/configs/ |
D | config-coap.h | 98 * The optimal size here depends on the typical size of records.
|
D | config-ccm-psk-tls1_2.h | 108 * The optimal size here depends on the typical size of records.
|
/Zephyr-latest/modules/fatfs/ |
D | zephyr_fatfs_config.h | 126 * to allow more optimal use with MCUs that require specific bufer alignment
|
/Zephyr-latest/arch/x86/core/ |
D | cache.c | 84 * both is optimal.
|
/Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/ |
D | README.rst | 75 Optimal configuration for low power consumption
|
/Zephyr-latest/lib/heap/ |
D | Kconfig | 87 - "auto" providing optimal memory overhead in all cases but with
|
/Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
D | index.rst | 145 features are used by the application and optimal code is being generated. 148 options from ``.tcf`` - but that may be far from optimal solution. For example, such approach
|
/Zephyr-latest/tests/subsys/fs/fat_fs_api/ |
D | README.txt | 107 Optimal transfer block size = 512
|
/Zephyr-latest/arch/xtensa/core/ |
D | xtensa_intgen.py | 9 # this isn't as optimal as I'd hoped. the individual cases are tested
|
/Zephyr-latest/soc/nordic/nrf54l/ |
D | soc.c | 110 * additions and subtractions, it generates slightly less than optimal in nordicsemi_nrf54l_init()
|
/Zephyr-latest/doc/project/ |
D | working_groups.rst | 32 optimal size of a working group can vary depending on the specific context and
|
/Zephyr-latest/doc/kernel/services/synchronization/ |
D | mutexes.rst | 85 involved. However, if multiple mutexes are involved, sub-optimal behavior will
|
/Zephyr-latest/cmake/linker_script/arm/ |
D | linker.cmake | 35 # ToDo: decide on the optimal location for this.
|
123