Searched full:puts (Results 1 – 25 of 62) sorted by relevance
123
7 puts "checking adapter speed..."
10 Do not use it directly. The generated bindings documentation puts these
34 # printing of scan results puts pressure on queues in new locking
14 Driving the XSHUT pin low puts the VL53L1X into hardware
28 * Tests the ISR interfaces. Test thread puts items into fifo2 and gives30 * puts items into fifo1. Child thread gives back control to the Test thread208 * @details Tests the ISR interfaces. Test thread puts items into fifo2210 * fifo2 and then puts items into fifo1. Child thread gives back control
44 The send functions puts frame int this queue and TX thread takes the
42 * stores UART input in it until EOL, and then puts it into in console_getline_init()
27 for demand paging. The qemu_x86_tiny.ld linker script puts
12 * for demand paging. The qemu_x86_tiny.ld linker script puts
148 puts
46 * Trace formatter puts data in the 16 byte long blocks.
79 # printing of scan results puts pressure on queues in new locking
11 * to z_thread_entry() since this arch puts the first four arguments
63 * not found in the cache. Releasing puts entry in idle list.
57 int puts(const char *s);
69 automatically puts the device into 4-byte address mode when the device
117 int puts(const char *s) in puts() function
28 #. Puts the current thread in the condition variable queue.
222 * This puts the stack into the pinned noinit linker section if254 * This puts the stack into the pinned noinit linker section if542 * This puts the stack into the pinned noinit linker section if599 * This puts the stack into the pinned noinit linker section if
112 /* a thread sleeps then puts data on the fifo */345 * puts data on the fifo on time. In second scenario test k_fifo_get with361 * Test fifo with some timeout and child thread that puts in ZTEST()
79 * Puts a character into console output buffer. It will be sent
50 * The system goes through a normal platform suspend where it puts51 * all of the cores in deepest possible idle state and *may* puts
