Searched full:somewhat (Results 1 – 25 of 36) sorted by relevance
12
| /Zephyr-latest/dts/bindings/clock/ |
| D | st,stm32wb0-lsi-clock.yaml | 9 allows to adapt all frequency-based calculations to a somewhat accurate value, ensuring
|
| /Zephyr-latest/cmake/compiler/xcc/ |
| D | compiler_flags.cmake | 5 # XCC is based on GCC 4.2 which has a somewhat pedantic take on the
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | rbtree.rst | 50 implementation, at the cost of a somewhat more cumbersome API for the
98 intrusive, that cannot work. Zephyr must include somewhat more
116 somewhat unique to Zephyr.
|
| D | dlist.rst | 11 pointers per node, and thus has somewhat higher runtime code and
|
| /Zephyr-latest/scripts/net/ |
| D | enumerate_http_status.py | 11 The output may appear somewhat redundant but it strives
|
| /Zephyr-latest/soc/intel/intel_adsp/common/include/ |
| D | cpu_init.h | 49 * details of the fields are somewhat complicated, but per the in cpu_early_init()
|
| D | cavs-idc.h | 14 * is... somewhat needlessly complicated.
|
| /Zephyr-latest/lib/heap/ |
| D | Kconfig | 88 a higher runtime overhead and somewhat bigger code footprint.
|
| /Zephyr-latest/include/zephyr/arch/x86/intel64/ |
| D | thread.h | 57 * Architecturally-defined portion. It is somewhat tedious to
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.smp | 22 architecture provides both, _arch_switch incurs more somewhat
|
| /Zephyr-latest/tests/drivers/sensor/temp_sensor/src/ |
| D | main.c | 78 /* Set the upper threshold somewhat below the temperature read above. */ in ZTEST()
|
| /Zephyr-latest/dts/riscv/openisa/ |
| D | rv32m1_ri5cy.dtsi | 41 * INTMUX channels below are somewhat arbitrary.
|
| D | rv32m1_zero_riscy.dtsi | 41 * INTMUX channels below are somewhat arbitrary.
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_WINDOWS.rst | 50 The name "start" is somewhat confusing, this is not a pointer.
|
| D | README_MMU.txt | 4 management on Xtensa is somewhat unique. And there is similarly a
129 same way we do for data, but somewhat inexplicably, Xtensa does not
|
| /Zephyr-latest/tests/kernel/threads/dynamic_thread/src/ |
| D | main.c | 152 * case to simplify things somewhat. in ZTEST()
|
| /Zephyr-latest/tests/arch/x86/static_idt/src/ |
| D | main.c | 25 /* These vectors are somewhat arbitrary. We try and use unused vectors */
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | intc_sam0_eic_priv.h | 23 * Unfortunately the ASF headers define the EIC mappings somewhat painfully:
|
| /Zephyr-latest/scripts/coredump/gdbstubs/arch/ |
| D | xtensa.py | 115 # Somewhat arbitrary; included only because GDB requests it
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 6 this to work is somewhat involved, however.
|
| /Zephyr-latest/arch/x86/core/ia32/ |
| D | swap.S | 377 * GDB stack unwinder to stop somewhat gracefully.
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 112 queues will be somewhat slower (though this is not generally a performance
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 323 somewhat lower-level context switch primitives for SMP systems:
|
| /Zephyr-latest/drivers/i2c/ |
| D | i2c_xilinx_axi.c | 497 /* TX FIFO empty detection is somewhat fragile because the status register in i2c_xilinx_axi_write()
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 393 Today Zephyr includes at least two other systems that are somewhat comparable in scope and
|
12
