Searched refs:near (Results 1 – 18 of 18) sorted by relevance
| /Zephyr-latest/tests/kernel/timer/timer_api/src/ |
| D | timer_convert.c | 52 TESTFUNC(ms, cyc, near, 32)
53 TESTFUNC(ms, cyc, near, 64)
58 TESTFUNC(ms, ticks, near, 32)
59 TESTFUNC(ms, ticks, near, 64)
64 TESTFUNC(us, cyc, near, 32)
65 TESTFUNC(us, cyc, near, 64)
70 TESTFUNC(us, ticks, near, 32)
71 TESTFUNC(us, ticks, near, 64)
76 TESTFUNC(cyc, ms, near, 32)
77 TESTFUNC(cyc, ms, near, 64)
[all …]
|
| /Zephyr-latest/samples/sensor/sm351lt/ |
| D | README.rst | 11 and displays if a magnet near to the sensor, via the console.
|
| /Zephyr-latest/tests/drivers/regulator/voltage/boards/ |
| D | rpi_pico.overlay | 11 * In the rpi_pico board, a short, thick, diagonal wiring pattern near the 3x3
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | returnvar.cocci | 7 // Comments: Comments on code can be deleted if near code that is removed.
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.x86 | 47 from the handling, and the near-instruction-cycle resolution
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | index.rst | 33 in the near future :ref:`sensor-fetch-and-get` will be deprecated in favor of
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 82 systems I've tried, EFI uses memory near the top of 32-bit-accessible
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 53 "near" (round to nearest). Finally the output precision can be
176 interrupt latency interactions) that they occur near tick boundaries
231 per-CPU tracking, and expects that if two timer interrupts fire near
|
| /Zephyr-latest/boards/96boards/neonkey/doc/ |
| D | index.rst | 181 header available at the bottom of the board, near RST button.
|
| /Zephyr-latest/boards/arduino/due/doc/ |
| D | index.rst | 62 For I2C, pull-up resistors are required for using SCL1 and SDA1 (near IO13).
|
| /Zephyr-latest/boards/arduino/nano_33_ble/doc/ |
| D | index.rst | 125 and there should be a pulsing orange LED near the USB port.
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | generation.rst | 33 code source tree near their specific component (such as ``/samples`` and
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | demand_paging.rst | 31 in anticipation that they are required in the near future. This is used to
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 474 * Put this near the top of the file. After the includes is a good place.
495 * Put this near the end of the file, e.g. after defining "my_api_funcs".
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 47 expects network activity in the near future.
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 196 reasonable hardware these regions will be near each other)
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/doc/ |
| D | index.rst | 325 The USB connector at the top left of the board (near the RESET button) is
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 204 details link near the end of the PR conversation list. See
|
