Searched refs:best (Results 1 – 25 of 71) sorted by relevance
123
/Zephyr-Core-3.5.0/drivers/interrupt_controller/ |
D | intc_esp32.c | 348 int best = -1; in get_available_int() local 374 best = vd->intno; in get_available_int() 376 return best; in get_available_int() 389 best = vd->intno; in get_available_int() 393 return best; in get_available_int() 439 best = x; in get_available_int() 445 INTC_LOG("...worse than int %d", best); in get_available_int() 448 if (best == -1) { in get_available_int() 457 best = x; in get_available_int() 471 best = x; in get_available_int() [all …]
|
/Zephyr-Core-3.5.0/cmake/compiler/xcc/ |
D | compiler_flags.cmake | 7 # time. Suppress the warning, it's the best we can do given that
|
/Zephyr-Core-3.5.0/doc/build/kconfig/ |
D | index.rst | 22 tips and best practices for writing :file:`Kconfig` files.
|
/Zephyr-Core-3.5.0/samples/sensor/max17262/ |
D | README.rst | 19 provides best performance for batteries with 100mAhr to 6Ahr capacity.
|
/Zephyr-Core-3.5.0/doc/security/ |
D | security-citations.rst | 49 Available: https://github.com/linuxfoundation/cii-best-practices-badge
|
/Zephyr-Core-3.5.0/drivers/display/ |
D | Kconfig.mcux_dcnano_lcdif | 23 Note that hardware will likely perform best if zero driver
|
D | Kconfig.mcux_elcdif | 23 Note that hardware will likely perform best if zero driver
|
/Zephyr-Core-3.5.0/samples/net/sockets/dumb_http_server/src/ |
D | response_big.html.bin | 27 … collaborative effort uniting leaders from across the industry to build a best-in-breed small, sca…
|
/Zephyr-Core-3.5.0/samples/net/sockets/dumb_http_server_mt/src/ |
D | response_big.html.bin | 27 … collaborative effort uniting leaders from across the industry to build a best-in-breed small, sca…
|
/Zephyr-Core-3.5.0/boards/arm/kv260_r5/doc/ |
D | index.rst | 78 Currently the best way to run this sample is by loading it through remoteproc 115 To avoid this limitation when accessing the Linux shell, the best approach is to
|
/Zephyr-Core-3.5.0/soc/arm/atmel_sam0/common/ |
D | Kconfig.saml2x | 16 resulting binary, or require the best possible boot time, say n.
|
/Zephyr-Core-3.5.0/doc/services/pm/ |
D | system.rst | 68 again. The core logic used by this policy to select the best power
|
/Zephyr-Core-3.5.0/ |
D | CODE_OF_CONDUCT.md | 20 * Focusing on what is best for the community
|
/Zephyr-Core-3.5.0/doc/project/ |
D | documentation.rst | 47 reports and using their name and identifier is the best way to identify them
|
/Zephyr-Core-3.5.0/cmake/modules/ |
D | FindZephyr-sdk.cmake | 75 # return a list of compatible versions and find the best suited version that
|
/Zephyr-Core-3.5.0/doc/build/dts/ |
D | bindings-upstream.rst | 132 specific drivers handling the nodes, it's usually best to use ``zephyr`` as 156 Driver developers should use their best judgment as to whether a value can be
|
/Zephyr-Core-3.5.0/share/zephyr-package/cmake/ |
D | ZephyrConfig.cmake | 146 # We are the best candidate, so let's include boiler plate.
|
D | ZephyrConfigVersion.cmake | 120 # We are the best candidate, so let's check our own version.
|
/Zephyr-Core-3.5.0/boards/posix/native_sim/doc/ |
D | index.rst | 59 and is therefore normally best to test and debug your code, as some bugs are
|
/Zephyr-Core-3.5.0/samples/boards/mimxrt595_evk_cm33/system_off/ |
D | README.rst | 78 fuses, it is best to write the OTP shadow registers first and confirm
|
/Zephyr-Core-3.5.0/doc/develop/ |
D | env_vars.rst | 34 This is best for experimentation. If you close your terminal window, use
|
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/ace/ |
D | ace-link.ld | 30 * best used for processor-local data (e.g. stacks) or shared data
|
/Zephyr-Core-3.5.0/samples/bluetooth/ipsp/ |
D | README.rst | 98 address. The best approach may be to reset your board after issuing
|
/Zephyr-Core-3.5.0/doc/connectivity/networking/ |
D | overview.rst | 173 functionality of the IP stack, but are not the best
|
/Zephyr-Core-3.5.0/scripts/kconfig/ |
D | menuconfig.py | 499 best = -1 506 best = color 508 return best
|
123