Home
last modified time | relevance | path

Searched full:respond (Results 1 – 25 of 130) sorted by relevance

123456

/Zephyr-latest/samples/bluetooth/periodic_adv_rsp/
DREADME.rst17 Multiple devices can synchronize and respond to one advertiser.
19 Which subevent to listen to and in which response slot to respond is
37 Zephyr tree that will synchronize and respond to this sample.
/Zephyr-latest/drivers/usb_c/tcpc/
DKconfig.tcpc_tcpci21 Some TCPCs are going into deep sleep mode when no charger is connected and won't respond
22 to the i2c address immediately. If device won't respond after retries, it means that
/Zephyr-latest/samples/net/mdns_responder/
DREADME.rst5 Listen and respond to mDNS queries.
11 respond to them. The default hostname is **zephyr** and it is set in the
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/dfu/
Ddfu_cli_all_targets_lost_on_caps_get.sh7 # Test if callback `lost_target` is called on every target that fails to respond to Caps Get message
Ddfu_cli_all_targets_lost_on_update_get.sh7 # Test if callback `lost_target` is called on every target that fails to respond to
/Zephyr-latest/doc/security/standards/
Dindex.rst8 of the problem and who to properly respond it.
/Zephyr-latest/samples/net/sockets/dumb_http_server_mt/
Dprj.conf46 # This is needed so that the sample app can respond to queries
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_cli.rst80 If a Target node fails to respond to an acknowledged message within the BLOB Transfer Client's time
100 to respond, or respond with incompatible transfer parameters, will be dropped.
/Zephyr-latest/samples/drivers/charger/
DREADME.rst22 the battery pack. Additionally, the sample intentionally does not respond to the reported charger
/Zephyr-latest/tests/drivers/fuel_gauge/bq27z746/src/
Dtest_bq27z746.c63 /* reprogrammed and respond with different values */ in ZTEST_USER_F()
78 /* reprogrammed and respond with different values */ in ZTEST_USER_F()
91 /* reprogrammed and respond with different values */ in ZTEST_USER_F()
/Zephyr-latest/samples/bluetooth/periodic_adv_conn/
DREADME.rst31 Zephyr tree that will synchronize and respond to this sample.
/Zephyr-latest/samples/bluetooth/periodic_sync_conn/
DREADME.rst5 Respond to periodic advertising and establish a connection.
/Zephyr-latest/dts/bindings/sdhc/
Dzephyr,sdhc-spi-slot.yaml19 Clock polarity to use for SPI SDHC. Some cards respond properly
/Zephyr-latest/subsys/net/
DKconfig.hostname9 This is used for example in mDNS to respond to <hostname>.local
/Zephyr-latest/subsys/net/lib/tftp/
DKconfig36 the request to the server in hopes that the server will respond within
/Zephyr-latest/samples/bluetooth/periodic_sync_rsp/
DREADME.rst16 Which subevent to listen to and in which response slot to respond is
/Zephyr-latest/tests/bsim/bluetooth/host/att/pipeline/test_scripts/
Drun_test_shall_not_pipeline_variant_rx_tx_prio_invert.sh22 # - Tester does not immediately respond but delays the response
Drun_test_tolerate_pipeline_variant_rx_tx_prio_invert.sh28 # - Or: The DUT may process and respond to the pipelined
/Zephyr-latest/dts/bindings/watchdog/
Dnxp,s32-swt.yaml32 Set this flag to generate a reset on respond to an invalid access.
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/bridge/
Dbrg_simple_va.sh36 # - To allow nodes to respond to the tester, messages from each node is bridged to the tester.
Dbrg_simple_group.sh36 # - To allow nodes to respond to the tester, messages from each node is bridged to the tester.
/Zephyr-latest/samples/net/dns_resolve/
DREADME.rst114 If you want Zephyr to respond to a LLMNR DNS request that Windows host is
124 A Zephyr host needs a hostname assigned to it so that it can respond to a DNS
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_hostname.rst15 details) and needs to respond to ``<hostname>.local`` DNS queries.
/Zephyr-latest/doc/hardware/peripherals/
Dcharger.rst17 host controller by setting the relevant properties, and can be adjusted at runtime to respond to
/Zephyr-latest/subsys/modbus/
Dmodbus_core.c95 bool respond = modbus_server_handler(ctx); in modbus_rx_handler() local
97 if (respond) { in modbus_rx_handler()
107 respond == false) { in modbus_rx_handler()

123456