1. 06 May, 2014 1 commit
    • Michal Kazior's avatar
      mac80211: fix CSA tx queue stopping · 59af6928
      Michal Kazior authored
      It was possible for tx queues to be stuck stopped
      if AP CSA finalization failed. In that case
      neither stop_ap nor do_stop woke the queues up.
      This means it was impossible to perform tx at all
      until driver was reloaded or a successful CSA was
      performed later.
      
      It was possible to solve this in a simpler manner
      however this is more robust and future proof
      (having multi-vif CSA in mind).
      
      New sdata->csa_block_tx is introduced to keep
      track of which interfaces requested tx to be
      blocked for CSA. This is required because mac80211
      stops all tx queues for that purpose. This means
      queues must be awoken only when last tx-blocking
      CSA interface is finished.
      
      It is still possible to have tx queues stopped
      after CSA failure but as soon as offending
      interfaces are stopped from userspace (stop_ap or
      ifdown) tx queues are woken up properly.
      Signed-off-by: default avatarMichal Kazior <michal.kazior@tieto.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      59af6928
  2. 05 May, 2014 3 commits
  3. 29 Apr, 2014 2 commits
  4. 28 Apr, 2014 5 commits
  5. 25 Apr, 2014 22 commits
  6. 22 Apr, 2014 6 commits
  7. 11 Apr, 2014 1 commit