Searched refs:times (Results 26 – 50 of 165) sorted by relevance
1234567
/Zephyr-latest/doc/hardware/peripherals/sensor/ |
D | channels.rst | 18 At times only :c:enum:`sensor_channel` is used but this should be considered
|
D | power_management.rst | 19 would be possible in the streaming case as the application informs the driver of usage at all times
|
/Zephyr-latest/dts/arm/st/f3/ |
D | stm32f334.dtsi | 42 sampling-times = <2 3 5 8 20 62 182 602>;
|
D | stm32f303.dtsi | 155 sampling-times = <2 3 5 8 20 62 182 602>; 172 sampling-times = <2 3 5 8 20 62 182 602>;
|
/Zephyr-latest/tests/benchmarks/sched/ |
D | README.rst | 19 It then iterates this many times, reporting timestamp latencies
|
/Zephyr-latest/samples/boards/nordic/system_off/ |
D | README.rst | 18 number of times system off was entered, and total uptime since initial power-on
|
/Zephyr-latest/tests/drivers/build_all/sensor/ |
D | Kconfig | 21 sensor range is 0..100, the test will run 5 times with expected values
|
/Zephyr-latest/tests/bsim/bluetooth/host/gatt/ccc_store/src/ |
D | central.c | 288 void run_central(int times) in run_central() argument 321 for (int i = 0; i < times; i++) { in run_central()
|
D | peripheral.c | 263 void run_peripheral(int times) in run_peripheral() argument 300 for (int i = 0; i < times; i++) { in run_peripheral()
|
/Zephyr-latest/subsys/dfu/ |
D | Kconfig | 76 on some hardware that has long erase times, to prevent long wait 77 times at the beginning of the DFU process.
|
/Zephyr-latest/dts/arm/st/f4/ |
D | stm32f446.dtsi | 120 sampling-times = <3 15 28 56 84 112 144 480>; 137 sampling-times = <3 15 28 56 84 112 144 480>;
|
/Zephyr-latest/dts/arm/st/g4/ |
D | stm32g491.dtsi | 67 sampling-times = <3 7 13 25 48 93 248 641>;
|
/Zephyr-latest/soc/atmel/sam/common/ |
D | Kconfig | 49 With default of MULA == N, and DIVA == 1 the PLL will run at N+1 times 63 With default of MULA == N, and DIVA == 1 the PLL will run at N+1 times
|
/Zephyr-latest/doc/services/storage/zms/ |
D | zms.rst | 251 \small\frac{(NUM\_SECTORS - 1) \times (SECTOR\_SIZE - (5 \times ATE\_SIZE))}{2} 263 For example for 4 sectors of 1024 bytes, free space for data is :math:`\frac{3 \times 944}{2} = 141… 279 Total data that could be stored in this partition for this case is :math:`11 \times 3 \times 64 = 2… 295 16 bytes is needed. This operation is 256 times faster in this case. 309 life expectancy which is determined by the number of times memory cells can be erased/written. 320 :math:`\frac{(944 \times 4)}{16} = 236 \text{ minutes}`. 326 For storage devices that could be written 20000 times, the storage will last about 341 …\small\frac{(SECTOR\_EFFECTIVE\_SIZE \times SECTOR\_NUMBER \times MAX\_NUM\_WRITES)}{(TOTAL\_EFFEC…
|
/Zephyr-latest/samples/drivers/eeprom/ |
D | README.rst | 54 Device booted 7 times.
|
/Zephyr-latest/subsys/pm/policy/ |
D | Kconfig | 15 on CPU residency times and other constraints imposed by the drivers or
|
/Zephyr-latest/tests/arch/arc/arc_dsp_sharing/ |
D | README.txt | 13 times).
|
/Zephyr-latest/tests/benchmarks/wait_queues/ |
D | README.rst | 17 times. However, if the verbose option is enabled then the raw timings will also
|
/Zephyr-latest/doc/develop/test/twister/ |
D | twister_blackbox.rst | 94 Call Twister multiple times in one test? 101 If we just call the ``importlib`` 's ``exec_module`` two times, we will experience log 102 duplication. ``twister.log`` will duplicate every line (triplicate if we call it three times, etc.)
|
/Zephyr-latest/subsys/testsuite/ztest/ |
D | Kconfig | 156 This is used to execute a test suite N number of times. 163 This is used to execute a test case N number of times. 178 This rule will execute a test suite N number of times. 184 This rule will execute a test N number of times.
|
/Zephyr-latest/drivers/wifi/simplelink/ |
D | Kconfig.simplelink | 40 The number of times, separated by a one second interval, to retry
|
/Zephyr-latest/subsys/mgmt/osdp/ |
D | Kconfig.cp | 43 defined the number of times such a POLL command is sent per second.
|
/Zephyr-latest/doc/kernel/services/synchronization/ |
D | mutexes.rst | 23 * A **lock count** that indicates the number of times the mutex has been locked 59 of times before the mutex becomes fully unlocked so it can be claimed 81 the high priority waiting thread times out), the kernel restores the thread's
|
/Zephyr-latest/doc/services/storage/stream/ |
D | stream_flash.rst | 18 in faster response times seen from the application.
|
/Zephyr-latest/samples/drivers/watchdog/ |
D | README.rst | 47 Feeding watchdog 5 times
|
1234567