Lines Matching full:manager

6 Connection Manager is a collection of optional Zephyr features that aim to allow applications to mo…
8 Using Connection Manager, applications can use a single abstract API to control network association…
12 Applications can also use Connection Manager to generically manage and use multiple connectivity te…
17 Connection Manager is split into the following two subsystems:
26     :alt: A simplified view of how Connection Manager integrates with Zephyr and the application.
29     A simplified view of how Connection Manager integrates with Zephyr and the application.
78 … Connection Manager also fires the following more specific ``CONNECTED`` / ``DISCONNECTED`` events:
114    /* Call this before Connection Manager monitoring initializes */
136 …nectivity events, you should register your listener(s) before Connection Manager monitoring initia…
181 Applications can request that ifaces be ignored by Connection Manager by calling :c:func:`conn_mgr_…
187 While ignored, the iface is treated by Connection Manager as though it were unready for network tra…
227 The following sections outline the basic operation of Connection Manager's connectivity control.
234 Before an iface can be commanded to associate or disassociate using Connection Manager, it must fir…
285 Connection Manager requires that all connectivity implementations support the following standard ke…
425 …By default, Connection Manager will automatically connect any :ref:`bound <conn_mgr_impl_binding>`…
433 …By default, Connection Manager will automatically take any bound iface admin-down if it has given …