Home
last modified time | relevance | path

Searched refs:link (Results 201 – 225 of 356) sorted by relevance

12345678910>>...15

/Zephyr-latest/include/zephyr/arch/x86/
Dmemory.ld93 /* Linear address range to link the kernel. If non-XIP, everything is
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/
Dull_filter.c1514 static memq_link_t link; in target_resolve() local
1515 static struct mayfly mfy = {0, 0, &link, 0, NULL}; in target_resolve()
1584 static memq_link_t link; in prpa_cache_resolve() local
1585 static struct mayfly mfy = {0, 0, &link, 0, NULL}; in prpa_cache_resolve()
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/lll/
Dlll_adv_sync.c344 ull_rx_put_sched(rx->hdr.link, rx);
Dlll_adv_aux.c999 ull_rx_put(rx->hdr.link, rx); in isr_tx_connect_rsp()
1006 ull_rx_put_sched(rx->hdr.link, rx); in isr_tx_connect_rsp()
/Zephyr-latest/drivers/bluetooth/hci/
Dspi.c66 be transmitted across this HCI link
/Zephyr-latest/kernel/
DCMakeLists.txt34 # this directory, libkernel.a, link it with the application code
DKconfig.obj_core8 This option enables the object core framework. This will link
/Zephyr-latest/subsys/net/ip/
DKconfig.tcp183 To avoid overstressing a link reduce the transmission rate as soon as
241 about the active link to a specific neighbor by signaling recent
/Zephyr-latest/doc/connectivity/networking/
Doverview.rst101 and link-local multicast name resolution
143 Additionally these network technologies (link layers) are supported in
Dqemu_setup.rst252 socat PTY,link=/tmp/slip.devMAIN UNIX-LISTEN:/tmp/slip.sockMAIN &
262 socat PTY,link=/tmp/slip.devOTHER UNIX-LISTEN:/tmp/slip.sockOTHER &
/Zephyr-latest/modules/openthread/
DCMakeLists.txt125 kconfig_to_ot_option(CONFIG_OPENTHREAD_TREL OT_TREL "Enable TREL radio link for Thread over Infrast…
143 …READ_CLI_VENDOR_EXTENSION} CACHE STRING "Path to CMake file to define and link Openthread CLI vend…
/Zephyr-latest/doc/build/cmake/
Dindex.rst40 libraries that link with app are built. In this case, using ``PUBLIC``
41 would cause libraries that link with ``app`` to also include the
294 The link from the previous stage is repeated, this time with the missing
/Zephyr-latest/boards/renesas/ek_ra6m2/doc/
Dindex.rst116 SEGGER J-link's drivers are avaialbe at https://www.segger.com/downloads/jlink/
/Zephyr-latest/boards/renesas/fpb_ra6e1/doc/
Dindex.rst111 SEGGER J-link's drivers are avaialbe at https://www.segger.com/downloads/jlink/
/Zephyr-latest/doc/
DCMakeLists.txt275 COMMENT "Running Sphinx link check..."
/Zephyr-latest/doc/services/llext/
Dconfig.rst79 This will directly modify the contents of the buffer during the link
/Zephyr-latest/subsys/net/l2/wifi/
DKconfig38 being unreachable (IP Level) or unable to receive down link traffic
/Zephyr-latest/boards/electronut/nrf52840_blip/doc/
Dindex.rst183 .. _Store link: https://www.tindie.com/stores/ElectronutLabs/
/Zephyr-latest/boards/electronut/nrf52840_papyr/doc/
Dnrf52840_papyr.rst178 .. _Store link: https://www.tindie.com/stores/ElectronutLabs/
/Zephyr-latest/dts/xtensa/intel/
Dintel_adsp_ace20_lnl.dtsi422 compatible = "intel,adsp-hda-link-out";
435 compatible = "intel,adsp-hda-link-in";
/Zephyr-latest/drivers/dai/intel/ssp/
Dssp.c1938 struct ssp_intel_link_ctl *link; in dai_ssp_parse_tlv() local
1988 link = (struct ssp_intel_link_ctl *)&aux_tlv->val; in dai_ssp_parse_tlv()
1992 I2CLCTL_MLCS(link->clock_source), dai_ip_base(dp) + in dai_ssp_parse_tlv()
1995 ssp->link_clock = link->clock_source; in dai_ssp_parse_tlv()
1998 I2CLCTL_MLCS(link->clock_source), in dai_ssp_parse_tlv()
2001 LOG_INF("link clock_source %u", link->clock_source); in dai_ssp_parse_tlv()
/Zephyr-latest/drivers/tee/optee/
Doptee.c59 sys_dnode_t link; member
274 sys_dlist_append(&supp->reqs, &req->link); in optee_call_supp()
1065 sys_dlist_remove(&req->link); in optee_suppl_recv()
/Zephyr-latest/subsys/fs/
Dfuse_fs_access.c427 .link = NULL,
/Zephyr-latest/soc/intel/intel_adsp/common/
DCMakeLists.txt45 # header (our link generates lots of phdrs because of the disjoint
/Zephyr-latest/samples/philosophers/
DREADME.rst72 tools like OpenOCD and J-link to inspect thread data using ``info threads``.

12345678910>>...15