summaryrefslogtreecommitdiffstats
path: root/drivers/net/wireless/iwlwifi/mvm/fw-api-mac.h
diff options
context:
space:
mode:
authorAriej Marjieh <ariej.marjieh@intel.com>2014-07-16 21:11:12 +0300
committerEmmanuel Grumbach <emmanuel.grumbach@intel.com>2014-07-22 19:20:59 +0300
commitb112889c5af8124e2b6d884d00859fc172c6748a (patch)
treeb6f340ee3261ef04f86fd58e5dc4440c1399be8b /drivers/net/wireless/iwlwifi/mvm/fw-api-mac.h
parent720befbf2ecce8e5851a816fa567584320d721ec (diff)
downloadop-kernel-dev-b112889c5af8124e2b6d884d00859fc172c6748a.zip
op-kernel-dev-b112889c5af8124e2b6d884d00859fc172c6748a.tar.gz
iwlwifi: mvm: add Aux ROC request/response flow
The Remain On Channel framework added to the firmare is a bit like time events. It allows the driver to request the firmware to be on a certain channel for a certain time. Unlike the time events, the ROC infrastructure doesn't need a MAC context in the firmware - it uses a generic context called "auxiliary framework". This is useful for any offchannel activity that is not bound to a specific MAC. The flow is synchronized much like with time events: 1) The driver receives an action frame from the wpa_supplicant via nl80211 that requests to be sent offchannel. 2) The driver sends an Aux ROC command (0x53) to the firmware. 3) The firmware responds with the unique id of the time event. 4) When time event starts, the driver puts the frame in the Aux queue. Special care needs to be taken when the time events ends: the queue needs to be cleaned-up. Signed-off-by: Ariej Marjieh <ariej.marjieh@intel.com> Reviewed-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Diffstat (limited to 'drivers/net/wireless/iwlwifi/mvm/fw-api-mac.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud