1REGULATORY_HINT(9)      Regulatory enforcement infrast      REGULATORY_HINT(9)
2
3
4

NAME

6       regulatory_hint - driver hint to the wireless core a regulatory domain
7

SYNOPSIS

9       int regulatory_hint(struct wiphy * wiphy, const char * alpha2);
10

ARGUMENTS

12       wiphy
13           the wireless device giving the hint (used only for reporting
14           conflicts)
15
16       alpha2
17           the ISO/IEC 3166 alpha2 the driver claims its regulatory domain
18           should be in. If rd is set this should be NULL. Note that if you
19           set this to NULL you should still set rd->alpha2 to some accepted
20           alpha2.
21

DESCRIPTION

23       Wireless drivers can use this function to hint to the wireless core
24       what it believes should be the current regulatory domain by giving it
25       an ISO/IEC 3166 alpha2 country code it knows its regulatory domain
26       should be in or by providing a completely build regulatory domain. If
27       the driver provides an ISO/IEC 3166 alpha2 userspace will be queried
28       for a regulatory domain structure for the respective country.
29
30       The wiphy must have been registered to cfg80211 prior to this call. For
31       cfg80211 drivers this means you must first use wiphy_register, for
32       mac80211 drivers you must first use ieee80211_register_hw.
33
34       Drivers should check the return value, its possible you can get an
35       -ENOMEM.
36

RETURN

38       0 on success. -ENOMEM.
39

AUTHOR

41       Johannes Berg <johannes@sipsolutions.net>
42           Author.
43

45Kernel Hackers Manual 3.10         June 2019                REGULATORY_HINT(9)
Impressum