summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2012-10-24 10:59:25 +0200
committerJohannes Berg <johannes.berg@intel.com>2012-10-30 09:11:34 +0100
commit1ea6f9c0d48b11b6ec3ec4b5579ec74fc3951cf8 (patch)
tree5a589d0bccfcac6ba0952942a04482b99752ddcc /drivers
parentc8442118ad9cd05cfe3b993f058e70ab25b1009a (diff)
downloadlinux-3.10-1ea6f9c0d48b11b6ec3ec4b5579ec74fc3951cf8.tar.gz
linux-3.10-1ea6f9c0d48b11b6ec3ec4b5579ec74fc3951cf8.tar.bz2
linux-3.10-1ea6f9c0d48b11b6ec3ec4b5579ec74fc3951cf8.zip
mac80211: handle TX power per virtual interface
Even before channel contexts/multi-channel, having a single global TX power limit was already problematic, in particular if two managed interfaces connected to two APs with different power constraints. The channel context introduction completely broke this though and in fact I had disabled TX power configuration there for drivers using channel contexts. Change everything to track TX power per interface so that different user settings and different channel maxima are treated correctly. Also continue tracking the global TX power though for compatibility with applications that attempt to configure the wiphy's TX power globally. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions