blob: 519492fdda3c9421e0c2ead848590233be2d8d5e [file] [log] [blame]
Luis R. Rodriguezb2e1b302008-09-09 23:19:48 -07001#ifndef __NET_WIRELESS_REG_H
2#define __NET_WIRELESS_REG_H
Luis R. Rodriguez3b77d5e2011-12-20 12:23:38 -08003/*
4 * Copyright 2008-2011 Luis R. Rodriguez <mcgrof@qca.qualcomm.com>
5 *
6 * Permission to use, copy, modify, and/or distribute this software for any
7 * purpose with or without fee is hereby granted, provided that the above
8 * copyright notice and this permission notice appear in all copies.
9 *
10 * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
11 * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
12 * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
13 * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
14 * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
15 * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
16 * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
17 */
Luis R. Rodriguezb2e1b302008-09-09 23:19:48 -070018
Luis R. Rodriguezf1303472009-01-30 09:26:42 -080019extern const struct ieee80211_regdomain *cfg80211_regdomain;
20
Johannes Berga3d2eaf2008-09-15 11:10:52 +020021bool is_world_regdom(const char *alpha2);
22bool reg_is_valid_request(const char *alpha2);
Luis R. Rodriguez8b60b072011-10-11 10:59:02 -070023bool reg_supported_dfs_region(u8 dfs_region);
Luis R. Rodriguezb2e1b302008-09-09 23:19:48 -070024
Luis R. Rodriguez57b5ce02012-07-12 11:49:18 -070025int regulatory_hint_user(const char *alpha2,
26 enum nl80211_user_reg_hint_type user_reg_hint_type);
Luis R. Rodriguezfe33eb32009-02-21 00:04:30 -050027
Scott James Remnant4d9d88d2011-03-08 10:45:30 -080028int reg_device_uevent(struct device *dev, struct kobj_uevent_env *env);
Luis R. Rodriguez57b5ce02012-07-12 11:49:18 -070029void wiphy_regulatory_register(struct wiphy *wiphy);
Luis R. Rodriguez3f2355c2008-11-12 14:22:02 -080030void reg_device_remove(struct wiphy *wiphy);
31
Uwe Kleine-König2fcc9f72010-06-18 09:38:55 +020032int __init regulatory_init(void);
Luis R. Rodriguezb2e1b302008-09-09 23:19:48 -070033void regulatory_exit(void);
34
Johannes Berga3d2eaf2008-09-15 11:10:52 +020035int set_regdom(const struct ieee80211_regdomain *rd);
Luis R. Rodriguezb2e1b302008-09-09 23:19:48 -070036
Sven Neumanneac03e32011-08-30 23:38:53 +020037void regulatory_update(struct wiphy *wiphy, enum nl80211_reg_initiator setby);
Luis R. Rodriguez57b5ce02012-07-12 11:49:18 -070038bool reg_last_request_cell_base(void);
Sven Neumanneac03e32011-08-30 23:38:53 +020039
Johannes Bergcf032682008-10-21 09:42:38 +020040/**
Luis R. Rodrigueze38f8a72009-02-21 00:20:39 -050041 * regulatory_hint_found_beacon - hints a beacon was found on a channel
42 * @wiphy: the wireless device where the beacon was found on
43 * @beacon_chan: the channel on which the beacon was found on
44 * @gfp: context flags
45 *
46 * This informs the wireless core that a beacon from an AP was found on
47 * the channel provided. This allows the wireless core to make educated
48 * guesses on regulatory to help with world roaming. This is only used for
49 * world roaming -- when we do not know our current location. This is
50 * only useful on channels 12, 13 and 14 on the 2 GHz band as channels
51 * 1-11 are already enabled by the world regulatory domain; and on
52 * non-radar 5 GHz channels.
53 *
54 * Drivers do not need to call this, cfg80211 will do it for after a scan
Luis R. Rodriguez37184242009-07-30 17:43:48 -070055 * on a newly found BSS. If you cannot make use of this feature you can
56 * set the wiphy->disable_beacon_hints to true.
Luis R. Rodrigueze38f8a72009-02-21 00:20:39 -050057 */
58int regulatory_hint_found_beacon(struct wiphy *wiphy,
59 struct ieee80211_channel *beacon_chan,
60 gfp_t gfp);
61
Luis R. Rodriguez8b19e6c2009-07-30 17:38:09 -070062/**
63 * regulatory_hint_11d - hints a country IE as a regulatory domain
64 * @wiphy: the wireless device giving the hint (used only for reporting
65 * conflicts)
Luis R. Rodriguez84920e32010-01-14 20:08:20 -050066 * @band: the band on which the country IE was received on. This determines
67 * the band we'll process the country IE channel triplets for.
Luis R. Rodriguez8b19e6c2009-07-30 17:38:09 -070068 * @country_ie: pointer to the country IE
69 * @country_ie_len: length of the country IE
70 *
71 * We will intersect the rd with the what CRDA tells us should apply
72 * for the alpha2 this country IE belongs to, this prevents APs from
73 * sending us incorrect or outdated information against a country.
Luis R. Rodriguez84920e32010-01-14 20:08:20 -050074 *
75 * The AP is expected to provide Country IE channel triplets for the
76 * band it is on. It is technically possible for APs to send channel
77 * country IE triplets even for channels outside of the band they are
78 * in but for that they would have to use the regulatory extension
79 * in combination with a triplet but this behaviour is currently
80 * not observed. For this reason if a triplet is seen with channel
81 * information for a band the BSS is not present in it will be ignored.
Luis R. Rodriguez8b19e6c2009-07-30 17:38:09 -070082 */
83void regulatory_hint_11d(struct wiphy *wiphy,
Luis R. Rodriguez84920e32010-01-14 20:08:20 -050084 enum ieee80211_band band,
Luis R. Rodriguez8b19e6c2009-07-30 17:38:09 -070085 u8 *country_ie,
86 u8 country_ie_len);
87
Luis R. Rodriguez09d989d2010-01-29 19:58:57 -050088/**
89 * regulatory_hint_disconnect - informs all devices have been disconneted
90 *
91 * Regulotory rules can be enhanced further upon scanning and upon
92 * connection to an AP. These rules become stale if we disconnect
93 * and go to another country, whether or not we suspend and resume.
94 * If we suspend, go to another country and resume we'll automatically
95 * get disconnected shortly after resuming and things will be reset as well.
96 * This routine is a helper to restore regulatory settings to how they were
97 * prior to our first connect attempt. This includes ignoring country IE and
98 * beacon regulatory hints. The ieee80211_regdom module parameter will always
99 * be respected but if a user had set the regulatory domain that will take
100 * precedence.
101 *
102 * Must be called from process context.
103 */
104void regulatory_hint_disconnect(void);
105
Luis R. Rodriguezb2e1b302008-09-09 23:19:48 -0700106#endif /* __NET_WIRELESS_REG_H */