diff options
author | Jonathan Doron <jond@wizery.com> | 2014-12-15 19:26:00 +0200 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2014-12-17 11:49:55 +0100 |
commit | b0d7aa59592b4270531de5ce65dcf18338a2d98c (patch) | |
tree | 85d54dba5117fedd4d5b605be70ddbf8451d7838 /include/net/tc_act | |
parent | ad30ca2c03cecfb1b0749874bdceead269542de6 (diff) | |
download | linux-b0d7aa59592b4270531de5ce65dcf18338a2d98c.tar.gz linux-b0d7aa59592b4270531de5ce65dcf18338a2d98c.tar.bz2 linux-b0d7aa59592b4270531de5ce65dcf18338a2d98c.zip |
cfg80211: allow wiphy specific regdomain management
Add a new regulatory flag that allows a driver to manage regdomain
changes/updates for its own wiphy.
A self-managed wiphys only employs regulatory information obtained from
the FW and driver and does not use other cfg80211 sources like
beacon-hints, country-code IEs and hints from other devices on the same
system. Conversely, a self-managed wiphy does not share its regulatory
hints with other devices in the system. If a system contains several
devices, one or more of which are self-managed, there might be
contradictory regulatory settings between them. Usage of flag is
generally discouraged. Only use it if the FW/driver is incompatible
with non-locally originated hints.
A new API lets the driver send a complete regdomain, to be applied on
its wiphy only.
After a wiphy-specific regdomain change takes place, usermode will get
a new type of change notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron <jonathanx.doron@intel.com>
Signed-off-by: Arik Nemtsov <arikx.nemtsov@intel.com>
Reviewed-by: Luis R. Rodriguez <mcgrof@suse.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'include/net/tc_act')
0 files changed, 0 insertions, 0 deletions