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