Searched refs:linked (Results 1 – 25 of 122) sorted by relevance
12345
/Zephyr-latest/doc/kernel/data_structures/ |
D | dlist.rst | 3 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
|
D | slist.rst | 3 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/ |
D | app.overlay | 61 linked-terminal = <&out_terminal>; 69 linked-terminal = <&in_terminal>;
|
/Zephyr-latest/boards/actinius/icarus/ |
D | Kconfig.defconfig | 10 # 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/ |
D | Kconfig.defconfig | 10 # 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/ |
D | Kconfig.defconfig | 10 # 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/ |
D | Kconfig.defconfig | 8 # 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/ |
D | Kconfig.defconfig | 6 # 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/ |
D | Kconfig.defconfig | 6 # 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/ |
D | app.overlay | 81 linked-terminal = <&out_terminal>; 89 linked-terminal = <&in_terminal>; 128 linked-terminal = <&hs_out_terminal>;
|
/Zephyr-latest/boards/sparkfun/thing_plus/ |
D | Kconfig.defconfig | 9 # 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/ |
D | Kconfig.defconfig | 8 # 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/ |
D | Kconfig.defconfig | 8 # 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/ |
D | Kconfig.defconfig | 10 # 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/ |
D | Kconfig.defconfig | 9 # 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/ |
D | Kconfig.defconfig | 20 # 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/ |
D | Kconfig | 12 If selected, applications are linked so that they can be loaded by Nordic
|
/Zephyr-latest/boards/makerdiary/nrf52840_mdk_usb_dongle/ |
D | Kconfig | 12 If selected, applications are linked so that they can be loaded by Nordic
|
/Zephyr-latest/cmake/linker/armlink/ |
D | linker_libraries.cmake | 6 # so we only need to set link order linking in case a custom C library is linked
|
/Zephyr-latest/boards/nordic/nrf9151dk/ |
D | Kconfig.defconfig | 8 # 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/ |
D | Kconfig.defconfig | 8 # 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/ |
D | Kconfig.defconfig | 8 # 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/ |
D | index.rst | 17 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/ |
D | memory.ld | 11 * 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/ |
D | Kconfig.defconfig | 18 # 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