1. 06 8月, 2013 1 次提交
  2. 16 7月, 2013 1 次提交
  3. 13 6月, 2013 2 次提交
    • S
      ath9k: Fix noisefloor calibration · 696df785
      Sujith Manoharan 提交于
      The commits,
      
      "ath9k: Fix regression in channelwidth switch at the same channel"
      "ath9k: Fix invalid noisefloor reading due to channel update"
      
      attempted to fix noisefloor calibration when a channel switch
      happens due to HT20/HT40 bandwidth change. This is causing invalid
      readings resulting in messages like:
      
      "ath: phy16: NF[0] (-45) > MAX (-95), correcting to MAX".
      
      This results in an incorrect noise being used initially for reporting
      the signal level of received packets, until NF calibration is done
      and the history buffer is updated via the ANI timer, which happens
      much later.
      
      When a bandwidth change happens, it is appropriate to reset
      the internal history data for the channel. Do this correctly in the
      reset() routine by checking the "chanmode" variable.
      
      Cc: stable@vger.kernel.org
      Cc: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
      Signed-off-by: NSujith Manoharan <c_manoha@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      696df785
    • F
      ath9k: implement support for .release_buffered_frames() · 86a22acf
      Felix Fietkau 提交于
      This adds support for PS-Poll and U-APSD driver-buffered frames (part of
      an aggregation session).
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      86a22acf
  4. 04 6月, 2013 1 次提交
  5. 23 5月, 2013 4 次提交
  6. 18 5月, 2013 1 次提交
  7. 09 5月, 2013 1 次提交
  8. 04 5月, 2013 1 次提交
  9. 23 4月, 2013 1 次提交
  10. 09 4月, 2013 1 次提交
  11. 04 4月, 2013 1 次提交
  12. 26 3月, 2013 1 次提交
  13. 19 3月, 2013 1 次提交
  14. 12 2月, 2013 1 次提交
  15. 31 1月, 2013 1 次提交
  16. 23 1月, 2013 3 次提交
  17. 15 1月, 2013 1 次提交
  18. 12 1月, 2013 2 次提交
  19. 10 1月, 2013 1 次提交
    • S
      ath9k: add spectral scan feature · e93d083f
      Simon Wunderlich 提交于
      Adds the spectral scan feature for ath9k. AR92xx and AR93xx chips
      are supported for now. The spectral scan is triggered by configuring
      a mode through a debugfs control file. Samples can be gathered via
      another relay debugfs file.
      
      Essentially, to try it out:
      
      echo chanscan > /sys/kernel/debug/ieee80211/phy0/ath9k/spectral_scan_ctl
      iw dev wlan0 scan
      cat /sys/kernel/debug/ieee80211/phy0/ath9k/spectral_scan0 > samples
      echo disable > /sys/kernel/debug/ieee80211/phy0/ath9k/spectral_scan_ctl
      
      This feature is still experimental.
      
      The special "chanscan" mode is used to perform spectral scan while
      mac80211 is scanning for channels. To allow this,
      sw_scan_start/complete() ops have been added.
      
      The patch contains code snippets and information from Zefir Kurtisi and
      information provided by Adrian Chadd and Felix Fietkau.
      Signed-off-by: NSimon Wunderlich <siwu@hrz.tu-chemnitz.de>
      Signed-off-by: NMathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      e93d083f
  20. 03 1月, 2013 1 次提交
    • J
      mac80211: split TX aggregation stop action · 18b559d5
      Johannes Berg 提交于
      When TX aggregation is stopped, there are a few
      different cases:
       - connection with the peer was dropped
       - session stop was requested locally
       - session stop was requested by the peer
       - connection was dropped while a session is stopping
      
      The behaviour in these cases should be different, if
      the connection is dropped then the driver should drop
      all frames, otherwise the frames may continue to be
      transmitted, aggregated in the case of a locally
      requested session stop or unaggregated in the case of
      the peer requesting session stop.
      
      Split these different cases so that the driver can
      act accordingly; however, treat local and remote stop
      the same way and ask the driver to not send frames as
      aggregated packets any more.
      
      In the case of connection drop, the stop callback the
      driver is otherwise supposed to call is no longer
      required.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      18b559d5
  21. 01 12月, 2012 2 次提交
  22. 22 11月, 2012 4 次提交
  23. 17 11月, 2012 1 次提交
  24. 10 11月, 2012 1 次提交
    • J
      mac80211: clarify interface iteration and make it configurable · 8b2c9824
      Johannes Berg 提交于
      During hardware restart, all interfaces are iterated even
      though they haven't been re-added to the driver, document
      this behaviour. The same also happens during resume, which
      is even more confusing since all of the interfaces were
      previously removed from the driver. Make this optional so
      drivers relying on the current behaviour can still use it,
      but to let drivers that don't want this behaviour disable
      it.
      
      Also convert all API users, keeping the old semantics
      except in hwsim, where the new normal ones are desired.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8b2c9824
  25. 30 10月, 2012 2 次提交
  26. 20 10月, 2012 1 次提交
    • R
      ath9k: perform ANI cycle in idle state · 424749c7
      Rajkumar Manoharan 提交于
      As of now the ANI cycle is executed only when the chip is awake.
      On idle state case, the station wakes up from network sleep for
      beacon reception. Since most of the time, ANI cycle is not syncing
      with beacon wakeup, ANI cycle is ignored. Approx 5 mins once, the
      calibration is performed. This could affect the connection stability
      when the station is idle for long. Even though the OFDM and CCK phy
      error rates are too high, ANI is unable to tune its immunity level
      as quick enough due to rare execution.
      
      Here the experiment shows that OFDM and CCK levels are at default
      even on higher phy error rate.
      
      listenTime=44 OFDM:3 errs=121977/s CCK:2 errs=440818/s ofdm_turn=1
      
      This change ensures that ANI calibration will be exectued atleast
      once for every 10 seconds. The below result shows improvements and
      immunity levels are adopted quick enough.
      
      listenTime=557 OFDM:4 errs=752/s CCK:4 errs=125/s ofdm_turn=0
      Signed-off-by: NRajkumar Manoharan <rmanohar@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      424749c7
  27. 06 10月, 2012 2 次提交