Lines Matching full:userspace
31 * This header file defines the userspace API to the wireless stack. Please
89 * Frame transmission and registration support exists to allow userspace
99 * that userspace registers for will not be returned as unhandled by the
114 * Frame transmission allows userspace to send for example the required
233 * below additional parameters to userspace, which can be either after setting
238 * %Nl80211_ATTR_PMK - used to update PMKSA cache in userspace
239 * The PMKSA can be maintained in userspace persistently so that it can be used
312 * With this capability, for FILS key derivation, drivers depend on userspace.
314 * After FILS key derivation, userspace shares the FILS AAD details with the
377 * be sent from userspace to request creation of a new virtual interface,
382 * userspace to request deletion of a virtual interface, then requires
486 * store this as a valid request and then query userspace for it.
536 * are used. Extra IEs can also be passed from the userspace by
574 * @NL80211_CMD_REG_CHANGE: indicates to userspace the regulatory domain
584 * @NL80211_CMD_REG_BEACON_HINT: indicates to userspace that an AP beacon
596 * userspace the wiphy on which we removed a restriction from
619 * MLME SAP interface (kernel providing MLME, userspace SME). The
690 * userspace asks the driver to perform PMKSA caching with BSS1 and the
713 * Following a %NL80211_CMD_ROAM event userspace can issue
717 * userspace that a connection was dropped by the AP or due to other
753 * (via @NL80211_CMD_FRAME) for processing in userspace. This command
862 * notification, userspace may decide to create a new station
864 * reoccurring, the userspace authentication daemon may want to create the
888 * inform userspace of the new replay counter.
890 * @NL80211_CMD_PMKSA_CANDIDATE: This is used as an event to inform userspace
894 * In addition, this can be used as an event to request userspace to take
942 * independently of the userspace SME, send this event indicating
953 * after %NL80211_ATTR_CH_SWITCH_COUNT TBTT's. The userspace may
966 * notify userspace that AP has rejected the connection request from a
986 * this event. This command is also used to notify userspace about radars
1017 * new channel. Userspace provides the new channel information (using
1042 * userspace via the normal management RX/TX framework, this only sets
1106 * returns, so userspace shouldn't process NAN events until it processes
1166 * to trigger the authentication and command response (userspace to
1279 * userspace wants to change the BSS color.
1321 * @NL80211_CMD_LINKS_REMOVED: Notify userspace about the removal of STA MLD
1715 * also be used by userspace to query the kernel for the currently set
1836 * to be used then userspace must also use the %NL80211_ATTR_SOCKET_OWNER
1891 * dumped changes, and as such userspace can verify that it has
2013 * allows auth frames in a mesh to be passed to userspace for processing via
2016 * &enum nl80211_plink_state. Used when userspace is driving the peer link
2037 * fully complying with the match sets and userspace needs to be
2040 * this is only an optimization and the userspace application
2170 * userspace. If unset it is assumed the hint comes directly from
2215 * @NL80211_ATTR_RADAR_EVENT: Type of radar event for notification to userspace,
2234 * @NL80211_ATTR_SPLIT_WIPHY_DUMP: flag attribute, userspace supports
2279 * channels and reports radar events to userspace. Userspace is required
2515 * This will give an opportunity to userspace to consider connecting to
2702 * &enum nl80211_fils_discovery_attributes. Userspace should pass an empty
2707 * &enum nl80211_unsol_bcast_probe_resp_attributes. Userspace should pass an empty
2743 * and enhanced multi-BSSID advertisements (EMA AP) to the userspace.
2744 * Userspace should use this attribute to configure per interface MBSSID
2781 * attribute is not present userspace shall consider maximum number of AKM
2818 * Userspace is responsible for splitting the RNR into multiple
2823 * index. If the userspace includes more RNR elements than number of
4313 * structure passed by userspace (CRDA) from our wireless-regdb.
4503 /* For backport compatibility with older userspace */
4851 * a userspace daemon. When this flag is set, the kernel will send peer
4852 * management frames to a userspace daemon that will implement AMPE
4856 * userspace daemon.
4862 * @NL80211_MESH_SETUP_USERSPACE_MPM: Enable this option if userspace will
5328 * @NUM_NL80211_BANDS: number of bands, avoid using this in userspace
5557 * by the kernel to userspace.
5808 * capability information given by the kernel to userspace.
6117 * @NL80211_FEATURE_NEED_OBSS_SCAN: The driver expects userspace to perform
6137 * @NL80211_FEATURE_USERSPACE_MPM: This driver supports a userspace Mesh
6311 * able to rekey an in-use key correctly. Userspace must not rekey PTK keys
6400 * frames. Userspace has to share FILS AAD details to the driver by using
6612 * added by userspace explicitly.)
6685 * Type of event to be used with NL80211_ATTR_RADAR_EVENT to inform userspace
6770 * advertises the SME functionality but would like the userspace
7696 * attribute is not present from userspace.
7761 * 0 means userspace doesn't have SAR limitation on this associated range.
7767 * Userspace isn't required to set all the ranges advertised by WLAN driver,
7768 * and userspace can skip some certain ranges. These skipped ranges don't
7805 * Remaining attributes should be used by the userspace to configure the
7817 * if EMA is enabled. Driver should indicate EMA support to the userspace
7824 * all non-transmitting interfaces. The userspace will be responsible
7861 * @NL80211_AP_SETTINGS_SA_QUERY_OFFLOAD_SUPPORT: Userspace supports SA Query
7863 * %NL80211_AP_SME_SA_QUERY_OFFLOAD in AP SME features, userspace shall
7865 * userspace.