summaryrefslogtreecommitdiffstats
path: root/Documentation/kmemleak.txt
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2015-03-01 09:10:13 +0200
committerJohannes Berg <johannes.berg@intel.com>2015-03-04 10:34:11 +0100
commit98fc43864af9e74116eec81c290db048cded15d8 (patch)
treeed8b1e929f1cf0d5eb3eb0e2a2e1150faed72424 /Documentation/kmemleak.txt
parent88724a81b4ac2a755bf9c532cdbee08a52803852 (diff)
downloadlinux-98fc43864af9e74116eec81c290db048cded15d8.tar.gz
linux-98fc43864af9e74116eec81c290db048cded15d8.tar.bz2
linux-98fc43864af9e74116eec81c290db048cded15d8.zip
nl80211: prohibit mixing 'any' and regular wowlan triggers
If the device supports waking up on 'any' signal - i.e. it continues operating as usual and wakes up the host on pretty much anything that happens, then it makes no sense to also configure the more restricted WoWLAN mode where the device operates more autonomously but also in a more restricted fashion. Currently only cw2100 supports both 'any' and other triggers, but it seems to be broken as it doesn't configure anything to the device, so we can't currently get into a situation where both even can correctly be configured. This is about to change (Intel devices are going to support both and have different behaviour depending on configuration) so make sure the conflicting modes cannot be configured. (It seems that cw2100 advertises 'any' and 'disconnect' as a means of saying that's what it will always do, but that isn't really the way this API was meant to be used nor does it actually mean anything as 'any' always implies 'disconnect' already, and the driver doesn't change device configuration in any way depending on the settings.) Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'Documentation/kmemleak.txt')
0 files changed, 0 insertions, 0 deletions