Searched refs:connection (Results 1 – 25 of 293) sorted by relevance
12345678910>>...12
| /Zephyr-Core-3.7.0/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.
21 define callbacks for connection & disconnection events, as well as other
22 events related to a connection such as a change in the security level or
23 the connection parameters. When acting as a central the application will
24 also get hold of the connection object through the return value of the
|
| /Zephyr-Core-3.7.0/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig.bluetooth | 32 Enables encrypted and authenticated connection requirement to
36 bool "Request specific connection parameters for SMP packet exchange"
40 Enables support for requesting specific connection parameters when
48 int "Minimum connection interval for SMP packet exchange"
52 Minimum connection interval in 1.25ms units used during the exchange of SMP packets.
55 int "Maximum connection interval for SMP packet exchange"
59 Maximum connection interval in 1.25ms units used during the exchange of SMP packets.
81 connection parameters are restored to peripheral preferred values
89 In case connection parameters update fails due to an error, this
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/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
|
| D | Kconfig.ublox-sara-r4 | 56 string "APN for establishing network connection"
60 for the network connection context. This value is specific to
77 string "MCC/MNOfor establishing network connection"
80 for the network connection context. This value is specific to
|
| D | Kconfig.simcom-sim7080 | 45 string "APN for establishing a network connection"
48 This setting is used to set the APN name for the network connection
|
| D | Kconfig.wncm14a2a | 32 string "APN name for establishing network connection"
36 for the network connection context. Normally, don't need to change
|
| /Zephyr-Core-3.7.0/samples/bluetooth/hci_pwr_ctrl/ |
| D | README.rst | 17 Upon successful connection, the connection RSSI strength is being monitored and
18 the Tx power of the peripheral device is modulated per connection accordingly
20 connection is. The peripheral implements a simple GATT profile exposing the
|
| /Zephyr-Core-3.7.0/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
60 * Interrupt connection must be manually established using a jumper wire between
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/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.
|
| D | mqtt_sn.rst | 97 If the connection was successful, ``MQTT_SN_EVT_CONNECTED`` will be notified to the
114 flag upon a successful connection. If the connection fails at the MQTT level
115 or a timeout occurs, the connection will be aborted.
117 After the connection is established, an application needs to call ``mqtt_input``
123 The connection can be closed by calling the ``mqtt_sn_disconnect`` function. This
|
| /Zephyr-Core-3.7.0/samples/bluetooth/periodic_sync_conn/ |
| D | README.rst | 13 subevent data. Once the connection is established, it will disconnect and wait
14 for a new connection to be established.
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/subsys/bluetooth/host/ |
| D | Kconfig.gatt | 67 connection to a peer is established.
77 Quirk: upon re-establishing a bonded connection, assumes the remote
217 This option if enabled allows automatically sending request for connection
218 parameters update after GAP recommended 5 seconds of connection as
222 bool "Configure peripheral preferred connection parameters"
226 This allows to configure peripheral preferred connection parameters.
228 If disabled it is up to application to set expected connection parameters.
232 int "Peripheral preferred minimum connection interval in 1.25ms units"
239 int "Peripheral preferred maximum connection interval in 1.25ms units"
275 Enabling this option requires the connection to be encrypted to write
[all …]
|
| D | Kconfig | 297 bool "Accept any values for connection parameters"
299 Some controllers support additional connection parameter ranges
301 allows the application to set any value to all connection parameters.
303 connection parameters (conn interval min and max, latency and timeout).
305 min and max connection intervals in order to verify whether the
306 desired parameters have been established in the connection.
314 changes on the connection. The current PHY info is available in the
315 connection info.
322 Initiate PHY Update Procedure on connection establishment.
334 about Data Length changes on the connection. The current Data Length
[all …]
|
| /Zephyr-Core-3.7.0/subsys/mgmt/hawkbit/ |
| D | Kconfig | 115 bool "Use TLS for hawkBit server connection"
118 Use TLS for hawkBit connection.
129 Use static certificate tag for TLS connection to the hawkBit server.
135 Use dynamic certificate tag for TLS connection to the hawkBit server.
144 Static certificate tag for TLS connection to the hawkBit server.
|
| /Zephyr-Core-3.7.0/tests/drivers/w1/w1_api/boards/ |
| D | nrf52840dk_nrf52840.overlay | 7 /* external connection of TX-pin to RX-pin needed */
|
| /Zephyr-Core-3.7.0/subsys/net/ip/ |
| D | CMakeLists.txt | 32 zephyr_library_sources_ifdef(CONFIG_NET_IP connection.c)
53 zephyr_library_sources_ifdef(CONFIG_NET_CONNECTION_SOCKETS connection.c)
|
| /Zephyr-Core-3.7.0/samples/bluetooth/peripheral_accept_list/ |
| D | README.rst | 11 Once a device is bonded, on subsequent boots, connection requests will only be
18 to be bonded, while a read can be done immediately after a connection
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/drivers/watchdog/ |
| D | Kconfig.ti_tps382x | 12 a GPIO connection from the processor.
|
| /Zephyr-Core-3.7.0/doc/services/device_mgmt/ |
| D | ota.rst | 10 devices using a network connection. Although the name implies a wireless
11 connection, updates received over a wired connection (such as Ethernet)
31 this implementation, the connection between cloud and device is secured using
|
12345678910>>...12
