Searched full:connectivity (Results 1 – 25 of 377) sorted by relevance
12345678910>>...16
/Zephyr-Core-3.6.0/include/zephyr/net/ |
D | conn_mgr_connectivity_impl.h | 9 * @brief API for defining conn_mgr connectivity implementations (allowing ifaces to be used with 27 * @brief Connection Manager Connectivity Implementation API 28 * @defgroup conn_mgr_connectivity_impl Connection Manager Connectivity Implementation API 37 * @brief Connectivity Manager Connectivity API structure 43 * @brief When called, the connectivity implementation should start attempting to 44 * establish connectivity (association with a network) for the bound iface pointed 54 * @brief When called, the connectivity implementation should disconnect (dissasociate), or 65 * @brief Called once for each iface that has been bound to a connectivity implementation 68 * Connectivity implementations should use this callback to perform any required 79 * Used to set implementation-specific connectivity settings. [all …]
|
D | conn_mgr_connectivity.h | 26 * @brief Connection Manager Connectivity API 27 * @defgroup conn_mgr_connectivity Connection Manager Connectivity API 35 /* Connectivity Events */ 56 * @brief net_mgmt event raised when a non-recoverable connectivity error occurs on an iface 63 * @brief Per-iface connectivity flags 69 * When set, indicates that the connectivity implementation bound to this iface should 70 * attempt to persist connectivity by automatically reconnecting after connection loss. 104 * If the provided iface has been bound to a connectivity implementation, initiate 114 * @retval -ENOTSUP if the iface does not have a connectivity implementation. 122 * If the provided iface has been bound to a connectivity implementation, disconnect/dissassociate [all …]
|
/Zephyr-Core-3.6.0/doc/connectivity/networking/conn_mgr/ |
D | main.rst | 6 …Zephyr features that aim to allow applications to monitor and control connectivity (access to IP-c… 10 This allows an application to potentially support several very different connectivity technologies … 12 Applications can also use Connection Manager to generically manage and use multiple connectivity te… 19 …Connectivity monitoring <conn_mgr_monitoring>` (header file :file:`include/zephyr/net/conn_mgr_mon… 21 * :ref:`Connectivity control <conn_mgr_control>` (header file :file:`include/zephyr/net/conn_mgr_co… 35 Connectivity monitoring 38 Connectivity monitoring tracks all available ifaces (whether or not they support :ref:`Connectivity… 64 …he iface's :ref:`L2 implementation <net_l2_interface>` or bound :ref:`connectivity implementation … 70 …:`network management <net_mgmt_interface>` event is triggered, and IP connectivity is said to be r… 74 …:`network management <net_mgmt_interface>` event is triggered, and IP connectivity is said to be u… [all …]
|
D | implementation.rst | 3 Connectivity Implementations 11 Connectivity implementations are technology-specific modules that allow specific Zephyr ifaces to s… 12 They are responsible for translating generic :ref:`connectivity control API <conn_mgr_control_api>`… 15 …delines <conn_mgr_impl_guidelines>` for details on writing conformant connectivity implementations. 22 The :ref:`implementation API <conn_mgr_impl_api>` allows connectivity implementations to be :ref:`d… 27 Make sure not to accidentally bind two connectivity implementations to a single iface. 29 Once the iface is bound, :ref:`connectivity control API <conn_mgr_control_api>` functions can be ca… 35 This binding structure will contain a reference to the bound iface, the connectivity implementation… 37 This iterable section can then be iterated over to find out what (if any) connectivity implementati… 38 This search process is used by most of the functions in the :ref:`connectivity control API <conn_mg… [all …]
|
/Zephyr-Core-3.6.0/tests/net/conn_mgr_monitor/src/ |
D | main.c | 72 /** The total number of connectivity events fired by conn_mgr_monitor */ 182 "No events should be fired if connectivity availability did not change."); in cycle_ready_ifaces() 187 /* Expect connectivity gained */ in cycle_ready_ifaces() 191 "NET_EVENT_L4_CONNECTED should be fired when connectivity is gained."); in cycle_ready_ifaces() 193 "Only NET_EVENT_L4_CONNECTED should be fired when connectivity is gained."); in cycle_ready_ifaces() 203 "No events should be fired if connectivity availability did not change."); in cycle_ready_ifaces() 212 "No events should be fired if connectivity availability did not change."); in cycle_ready_ifaces() 217 /* Expect connectivity loss */ in cycle_ready_ifaces() 221 "NET_EVENT_L4_DISCONNECTED should be fired when connectivity is lost."); in cycle_ready_ifaces() 223 "Only NET_EVENT_L4_DISCONNECTED should be fired when connectivity is lost."); in cycle_ready_ifaces() [all …]
|
/Zephyr-Core-3.6.0/subsys/net/conn_mgr/ |
D | Kconfig | 29 Sets the stack size which will be used by the connection manager for connectivity monitoring. 43 bool "Generic WiFi management connectivity implementation" 46 Enable CONNECTIVITY_WIFI_MGMT connectivity bindings on WiFi drivers. 50 prompt "Implementation of the generic wifi_mgmt connectivity backend" 55 bool "Application specific implementation of the connectivity backend"
|
/Zephyr-Core-3.6.0/drivers/bluetooth/hci/ |
D | Kconfig.infineon | 13 Enable Infineon CYW4343W BLE connectivity, 15 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 20 Enable Infineon CYW4373 BLE connectivity, 22 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 27 Enable Infineon CYW43012 BLE connectivity, 29 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 34 Enable Infineon CYW43438 BLE connectivity, 36 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 41 Enable Infineon CYW43439 BLE connectivity, 43 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy…
|
/Zephyr-Core-3.6.0/drivers/wifi/infineon/ |
D | Kconfig.airoc | 47 Enable Infineon AIROC CYW4343W Wi-Fi connectivity, 49 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 54 Enable Infineon AIROC CYW4373 Wi-Fi connectivity, 56 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 61 Enable Infineon AIROC CYW43012 Wi-Fi connectivity, 63 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 68 Enable Infineon AIROC CYW43438 Wi-Fi connectivity, 70 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy… 75 Enable Infineon AIROC CYW43439 Wi-Fi connectivity, 77 …https://www.infineon.com/cms/en/product/wireless-connectivity/airoc-wi-fi-plus-bluetooth-combos/cy…
|
/Zephyr-Core-3.6.0/doc/_doxygen/ |
D | groups.dox | 42 @brief Connectivity 43 @defgroup connectivity Connectivity 49 @ingroup connectivity
|
/Zephyr-Core-3.6.0/tests/net/conn_mgr_conn/src/ |
D | test_ifaces.c | 32 * iface a1 and a2 share L2 connectivity implementation a 33 * iface b uses connectivity implementation b 69 /* Create an ifaces with NULL implementation, NULL init, and no connectivity at all */ 104 /* Bind L2 connectivity implementations to ifaces */ 109 /* Bind edge-case L2 connectivity implementations to ifaces */
|
D | test_conn_impl.h | 58 /* Create test L2 connectivity implementations A and B 71 /* Create an invalid L2 connectivity implementation with NULL API */ 75 /* Create an L2 connectivity implementation without the optional init */
|
/Zephyr-Core-3.6.0/boards/arm/pan1781_evb/doc/ |
D | index.rst | 32 `Panasonic Wireless Connectivity Development Hub`_. 45 `download section`_ of the `Panasonic Wireless Connectivity Development Hub`_. 54 .. _product website: https://industry.panasonic.eu/products/devices/wireless-connectivity/bluetooth… 55 .. _Panasonic Wireless Connectivity Development Hub: https://pideu.panasonic.de/development-hub/
|
/Zephyr-Core-3.6.0/boards/arm/pan1782_evb/doc/ |
D | index.rst | 32 `Panasonic Wireless Connectivity Development Hub`_. 45 `download section`_ of the `Panasonic Wireless Connectivity Development Hub`_. 55 .. _product website: https://industry.panasonic.eu/products/devices/wireless-connectivity/bluetooth… 56 .. _Panasonic Wireless Connectivity Development Hub: https://pideu.panasonic.de/development-hub/
|
/Zephyr-Core-3.6.0/boards/arm/pan1770_evb/doc/ |
D | index.rst | 34 `Panasonic Wireless Connectivity Development Hub`_. 47 `download section`_ of the `Panasonic Wireless Connectivity Development Hub`_. 56 .. _product website: https://industry.panasonic.eu/products/devices/wireless-connectivity/bluetooth… 57 .. _Panasonic Wireless Connectivity Development Hub: https://pideu.panasonic.de/development-hub/
|
/Zephyr-Core-3.6.0/boards/arm/pan1780_evb/doc/ |
D | index.rst | 33 `Panasonic Wireless Connectivity Development Hub`_. 46 `download section`_ of the `Panasonic Wireless Connectivity Development Hub`_. 55 .. _product website: https://industry.panasonic.eu/products/devices/wireless-connectivity/bluetooth… 56 .. _Panasonic Wireless Connectivity Development Hub: https://pideu.panasonic.de/development-hub/
|
/Zephyr-Core-3.6.0/samples/net/sockets/echo_client/boards/ |
D | qemu_cortext_m3.conf | 1 # The addresses are selected so that qemu<->qemu connectivity works ok. 2 # For linux<->qemu connectivity, create a new conf file and swap the
|
D | qemu_x86.conf | 1 # The addresses are selected so that qemu<->qemu connectivity works ok. 2 # For linux<->qemu connectivity, create a new conf file and swap the
|
/Zephyr-Core-3.6.0/boards/arm/bl5340_dvk/ |
D | bl5340_dvk_cpuapp_ns.dts | 2 * Copyright (c) 2021 Laird Connectivity 12 model = "Laird Connectivity BL5340 (nRF5340) Application";
|
D | bl5340_dvk_cpuapp.dts | 2 * Copyright (c) 2021 Laird Connectivity 12 model = "Laird Connectivity BL5340 (nRF5340) Application";
|
D | bl5340_dvk_cpunet.dts | 2 * Copyright (c) 2021-2023 Laird Connectivity 13 model = "Laird Connectivity BL5340 (nRF5340) Network";
|
/Zephyr-Core-3.6.0/include/zephyr/net/conn_mgr/ |
D | connectivity_wifi_mgmt.h | 9 * @brief Connectivity implementation for drivers exposing the wifi_mgmt API 22 * Context type for generic WIFI_MGMT connectivity backend.
|
/Zephyr-Core-3.6.0/boards/arm/pan1783/doc/ |
D | index.rst | 43 for the Evaluation Boards in the `Panasonic Wireless Connectivity Development Hub`_. 55 of the `Panasonic Wireless Connectivity Development Hub`_. 66 .. _product website: https://industry.panasonic.eu/products/devices/wireless-connectivity/bluetooth… 67 .. _Panasonic Wireless Connectivity Development Hub: https://pideu.panasonic.de/development-hub/
|
/Zephyr-Core-3.6.0/samples/net/sockets/echo_client/ |
D | prj.conf | 39 # The addresses are selected so that qemu<->qemu connectivity works ok. 40 # For linux<->qemu connectivity, create a new conf file and swap the
|
/Zephyr-Core-3.6.0/tests/bsim/net/sockets/echo_test/ |
D | prj.conf | 41 # The addresses are selected so that qemu<->qemu connectivity works ok. 42 # For linux<->qemu connectivity, create a new conf file and swap the
|
/Zephyr-Core-3.6.0/soc/arm/st_stm32/stm32f1/ |
D | Kconfig.soc | 55 Connectivity line devices are STM32F105xx and STM32F107xx 57 connectivity and real-time performances are required such as
|
12345678910>>...16