1. 19 1月, 2015 1 次提交
    • E
      iwlwifi: mvm: abort scheduled scan upon RFKILL · 90ea15c1
      Emmanuel Grumbach 提交于
      When we have an active scheduled scan, and the RFKILL
      interrupt kicks in, the stack will cancel the scheduled
      scan as part of the down flow. But cancelling scheduled
      scan usually implies sending a command to the firwmare
      which has been killed as part of the RFKILL interrupt
      handling.
      Because of that, we returned an error to mac80211 when
      it asked to stop the scheduled scan and didn't notify the
      end of the scheduled scan. Besides a fat warning, this led
      to a situation in which cfg80211 would refuse any new scan
      request.
      
      To disentangle this, fake that the scheduled scan has been
      stopped without sending the command to the firwmare, return
      0 after having properly let cfg80211 know that the scan
      has been cancelled.
      
      This is basically the same as:
      commit 9b520d84
      Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
      Date:   Tue Nov 4 15:54:11 2014 +0200
      
          iwlwifi: mvm: abort scan upon RFKILL
      
          This code existed but not for all the different FW APIs
          we support.
          Fix this.
      
      but for the scheduled scan case.
      
      Link: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/133232Reported-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      90ea15c1
  2. 12 1月, 2015 1 次提交
  3. 05 1月, 2015 2 次提交
  4. 24 11月, 2014 6 次提交
  5. 11 11月, 2014 1 次提交
  6. 29 10月, 2014 3 次提交
  7. 24 10月, 2014 1 次提交
  8. 22 9月, 2014 1 次提交
  9. 16 9月, 2014 1 次提交
  10. 15 9月, 2014 1 次提交
  11. 04 9月, 2014 2 次提交
  12. 08 7月, 2014 3 次提交
  13. 25 6月, 2014 2 次提交
  14. 24 6月, 2014 3 次提交
  15. 13 5月, 2014 2 次提交
  16. 11 5月, 2014 1 次提交
  17. 14 4月, 2014 2 次提交
  18. 13 4月, 2014 1 次提交
  19. 19 3月, 2014 2 次提交
    • A
      iwlwifi: mvm: configure low latency dependent scan parameters · 50df8a30
      Alexander Bondar 提交于
      In case of system low latency configure passive scan to be fragmented.
      Set the following scan parameters for both immediate and scheduled scan:
       - passive scan fragment duration = 20ms
       - out-of-channel time = 70ms
       - suspend time = 105ms
      Restructure channel's active/passive dwell time configuration to better
      suit the above change.
      
      The idea is that under low latency traffic passive scan is fragmented,
      i.e. that dwell on a particular channel will be fragmented. Each
      fragment dwell time is 20ms and fragments period is 105ms. Skipping to
      next channel will be delayed by the same period (105ms). So suspend_time
      parameter describing both fragments and channels skipping periods is set
      to 105ms. This value is chosen so that overall passive scan duration
      will not be too long. Max_out_time in this case is set to 70ms, so for
      active scanning operating channel will be left for 70ms while for
      passive still for 20ms (fragment dwell).
      Signed-off-by: NAlexander Bondar <alexander.bondar@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      50df8a30
    • A
      iwlwifi: mvm: restructure scan parameters calculation · 8a110d9b
      Alexander Bondar 提交于
      Some scan parameters should be dependent on traffic conditions.
      Centralize conditions verification in one function and obtain
      scan max out-of-channel and suspend time in that new function.
      Rely on bound interfaces indication instead of association state
      to calculate scan parameters. If no bound interfaces use default
      values for out-of-channel and suspend time parameters.
      
      Additionally, get rid of NL80211_SCAN_FLAG_LOW_PRIORITY checks
      since no use case for this exists so far.
      Signed-off-by: NAlexander Bondar <alexander.bondar@intel.com>
      [reword commit log a bit]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      8a110d9b
  20. 10 3月, 2014 3 次提交
  21. 13 2月, 2014 1 次提交