Home
last modified time | relevance | path

Searched full:responding (Results 1 – 25 of 39) sorted by relevance

12

/Zephyr-latest/samples/drivers/charger/
DREADME.rst24 responsibility of responding to these events falls on the user or the charger device implementation.
/Zephyr-latest/samples/bluetooth/periodic_adv_conn/
DREADME.rst15 responding with its address. Once the connection is established, it will
/Zephyr-latest/arch/x86/core/
Dcpuhalt.c34 * "After the IF flag is set, the processor begins responding to in arch_cpu_atomic_idle()
/Zephyr-latest/soc/intel/intel_adsp/ace/
Dpmc_interface.h50 * responding agent. When this bit is set it will prompt the PMC to execute the command placed in
/Zephyr-latest/subsys/mgmt/ec_host_cmd/backends/
Dec_host_cmd_backend_shi.h16 * when the EC is not in a state where it will ever get around to responding
/Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/
DREADME.rst12 to a remote MQTT broker, while responding to commands received over MQTT.
20 - Responding to commands received over the network (LED control)
/Zephyr-latest/subsys/net/lib/coap/
DKconfig205 Enable responding to the ./well-known/core service resource.
/Zephyr-latest/subsys/bluetooth/host/classic/
Drfcomm_internal.h165 * responding station have the C/R bit set to 0
/Zephyr-latest/samples/bluetooth/periodic_sync_conn/src/
Dmain.c90 printk("Responding with own addr: %s\n", addr_str); in recv_cb()
/Zephyr-latest/drivers/ethernet/
Dphy_gecko.c151 /* Verify that the PHY device is responding */ in phy_gecko_init()
/Zephyr-latest/samples/bluetooth/periodic_sync_rsp/src/
Dmain.c107 printk("Indication: subevent %d, responding in slot %d\n", info->subevent, in recv_cb()
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-arch.rst106 and responding with events and received data. A build of this type sets the
/Zephyr-latest/tests/bsim/bluetooth/host/l2cap/multilink_peripheral/src/
Ddut.c279 * responding. in entrypoint_dut()
/Zephyr-latest/subsys/bluetooth/audio/shell/
Dcsip_set_member.c66 "Responding with %s", addr, rsp_strings[sirk_read_rsp]); in sirk_read_req_cb()
Dcap_acceptor.c80 "Responding with %s", addr, rsp_strings[sirk_read_rsp]); in sirk_read_req_cb()
/Zephyr-latest/tests/bsim/bluetooth/mesh/src/
Dtest_provision.c803 /* stop responding for 30s to timeout PB-ADV link establishment. */ in test_device_unresponsive()
809 /* stop responding for 60s to timeout protocol */ in test_device_unresponsive()
1770 "Device: pb-adv provisioning, stops and resumes responding to provisioning"),
1777 "Device: used for remote provisioning, starts unprovisioned, stops responding"),
1808 "Provisioner: provisioning test, devices stop responding"),
/Zephyr-latest/dts/bindings/ethernet/
Dxlnx,gem.yaml56 instance. Set the address to 0 for auto-detection (first responding
/Zephyr-latest/tests/bsim/bluetooth/host/att/pipeline/dut/src/
Dmain.c346 * - no buffer allocation failures for responding to the good peer, in test_procedure_0()
/Zephyr-latest/doc/releases/
Drelease-notes-1.5.rst201 * ``ZEP-218`` - [drivers/nble][PTS_TEST] Fix responding with the wrong error codes to the Prepare W…
/Zephyr-latest/doc/contribute/
Dcontributor_expectations.rst154 the "Files changed" view. This allows responding to multiple comments and
/Zephyr-latest/modules/trusted-firmware-m/
DKconfig.tfm348 and can defer responding to a message while continuing to process
/Zephyr-latest/include/zephyr/drivers/usb_c/
Dusbc_pd.h85 * determine that its Port Partner is not responding after a Hard Reset.
92 * determine that its Port Partner is not responding after a Hard Reset.
/Zephyr-latest/subsys/bluetooth/mesh/
Ddfu_srv.c140 LOG_INF("Still applying, not responding"); in handle_info_get()
/Zephyr-latest/include/zephyr/net/
Ddns_resolve.h154 DNS_SOCKET_RESPONDER = 2 /**< Socket is used for responding (server type) */
/Zephyr-latest/tests/net/lib/lwm2m/interop/pytest/
Dleshan.py34 raise RuntimeError('Leshan not responding') from exc

12