1. 03 Jun, 2013 1 commit
  2. 30 May, 2013 1 commit
  3. 22 May, 2013 1 commit
  4. 23 Apr, 2013 1 commit
  5. 22 Apr, 2013 1 commit
  6. 08 Apr, 2013 2 commits
  7. 01 Feb, 2013 1 commit
  8. 30 Jan, 2013 1 commit
  9. 14 Jan, 2013 1 commit
  10. 09 Jan, 2013 1 commit
    • Simon Wunderlich's avatar
      ath9k: add spectral scan feature · e93d083f
      Simon Wunderlich authored
      
      
      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: default avatarSimon Wunderlich <siwu@hrz.tu-chemnitz.de>
      Signed-off-by: default avatarMathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      e93d083f
  11. 07 Jan, 2013 2 commits
  12. 11 Dec, 2012 1 commit
  13. 10 Dec, 2012 1 commit
  14. 21 Nov, 2012 2 commits
  15. 29 Oct, 2012 1 commit
  16. 24 Sep, 2012 2 commits
  17. 11 Sep, 2012 1 commit
  18. 17 Jul, 2012 2 commits
  19. 12 Jul, 2012 1 commit
  20. 06 Jun, 2012 2 commits
  21. 23 Apr, 2012 1 commit
  22. 11 Apr, 2012 1 commit
  23. 10 Apr, 2012 2 commits
  24. 09 Apr, 2012 1 commit
    • Rajkumar Manoharan's avatar
      ath9k: recover ar9380 chips from rare stuck state · 01e18918
      Rajkumar Manoharan authored
      
      
      In the experiment with Azimuth ADEPT-n testbed where the APs transmit
      power was reduced to 25% and the signal strength was futher attenuated
      by 20dB and induced a path loss of ~7dB, the station was reporting
      beacon losses and the following issue were observed.
      
      * rx clear is stuck at low for more than 300ms
      * dcu chain and complete state is stuck at one of the hang signature
      
      This patch triggers the hang detection logic that recovers the chip
      from any of the above conditions. As the issue was originally reported
      in ChromeOs with AR9382 chips, this detection logic is enabled only for
      AR9380/2 chips.
      
      Cc: Paul Stewart <pstew@google.com>
      Reported-by: default avatarGary Morain <gmorain@google.com>
      Signed-off-by: default avatarRajkumar Manoharan <rmanohar@qca.qualcomm.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      01e18918
  25. 26 Mar, 2012 1 commit
  26. 15 Mar, 2012 3 commits
  27. 07 Mar, 2012 1 commit
  28. 27 Feb, 2012 2 commits
  29. 03 Feb, 2012 1 commit
    • Mohammed Shafi Shajakhan's avatar
      ath9k: Fix kernel panic during driver initilization · 07445f68
      Mohammed Shafi Shajakhan authored
      
      
      all works need to be initialized before ieee80211_register_hw
      to prevent mac80211 call backs such as drv_start, drv_config
      getting started. otherwise we would queue/cancel works before
      initializing them and it leads to kernel panic.
      this issue can be recreated with the following script
      in Chrome laptops with AR928X cards, with background scan
      running (or) Network manager is running
      
      while true
      do
      sudo modprobe -v ath9k
      sleep 3
      sudo modprobe -r ath9k
      sleep 3
      done
      
      	 EIP: [<81040a47>] __cancel_work_timer+0xb8/0xe1 SS:ESP 0068:f6be9d70
      	 ---[ end trace 4f86d6139a9900ef ]---
      	 Registered led device: ath9k-phy0
      	 ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xf88a0000,
      	 irq=16
      	 Kernel panic - not syncing: Fatal exception
      	 Pid: 456, comm: wpa_supplicant Tainted: G      D
      	 3.0.13 #1
      	Call Trace:
      	 [<81379e21>] panic+0x53/0x14a
      	 [<81004a30>] oops_end+0x73/0x81
      	 [<81004b53>] die+0x4c/0x55
      	 [<81002710>] do_trap+0x7c/0x83
      	 [<81002855>] ? do_bounds+0x58/0x58
      	 [<810028cc>] do_invalid_op+0x77/0x81
      	 [<81040a47>] ? __cancel_work_timer+0xb8/0xe1
      	 [<810489ec>] ? sched_clock_cpu+0x81/0x11f
      	 [<8103f809>] ? wait_on_work+0xe2/0xf7
      	 [<8137f807>] error_code+0x67/0x6c
      	 [<810300d8>] ? wait_consider_task+0x4ba/0x84c
      	 [<81040a47>] ? __cancel_work_timer+0xb8/0xe1
      	 [<810380c9>] ? try_to_del_timer_sync+0x5f/0x67
      	 [<81040a91>] cancel_work_sync+0xf/0x11
      	 [<f88d7b7c>] ath_set_channel+0x62/0x25c [ath9k]
      	 [<f88d67d1>] ? ath9k_tx_last_beacon+0x26a/0x85c [ath9k]
      	 [<f88d8899>] ath_radio_disable+0x3f1/0x68e [ath9k]
      	 [<f90d0edb>] ieee80211_hw_config+0x111/0x116 [mac80211]
      	 [<f90dd95c>] __ieee80211_recalc_idle+0x919/0xa37 [mac80211]
      	 [<f90dda76>] __ieee80211_recalc_idle+0xa33/0xa37 [mac80211]
      	 [<812dbed8>] __dev_open+0x82/0xab
      
      Cc: <stable@vger.kernel.org>
      Cc: Gary Morain <gmorain@google.com>
      Cc: Paul Stewart <pstew@google.com>
      Cc: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
      Tested-by: default avatarMohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
      Signed-off-by: default avatarRajkumar Manoharan <rmanohar@qca.qualcomm.com>
      Signed-off-by: default avatarMohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      07445f68
  30. 19 Dec, 2011 1 commit
    • Felix Fietkau's avatar
      ath9k_hw: make bluetooth coexistence support optional at compile time · 8a309305
      Felix Fietkau authored
      
      
      Many systems (e.g. embedded systems) do not have wifi modules connected to
      bluetooth modules, so bluetooth coexistence is irrelevant there. With the
      addition of MCI support, ath9k picked up quite a bit of extra code that
      can be compiled out this way.
      
      This patch redefines ATH9K_HW_CAP_MCI and adds an inline wrapper for
      querying the bluetooth coexistence scheme, allowing the compiler to
      eliminate code that uses it, with only very little use of #ifdef.
      
      On MIPS this reduces the total size for the modules by about 20k.
      Signed-off-by: default avatarFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      8a309305