mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-25 14:13:01 -04:00
Merge "cfg80211: export regulatory_hint_user() API"
This commit is contained in:
commit
9936d8bd66
3 changed files with 27 additions and 3 deletions
|
|
@ -5729,6 +5729,32 @@ int regulatory_set_wiphy_regd(struct wiphy *wiphy,
|
|||
int regulatory_set_wiphy_regd_sync_rtnl(struct wiphy *wiphy,
|
||||
struct ieee80211_regdomain *rd);
|
||||
|
||||
/**
|
||||
* regulatory_hint_user - hint to the wireless core a regulatory domain
|
||||
* which the driver has received from an application
|
||||
* @alpha2: the ISO/IEC 3166 alpha2 the driver claims its regulatory domain
|
||||
* should be in. If @rd is set this should be NULL. Note that if you
|
||||
* set this to NULL you should still set rd->alpha2 to some accepted
|
||||
* alpha2.
|
||||
* @user_reg_hint_type: the type of user regulatory hint.
|
||||
*
|
||||
* Wireless drivers can use this function to hint to the wireless core
|
||||
* the current regulatory domain as specified by trusted applications,
|
||||
* it is the driver's responsibilty to estbalish which applications it
|
||||
* trusts.
|
||||
*
|
||||
* The wiphy should be registered to cfg80211 prior to this call.
|
||||
* For cfg80211 drivers this means you must first use wiphy_register(),
|
||||
* for mac80211 drivers you must first use ieee80211_register_hw().
|
||||
*
|
||||
* Drivers should check the return value, its possible you can get
|
||||
* an -ENOMEM or an -EINVAL.
|
||||
*
|
||||
* Return: 0 on success. -ENOMEM, -EINVAL.
|
||||
*/
|
||||
int regulatory_hint_user(const char *alpha2,
|
||||
enum nl80211_user_reg_hint_type user_reg_hint_type);
|
||||
|
||||
/**
|
||||
* wiphy_apply_custom_regulatory - apply a custom driver regulatory domain
|
||||
* @wiphy: the wireless device we want to process the regulatory domain on
|
||||
|
|
|
|||
Loading…
Reference in a new issue