Home
last modified time | relevance | path

Searched refs:linked (Results 1 – 25 of 122) sorted by relevance

12345

/Zephyr-latest/doc/kernel/data_structures/
Ddlist.rst3 Double-linked List
6 Similar to the single-linked list in many respects, Zephyr includes a
7 double-linked implementation. This provides the same algorithmic
47 not a node is currently linked into a dlist or not (via an
50 Double-linked List Internals
97 Doubly-linked List API Reference
100 .. doxygengroup:: doubly-linked-list_apis
Dslist.rst3 Single-linked List
7 singly-linked list data (i.e. data where each list element stores a
65 Single-linked List Internals
91 single-linked list variants using the same basic primitives. The
117 Single-linked List API Reference
120 .. doxygengroup:: single-linked-list_apis
125 .. doxygengroup:: flagged-single-linked-list_apis
/Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/
Dapp.overlay61 linked-terminal = <&out_terminal>;
69 linked-terminal = <&in_terminal>;
/Zephyr-latest/boards/actinius/icarus/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/actinius/icarus_som/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/actinius/icarus_bee/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/nordic/nrf9131ek/
DKconfig.defconfig8 # For the secure version of the board the firmware is linked at the beginning
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/norik/octopus_io_board/
DKconfig.defconfig6 # For the secure version of the board the firmware is linked at the beginning
12 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/norik/octopus_som/
DKconfig.defconfig6 # For the secure version of the board the firmware is linked at the beginning
12 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/tests/subsys/usb/uac2/
Dapp.overlay81 linked-terminal = <&out_terminal>;
89 linked-terminal = <&in_terminal>;
128 linked-terminal = <&hs_out_terminal>;
/Zephyr-latest/boards/sparkfun/thing_plus/
DKconfig.defconfig9 # For the secure version of the board the firmware is linked at the beginning
15 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/innblue/innblue22/
DKconfig.defconfig8 # For the secure version of the board the firmware is linked at the beginning
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/innblue/innblue21/
DKconfig.defconfig8 # For the secure version of the board the firmware is linked at the beginning
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/actinius/icarus_som_dk/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
16 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/circuitdojo/feather/
DKconfig.defconfig9 # For the secure version of the board the firmware is linked at the beginning
15 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/nxp/lpcxpresso55s28/
DKconfig.defconfig20 # For the secure version of the board the firmware is linked at the beginning
26 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/nordic/nrf52840dongle/
DKconfig12 If selected, applications are linked so that they can be loaded by Nordic
/Zephyr-latest/boards/makerdiary/nrf52840_mdk_usb_dongle/
DKconfig12 If selected, applications are linked so that they can be loaded by Nordic
/Zephyr-latest/cmake/linker/armlink/
Dlinker_libraries.cmake6 # so we only need to set link order linking in case a custom C library is linked
/Zephyr-latest/boards/nordic/nrf9151dk/
DKconfig.defconfig8 # For the secure version of the board the firmware is linked at the beginning
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/nordic/nrf9160dk/
DKconfig.defconfig8 # For the secure version of the board the firmware is linked at the beginning
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/boards/nordic/nrf9161dk/
DKconfig.defconfig8 # For the secure version of the board the firmware is linked at the beginning
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
/Zephyr-latest/doc/kernel/object_cores/
Dindex.rst17 Objects of the same type are linked together via their respective object
18 cores to form a singly linked list. Each object core also links to the their
19 respective object type. Each object type contains a singly linked list
21 linked together via a singly linked list. Together, this can allow debugging
139 Two routines exist for walking the list of object cores linked to an object
/Zephyr-latest/include/zephyr/arch/x86/
Dmemory.ld11 * By default, the kernel is linked at its physical address and all addresses
17 * in RAM and are copied from flash at boot. Text/rodata linked in-place in
94 * linked in this space. Otherwise, rodata and text are linked at their
/Zephyr-latest/boards/nxp/lpcxpresso55s69/
DKconfig.defconfig18 # For the secure version of the board the firmware is linked at the beginning
24 # must be linked into the code-partition (non-secure) defined in DT, regardless.

12345