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