786e414afd914805c7a90f16ee738106903ab9c9
[deliverable/linux.git] / net / wireless / reg.h
1 #ifndef __NET_WIRELESS_REG_H
2 #define __NET_WIRELESS_REG_H
3
4 extern const struct ieee80211_regdomain *cfg80211_regdomain;
5
6 bool is_world_regdom(const char *alpha2);
7 bool reg_is_valid_request(const char *alpha2);
8 bool reg_supported_dfs_region(u8 dfs_region);
9
10 int regulatory_hint_user(const char *alpha2);
11
12 int reg_device_uevent(struct device *dev, struct kobj_uevent_env *env);
13 void reg_device_remove(struct wiphy *wiphy);
14
15 int __init regulatory_init(void);
16 void regulatory_exit(void);
17
18 int set_regdom(const struct ieee80211_regdomain *rd);
19
20 void regulatory_update(struct wiphy *wiphy, enum nl80211_reg_initiator setby);
21
22 /**
23 * regulatory_hint_found_beacon - hints a beacon was found on a channel
24 * @wiphy: the wireless device where the beacon was found on
25 * @beacon_chan: the channel on which the beacon was found on
26 * @gfp: context flags
27 *
28 * This informs the wireless core that a beacon from an AP was found on
29 * the channel provided. This allows the wireless core to make educated
30 * guesses on regulatory to help with world roaming. This is only used for
31 * world roaming -- when we do not know our current location. This is
32 * only useful on channels 12, 13 and 14 on the 2 GHz band as channels
33 * 1-11 are already enabled by the world regulatory domain; and on
34 * non-radar 5 GHz channels.
35 *
36 * Drivers do not need to call this, cfg80211 will do it for after a scan
37 * on a newly found BSS. If you cannot make use of this feature you can
38 * set the wiphy->disable_beacon_hints to true.
39 */
40 int regulatory_hint_found_beacon(struct wiphy *wiphy,
41 struct ieee80211_channel *beacon_chan,
42 gfp_t gfp);
43
44 /**
45 * regulatory_hint_11d - hints a country IE as a regulatory domain
46 * @wiphy: the wireless device giving the hint (used only for reporting
47 * conflicts)
48 * @band: the band on which the country IE was received on. This determines
49 * the band we'll process the country IE channel triplets for.
50 * @country_ie: pointer to the country IE
51 * @country_ie_len: length of the country IE
52 *
53 * We will intersect the rd with the what CRDA tells us should apply
54 * for the alpha2 this country IE belongs to, this prevents APs from
55 * sending us incorrect or outdated information against a country.
56 *
57 * The AP is expected to provide Country IE channel triplets for the
58 * band it is on. It is technically possible for APs to send channel
59 * country IE triplets even for channels outside of the band they are
60 * in but for that they would have to use the regulatory extension
61 * in combination with a triplet but this behaviour is currently
62 * not observed. For this reason if a triplet is seen with channel
63 * information for a band the BSS is not present in it will be ignored.
64 */
65 void regulatory_hint_11d(struct wiphy *wiphy,
66 enum ieee80211_band band,
67 u8 *country_ie,
68 u8 country_ie_len);
69
70 /**
71 * regulatory_hint_disconnect - informs all devices have been disconneted
72 *
73 * Regulotory rules can be enhanced further upon scanning and upon
74 * connection to an AP. These rules become stale if we disconnect
75 * and go to another country, whether or not we suspend and resume.
76 * If we suspend, go to another country and resume we'll automatically
77 * get disconnected shortly after resuming and things will be reset as well.
78 * This routine is a helper to restore regulatory settings to how they were
79 * prior to our first connect attempt. This includes ignoring country IE and
80 * beacon regulatory hints. The ieee80211_regdom module parameter will always
81 * be respected but if a user had set the regulatory domain that will take
82 * precedence.
83 *
84 * Must be called from process context.
85 */
86 void regulatory_hint_disconnect(void);
87
88 #endif /* __NET_WIRELESS_REG_H */
This page took 0.032844 seconds and 4 git commands to generate.