73c7c2da99
The response for the respective TWT operations can either be synchronous or asynchronous (wherever specified). If synchronous, the response to this operation is obtained in the corresponding vendor command reply to the user space. For asynchronous case, the response is obtained as an event with the same operation type. Drivers shall support either of these modes but not both simultaneously. The support for asynchronous mode is advertised through the new flag QCA_WLAN_VENDOR_FEATURE_TWT_ASYNC_SUPPORT. If the driver does not include this flag, it shall support synchronous mode. Signed-off-by: Jouni Malinen <jouni@codeaurora.org> |
||
---|---|---|
.. | ||
ap | ||
common | ||
crypto | ||
drivers | ||
eap_common | ||
eap_peer | ||
eap_server | ||
eapol_auth | ||
eapol_supp | ||
fst | ||
l2_packet | ||
p2p | ||
pae | ||
radius | ||
rsn_supp | ||
tls | ||
utils | ||
wps | ||
build.rules | ||
lib.rules | ||
Makefile | ||
objs.mk |