Home
last modified time | relevance | path

Searched full:adjacent (Results 1 – 25 of 29) sorted by relevance

12

/Zephyr-latest/include/zephyr/linker/
Dlinker-devnull.h41 /* Determine where to put the devnull region. It should be adjacent to the ROM
46 * adjacent to the ROM (e.g. ROM starts at 0 and RAM follows ROM). In that
66 #error "Cannot place devnull segment adjacent to ROM region."
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/radio/
Dradio_nrf5_ppi_resources.h119 * 2 adjacent PPIs (9 & 10) and 2 adjacent PPI groups are used for this wiring;
129 * 2 adjacent PPI groups are used for this wiring. 'index' must be 0 or 1.
140 * 2 adjacent PPIs (12 & 13) are used for this wiring; <index> must be 0 or 1.
193 /* The 2 adjacent PPI groups used for implementing SW_SWITCH_TIMER-based
Dradio_nrf5_ppi.h9 /* The 2 adjacent TIMER EVENTS_COMPARE event offsets used for implementing
330 /* The 2 adjacent PPI groups used for implementing SW_SWITCH_TIMER-based
336 /* The 2 adjacent TIMER EVENTS_COMPARE event offsets used for implementing
344 * 2 adjacent PPIs (9 & 10) and 2 adjacent PPI groups are used for this wiring;
363 * TASK ENABLE task. 2 adjacent PPI groups are used for this wiring.
374 * 2 adjacent PPIs (12 & 13) are used for this wiring; <index> must be 0 or 1.
583 /* The 2 adjacent TIMER EVENTS_COMPARE event offsets used for implementing PHYEND delay compensation
Dradio_nrf5_dppi_resources.h110 * 2 adjacent PPIs (14 & 15) and 2 adjacent PPI groups are used for this wiring;
168 /* The 2 adjacent PPI groups used for implementing SW_SWITCH_TIMER-based
Dradio_nrf5_dppi.h250 /* The 2 adjacent PPI groups used for implementing SW_SWITCH_TIMER-based
256 /* The 2 adjacent TIMER EVENTS_COMPARE event offsets used for implementing
262 /* The 2 adjacent TIMER EVENTS_COMPARE event offsets used for implementing
285 * 2 adjacent PPIs (14 & 15) and 2 adjacent PPI groups are used for this wiring;
359 /* The 2 adjacent TIMER EVENTS_COMPARE event offsets used for implementing PHYEND delay compensation
Dradio_nrf5_resources.h136 /* Allocate 2 adjacent channels for PHYEND delay compensation. Use the same channels as for
/Zephyr-latest/dts/bindings/display/
Dsolomon,ssd1322.yaml65 Map multiple adjacent segments to one pixel.
67 two adjacent pixel drivers to each physical pixel. By setting this to 2,
/Zephyr-latest/tests/drivers/audio/dmic_api/
DREADME.txt18 * Verify that invalid channel maps (R/R pair, non-adjacent channels) are
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dbrg_cfg.rst9 between specific devices in different, adjacent subnets without compromising security.
12 as Subnet Bridges, allowing controlled communication by relaying messages between nodes in adjacent
/Zephyr-latest/doc/_extensions/zephyr/domain/static/js/
Dcodesample-livesearch.js18 parent.normalize(); // Merge adjacent text nodes
/Zephyr-latest/tests/lib/heap_align/src/
Dmain.c21 * immediately with adjacent free blocks.
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst196 as the thread will simply not have permission to write to adjacent memory
207 placed immediately adjacent to the stack buffer. Stack overflows caught in this
/Zephyr-latest/tests/drivers/audio/dmic_api/src/
Dmain.c265 /* Verify that channel map without adjacent L/R pairs fails */
288 "non adjacent channels in map"); in ZTEST()
/Zephyr-latest/drivers/sensor/maxim/max30101/
DKconfig19 To reduce the amount of data throughput, adjacent samples (in each
/Zephyr-latest/tests/unit/rbtree/
Dmain.c107 /* Can't have adjacent red nodes */ in check_rbnode()
/Zephyr-latest/tests/kernel/mem_heap/k_heap_api/src/
Dtest_kheap_api.c69 /* These need to be adjacent in BSS */
/Zephyr-latest/doc/kernel/memory_management/
Dheap.rst77 combined with adjacent free blocks to prevent fragmentation.
/Zephyr-latest/include/zephyr/audio/
Ddmic.h146 * to be adjacent to each other.
/Zephyr-latest/include/zephyr/sys/
Dsys_heap.h36 * merged with adjacent free blocks. Allocations are attempted from a
/Zephyr-latest/drivers/i2c/
Di2c_numaker.c133 /* ACK last data byte, so to merge adjacent messages into one transaction */ in m_numaker_i2c_master_xfer_msg_read_last_byte()
216 LOG_WRN("Cannot merge adjacent messages, force I2C Repeat Start"); in m_numaker_i2c_master_xfer_msg_end()
/Zephyr-latest/drivers/input/
Dinput_kbd_matrix.c45 * simultaneously. A block can also be formed, with not adjacent in input_kbd_matrix_ghosting()
/Zephyr-latest/include/zephyr/arch/x86/ia32/
Dlinker.ld19 * placing all the sections adjacent to each other. There is also no separate
/Zephyr-latest/drivers/gpio/
Dgpio_mcp23xxx.c78 * two adjacent memory locations. Because the underlying `write_fn` always does a 16-bit write for
/Zephyr-latest/drivers/disk/
Dflashdisk.c309 * and write data never spans across adjacent blocks.
/Zephyr-latest/doc/hardware/porting/
Darch.rst586 it's possible to overshoot the guard and corrupt adjacent data structures
657 completely overshooting a minimally-sized guard and corrupting adjacent

12