Searched full:entirely (Results 1 – 25 of 55) sorted by relevance
123
17 # sram_code instead runs entirely from SRAM after being copied there.
14 entirely the responsibility of the device driver.
19 used. There is no device interface to these regulators as they are entirely
63 Use eMMC instead of SDIO (SD card) protocol. These are similar, but not entirely the same.
52 /* Check if the buffer is entirely contained in the region */ in mem_attr_check_buf()
65 entirely.
143 device, rather than suppressing it entirely. See also EARLY_CONSOLE
104 * @retval -ENOBUFS if the buffer is entirely allocated outside a memory region.
34 :ref:`sensor-read-and-decode`. Triggers are handled entirely differently for
46 entirely out of the loop in handling sensor events like FIFO watermarks.
287 * can be performed entirely from within ISRs.345 * is entirely safe given RTIO is designed to work from ISR context. in sample_rtio_write_read_async()
109 * automatically. For ISRs written in assembly it is entirely up to the125 * entirely.
25 * The C code here, starting from boot_core0(), is running entirely in
27 * entirely in software, the I2S API lacks appropriate timestamping. Therefore
43 # _sw_isr_table entirely.
14 * Window exceptions are handled entirely in the vector area and are very tight15 * for performance. The alloca exception is also handled entirely in the window
73 * This means that we must work entirely within registers in a single
32 rbnode is entirely opaque. It is not possible for the user to extract
115 The shared memory region is entirely used by a single FIFO.
50 These devices work entirely in RAM, so there is no "flash" process as
44 entirely on native_sim. Since we know that the I2C driver on the real hardware
232 * a ISR_DIRECT_PM() macro, or omitted entirely.
209 descriptors entirely. Meaning the hardware can potentially do more than ever.
226 of printk() output entirely. Output is sent immediately, without
331 * Caching is entirely on the onus of the client
