| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | connection_mgmt.rst | 12 :c:func:`bt_conn_ref` API whenever storing a connection pointer for a
14 (even if the connection would get disconnected). Similarly the
16 to a connection.
18 A common mistake is to forget unreleasing a reference to a connection
22 which forces these functions return an error if the connection pointer
24 sporadic bugs caused by not releasing the connection object.
29 define callbacks for connection & disconnection events, as well as other
30 events related to a connection such as a change in the security level or
31 the connection parameters. When acting as a central the application will
32 also get hold of the connection object through the return value of the
|
| /Zephyr-latest/samples/bluetooth/channel_sounding/src/ |
| D | connected_cs_initiator.c | 29 static struct bt_conn *connection; variable
105 __ASSERT(connection == conn, "Unexpected connected callback"); in connected_cb()
109 connection = NULL; in connected_cb()
114 err = bt_gatt_exchange_mtu(connection, &mtu_exchange_params); in connected_cb()
127 connection = NULL; in disconnected_cb()
194 if (connection) { in device_found()
216 &connection); in device_found()
267 err = bt_le_cs_set_default_settings(connection, &default_settings); in main()
272 err = bt_conn_set_security(connection, BT_SECURITY_L2); in main()
280 err = bt_le_cs_read_remote_supported_capabilities(connection); in main()
[all …]
|
| D | connected_cs_reflector.c | 27 static struct bt_conn *connection; variable
65 __ASSERT(connection == conn, "Unexpected connected callback"); in connected_cb()
69 connection = NULL; in connected_cb()
72 connection = bt_conn_ref(conn); in connected_cb()
76 err = bt_gatt_exchange_mtu(connection, &mtu_exchange_params); in connected_cb()
89 connection = NULL; in disconnected_cb()
202 err = bt_le_cs_set_default_settings(connection, &default_settings); in main()
213 err = bt_gatt_discover(connection, &discover_params); in main()
234 err = bt_gatt_write(connection, &write_params); in main()
|
| D | cs_test_reflector.c | 26 static struct bt_conn *connection; variable
74 __ASSERT(connection == conn, "Unexpected connected callback"); in connected_cb()
78 connection = NULL; in connected_cb()
81 connection = bt_conn_ref(conn); in connected_cb()
85 err = bt_gatt_exchange_mtu(connection, &mtu_exchange_params); in connected_cb()
98 connection = NULL; in disconnected_cb()
217 err = bt_gatt_discover(connection, &discover_params); in main()
235 err = bt_gatt_write(connection, &write_params); in main()
|
| D | cs_test_initiator.c | 26 static struct bt_conn *connection; variable
108 __ASSERT(connection == conn, "Unexpected connected callback"); in connected_cb()
112 connection = NULL; in connected_cb()
117 err = bt_gatt_exchange_mtu(connection, &mtu_exchange_params); in connected_cb()
130 connection = NULL; in disconnected_cb()
159 if (connection) { in device_found()
181 &connection); in device_found()
268 bt_conn_disconnect(connection, BT_HCI_ERR_REMOTE_USER_TERM_CONN); in main()
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/conn/ |
| D | Kconfig | 5 bool "Test 1 ms connection interval support"
7 Test 1 ms connection interval support.
|
| /Zephyr-latest/subsys/net/conn_mgr/ |
| D | Kconfig | 5 bool "Network connection manager [EXPERIMENTAL]"
12 When enabled, this will start the connection manager that will
21 module-str = Log level for connection manager
22 module-help = Enables connection manager code to output debug messages.
29 Sets the stack size which will be used by the connection manager for connectivity monitoring.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig.bluetooth | 48 bool "Request specific connection parameters for SMP packet exchange"
52 Enables support for requesting specific connection parameters when
60 int "Minimum connection interval for SMP packet exchange"
64 Minimum connection interval in 1.25ms units used during the exchange of SMP packets.
67 int "Maximum connection interval for SMP packet exchange"
71 Maximum connection interval in 1.25ms units used during the exchange of SMP packets.
93 connection parameters are restored to peripheral preferred values
101 In case connection parameters update fails due to an error, this
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.quectel-bg9x | 34 string "APN for establishing network connection"
37 This setting is used to set the APN name for the network connection
42 string "Username for establishing network connection"
45 This setting is used to set the User name for the network connection
50 string "Password for establishing network connection"
53 This setting is used to set the Password for the network connection
|
| /Zephyr-latest/boards/shields/adafruit_data_logger/ |
| D | adafruit_data_logger.overlay | 15 * LED1 connection must be manually established using a jumper between
23 * LED2 connection must be manually established using a jumper between
61 * Interrupt connection must be manually established using a jumper wire between
|
| /Zephyr-latest/samples/bluetooth/periodic_sync_conn/ |
| D | README.rst | 5 Respond to periodic advertising and establish a connection.
14 subevent data. Once the connection is established, it will disconnect and wait
15 for a new connection to be established.
|
| /Zephyr-latest/samples/bluetooth/hci_pwr_ctrl/ |
| D | README.rst | 18 Upon successful connection, the connection RSSI strength is being monitored and
19 the Tx power of the peripheral device is modulated per connection accordingly
21 connection is. The peripheral implements a simple GATT profile exposing the
|
| /Zephyr-latest/samples/bluetooth/central_multilink/ |
| D | README.rst | 5 Scan, connect and establish connection to up to 62 peripherals.
11 BLE devices and establishing connection to up to 62 peripherals with a strong
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 212 …s should provide means for applications to pre-configure all necessary connection parameters (for …
220 …s because the application pre-configured invalid connection parameters, or did not configure conne…
222 …connectivity implementation should not give up on the connection attempt, even if valid connection…
224 Instead, the connectivity implementation should asynchronously wait for valid connection parameters…
242 …* It is acceptable to gate this behind a small timeout (separate from the connection timeout) for …
284 …for the connectivity implementation to interpret this as an unexpected connection loss and immedia…
293 For instance, calls to :c:member:`conn_mgr_conn_api.connect` should initiate a connection process a…
395 Trigger :c:macro:`NET_EVENT_CONN_CMD_IF_TIMEOUT` when a connection :ref:`timeout <conn_mgr_control_…
398 Trigger :c:macro:`NET_EVENT_CONN_IF_FATAL_ERROR` when a fatal (non-recoverable) connection error oc…
420 …rlying technology automatically attempts to reconnect or retry connection after connection loss or…
[all …]
|
| /Zephyr-latest/samples/bluetooth/hap_ha/ |
| D | README.rst | 5 Advertise and await connection from a Hearing Aid Unicast Client or Remote Controller.
11 Starts advertising and awaits connection from a Hearing Aid Unicast Client (HAUC)
|
| /Zephyr-latest/samples/net/mqtt_publisher/ |
| D | Kconfig | 12 Send sample MQTT messages this many times in a MQTT connection
20 Number of times to connect to the MQTT server. With each connection
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 133 bool "Use a separate workqueue for connection TX notify processing [EXPERIMENTAL]"
144 int "Stack size of workqueue for connection TX notify processing"
148 int "Cooperative priority of workqueue for connection TX notify processing"
152 int "Init priority of workqueue for connection TX notify processing"
155 The connection TX notify processing workqueue is initialized during
336 bool "Accept any values for connection parameters"
338 Some controllers support additional connection parameter ranges
340 allows the application to set any value to all connection parameters.
342 connection parameters (conn interval min and max, latency and timeout).
344 min and max connection intervals in order to verify whether the
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | mqtt.rst | 96 establish a TCP/TLS connection, and send an ``MQTT CONNECT`` message.
100 If the connection was successful, ``MQTT_EVT_CONNACK`` will be notified to the
121 flag upon a successful connection. If the connection fails at the MQTT level
122 or a timeout occurs, the connection will be aborted, and the underlying socket
125 After the connection is established, an application needs to call ``mqtt_input``
127 the connection. If an MQTT message is received, an MQTT callback function will
130 The connection can be closed by calling the ``mqtt_disconnect`` function.
|
| /Zephyr-latest/samples/net/sockets/echo_service/ |
| D | README.rst | 48 After a connection is made, the application will echo back any line sent
50 sockets, and currently is only implemented to serve only one client connection
51 at time. After the current client disconnects, the next connection can proceed.
|
| /Zephyr-latest/samples/bluetooth/periodic_adv_conn/ |
| D | README.rst | 5 Initiate a connection to a device using the Periodic Advertising Connection Procedure.
15 responding with its address. Once the connection is established, it will
|
| /Zephyr-latest/tests/drivers/w1/w1_api/boards/ |
| D | nrf52840dk_nrf52840.overlay | 7 /* external connection of TX-pin to RX-pin needed */
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | usbnet_setup.rst | 42 To establish network connection to the board we need to choose IP address
68 connection depending on the board network configuration.
92 Testing connection
95 From the host we can test the connection by pinging Zephyr IP address of
|
| /Zephyr-latest/drivers/watchdog/ |
| D | Kconfig.ti_tps382x | 12 a GPIO connection from the processor.
|
| /Zephyr-latest/samples/net/sockets/echo/ |
| D | README.rst | 43 After a connection is made, the application will echo back any line sent
45 sockets, and thus can serve only one client connection at time. After the
46 current client disconnects, the next connection can proceed.
|
| /Zephyr-latest/samples/bluetooth/peripheral_accept_list/ |
| D | README.rst | 12 Once a device is bonded, on subsequent boots, connection requests will only be
19 to be bonded, while a read can be done immediately after a connection
|
