Home
last modified time | relevance | path

Searched refs:initiated (Results 1 – 25 of 43) sorted by relevance

12

/Zephyr-latest/subsys/bluetooth/controller/ll_sw/
Dlll_conn.h76 uint8_t initiated:1; member
82 uint8_t initiated:1; member
89 uint8_t initiated:1; member
Dull_peripheral.c627 lll->periph.initiated = 0U;
/Zephyr-latest/drivers/watchdog/
DKconfig.xlnx21 API which allows determining whether the WDT initiated the last
/Zephyr-latest/samples/drivers/charger/
DREADME.rst17 - After the charge cycle is initiated, the sample application will check the status property of the
/Zephyr-latest/drivers/timer/
DKconfig.nrf_xrtc14 System clock source is initiated but does not wait for clock readiness.
/Zephyr-latest/doc/services/
Dnotify.rst7 operation is initiated and the application needs to be informed when it
/Zephyr-latest/drivers/espi/
DKconfig182 bool "OOB host-initiated traffic handling"
185 Enables asynchronous handling for host-initiated OOB traffic.
186 Otherwise OOB traffic is assumed to be always client-initiated.
/Zephyr-latest/doc/connectivity/bluetooth/api/
Dgatt.rst67 Discover procedures can be initiated with the use of
88 Subscriptions to notification and indication can be initiated with use of
Dl2cap.rst34 Client channels can be initiated with use of :c:func:`bt_l2cap_chan_connect`
/Zephyr-latest/doc/hardware/peripherals/
Dcharger.rst26 A charge cycle is initiated or terminated using :c:func:`charger_charge_enable`.
Di2c.rst43 transactions initiated by a different controller on the bus. It might
/Zephyr-latest/drivers/flash/
DKconfig.nordic_qspi_nor41 allow the write to proceed. Multiple transfers will be initiated
/Zephyr-latest/samples/sensor/lps22hh_i3c/
DREADME.rst35 Since IBI is initiated by the sensor, it will take over the I3C
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-ctlr-arch.rst187 * State machine handling local initiated procedures
200 * Naming concept: lp_<...> => local initiated procedure, rp_<...> => remote initiated procedure
/Zephyr-latest/soc/nordic/nrf52/
DKconfig85 clock so if clock is initiated in certain window, the clock may also fail
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/lll/
Dlll_scan.c359 (lll->conn->central.initiated ||
540 if (lll->conn && lll->conn->central.initiated) {
616 lll->conn && lll->conn->central.initiated) {
1235 lll->conn->central.initiated = 1U;
Dlll_scan_aux.c471 (lll->conn->central.initiated || in prepare_cb()
1073 lll->conn->central.initiated = 1U;
1555 lll->conn->central.initiated = 0U;
Dlll_adv.c951 (lll->conn->periph.initiated || lll->conn->periph.cancelled))) { in prepare_cb()
1639 lll->conn->periph.initiated = 1; in isr_rx_pdu()
Dlll_adv_aux.c1010 lll->conn->periph.initiated = 1; in isr_tx_connect_rsp()
/Zephyr-latest/subsys/usb/device/
DKconfig145 all offloaded operations initiated by the USB subsystem.
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/openisa/lll/
Dlll_adv.c333 if (unlikely(lll->conn && lll->conn->central.initiated)) { in prepare_cb()
920 lll->conn->central.initiated = 1; in isr_rx_pdu()
Dlll_scan.c140 if (unlikely(lll->conn && lll->conn->central.initiated)) { in prepare_cb()
827 lll->conn->central.initiated = 1;
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Drpr_cli.rst113 The three NPPI procedures can be initiated with the :c:func:`bt_mesh_reprovision_remote` call:
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dbap.rst142 Server initiated disable and release:
590 initiated.
/Zephyr-latest/drivers/bluetooth/hci/
DKconfig246 bool "Host auto-initiated Data Length Update quirk"

12