Searched refs:conn_mgr_conn_api (Results 1 – 5 of 5) sorted by relevance
246 static struct conn_mgr_conn_api test_conn_api_a = {254 static struct conn_mgr_conn_api test_conn_api_b = {260 static struct conn_mgr_conn_api test_conn_api_ni = {
41 struct conn_mgr_conn_api { struct128 struct conn_mgr_conn_api *api; argument
20 struct conn_mgr_conn_api *api; in conn_mgr_if_connect()57 struct conn_mgr_conn_api *api; in conn_mgr_if_disconnect()106 struct conn_mgr_conn_api *api; in conn_mgr_if_get_opt()142 struct conn_mgr_conn_api *api; in conn_mgr_if_set_opt()
24 …` struct, which then stores a reference to the passed in :c:struct:`conn_mgr_conn_api` struct (whi…29 … will be translated to the corresponding implementation functions in :c:struct:`conn_mgr_conn_api`.85 static struct conn_mgr_conn_api my_impl_api = {203 Each :c:struct:`implementation API function <conn_mgr_conn_api>` you implement should behave as-des…205 For example, your implementation of :c:member:`conn_mgr_conn_api.connect` should conform to the beh…235 * Set the iface to dormant, carrier-down, or both during :c:member:`binding init <conn_mgr_conn_api…293 For instance, calls to :c:member:`conn_mgr_conn_api.connect` should initiate a connection process a…295 One exception is :c:member:`conn_mgr_conn_api.init`, whose implementations are permitted to block.304 …mentations must be ready to receive API calls immediately after :c:member:`conn_mgr_conn_api.init`.306 …member:`conn_mgr_conn_api.connect` must eventually lead to an association attempt, even if called …[all …]
133 static struct conn_mgr_conn_api test_conn_api = {
