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