Searched refs:every (Results 1 – 25 of 318) sorted by relevance
12345678910>>...13
82 0: 1 conv every 16 sec83 1: 1 conv every 8 sec84 2: 1 conv every 4 sec85 3: 1 conv every 2 sec86 4: 1 conv every sec87 5: 2 convs every sec88 6: 4 convs every sec89 7: 8 convs every sec90 8: 16 convs every sec91 9: 32 convs every sec
19 is reported every 30 seconds.27 every 30 seconds.39 every 30 seconds.49 of a thread. The total number of context switches is reported every57 is reported every 30 seconds.64 This number is reported every 30 seconds.72 every 30 seconds.79 is reported every 30 seconds.
28 bool "Measurement every second"31 bool "Measurement every ten seconds"34 bool "Measurement every sixty seconds"37 bool "Measurement every 250 milliseconds"
11 of packet sockets over Ethernet. The sample prints every packet12 received, and sends a dummy packet every 5 seconds.21 packet every 5 seconds. You can use Wireshark to observe these
14 every devices. This driver does not provide such customizations. It15 just hardcodes sane default parameters for every devices.
8 # output being in the range of every few seconds to every few minutes. To
28 One block is needed for every chunk found in the SPI transaction and every 2048 bytes
12 VOC. The values are fetched and printed every second.20 This sample can run on every board with i2c.
11 every 2 seconds and prints them to console.36 you should get a similar output as below, repeated every 2 seconds:
40 The application will read and print sensor temperature every second. Note that49 <repeats endlessly every second>
11 int "Change direction every N revolutions"
14 Print statistics after every n. seconds
39 data every 2 seconds.52 <repeats endlessly every 2 seconds>
15 bool "Adds memory barrier after every address and data register access"
15 int "Change direction every N revolutions"
27 /* one entry for every devices at spi.dtsi */
29 /* one entry for every devices at spi.dtsi */
7 Generate the symbol table with the offset and name of every
18 be called every interval prior to this time elapsing to prevent a
8 the Zephyr project are released approximately every four months.26 The Zephyr project provides periodic releases every 4 months leading to the27 long term support releases approximately every 2 years. Periodic and non-LTS36 published every 2 years and is branched and maintained independently from the
9 # every time you run 'west update'.
