1. 05 8月, 2010 3 次提交
    • F
      ath9k_hw: fix a noise floor calibration related race condition · 4254bc1c
      Felix Fietkau 提交于
      On AR5008-AR9002, other forms of calibration must not be started while
      the noise floor calibration is running, as this can create invalid
      readings which were sometimes not even recoverable by any further
      calibration attempts.
      
      This patch also ensures that the result of noise floor measurements
      are processed faster and also allows the result of the initial
      calibration on reset to make it into the NF history buffer
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      4254bc1c
    • F
      ath9k_hw: clean up per-channel calibration data · 20bd2a09
      Felix Fietkau 提交于
      The noise floor history buffer is currently not kept per channel, which
      can lead to problems when changing channels from a clean channel to a
      noisy one. Also when switching from HT20 to HT40, the noise floor
      history buffer is full of measurements, but none of them contain data
      for the extension channel, which it needs quite a bit of time to recover
      from.
      
      This patch puts all the per-channel calibration data into a single data
      structure, and gives the the driver control over whether that is used
      per-channel or even not used for some channels.
      
      For ath9k_htc, I decided to keep this per-channel in order to avoid
      creating regressions.
      
      For ath9k, the data is kept only for the operating channel, which saves
      some space. ath9k_hw takes care of wiping old data when the operating
      channel or its channel flags change.
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      20bd2a09
    • F
      ath9k_hw: clean up and fix initial noise floor calibration · 00c86590
      Felix Fietkau 提交于
      On AR9003 the initial noise floor calibration is currently triggered
      at the end of the reset without allowing the hardware to update the
      baseband settings. This could potentially make scans in noisy
      environments a bit more unreliable, so use the same calibration
      sequence that is used on AR9002.
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Acked-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      00c86590
  2. 13 7月, 2010 1 次提交
    • F
      ath9k: merge noisefloor load implementations · bbacee13
      Felix Fietkau 提交于
      AR5008+ and AR9003 currently use two separate implementations of the
      ath9k_hw_loadnf function. There are three main differences:
      
       - PHY registers for AR9003 are different
       - AR9003 always uses 3 chains, earlier versions are more selective
       - The AR9003 variant contains a fix for NF load timeouts
      
      This patch merges the two implementations into one, storing the
      register array in the ath_hw struct. The fix for NF load timeouts is
      not just relevant for AR9003, but also important for earlier hardware,
      so it's better to just keep one common implementation.
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      bbacee13
  3. 03 7月, 2010 1 次提交
  4. 17 4月, 2010 3 次提交
  5. 08 10月, 2009 1 次提交
  6. 23 9月, 2009 1 次提交
  7. 29 8月, 2009 1 次提交
  8. 25 7月, 2009 1 次提交
    • S
      ath9k: Manipulate and report the correct RSSI · a59b5a5e
      Senthil Balasubramanian 提交于
      RSSI reported by the RX descriptor requires little manipulation.
      Manipulate and report the correct RSSI to the stack. This will
      fix the improper signal levels reported by iwconfig iw dev wlanX
      station dump. Also the Link Quality reported seems to be varying
      (falls to zero also sometimes) when iperf is run from STA to AP.
      
      Also use the default noise floor for now as the one reported
      during the caliberation seems to be wrong.
      
      The Signal and Link Quality before this patch (taken while TX is
      in progress from STA to AP)
      
      09:59:13.285428037 Link Quality=29/70  Signal level=-81 dBm
      09:59:13.410660084 Link Quality=20/70  Signal level=-90 dBm
      09:59:13.586864392 Link Quality=21/70  Signal level=-89 dBm
      09:59:13.710296281 Link Quality=21/70  Signal level=-89 dBm
      09:59:13.821683064 Link Quality=25/70  Signal level=-85 dBm
      09:59:13.933402989 Link Quality=24/70  Signal level=-86 dBm
      09:59:14.045839276 Link Quality=26/70  Signal level=-84 dBm
      09:59:14.193926673 Link Quality=23/70  Signal level=-87 dBm
      09:59:14.306230262 Link Quality=31/70  Signal level=-79 dBm
      09:59:14.419459667 Link Quality=26/70  Signal level=-84 dBm
      09:59:14.530711167 Link Quality=37/70  Signal level=-73 dBm
      09:59:14.642593962 Link Quality=29/70  Signal level=-81 dBm
      09:59:14.754361169 Link Quality=21/70  Signal level=-89 dBm
      09:59:14.866217355 Link Quality=21/70  Signal level=-89 dBm
      09:59:14.976963623 Link Quality=28/70  Signal level=-82 dBm
      09:59:15.089149809 Link Quality=26/70  Signal level=-84 dBm
      09:59:15.205039887 Link Quality=27/70  Signal level=-83 dBm
      09:59:15.316368003 Link Quality=23/70  Signal level=-87 dBm
      09:59:15.427684036 Link Quality=36/70  Signal level=-74 dBm
      09:59:15.539756380 Link Quality=21/70  Signal level=-89 dBm
      09:59:15.650549093 Link Quality=22/70  Signal level=-88 dBm
      09:59:15.761171672 Link Quality=32/70  Signal level=-78 dBm
      09:59:15.872793750 Link Quality=23/70  Signal level=-87 dBm
      09:59:15.984421694 Link Quality=22/70  Signal level=-88 dBm
      09:59:16.097315093 Link Quality=21/70  Signal level=-89 dBm
      
      The link quality and signal level after this patch (take while
      TX is in progress from STA to AP)
      
      17:21:25.627848091 Link Quality=65/70  Signal level=-45 dBm
      17:21:25.762805607 Link Quality=65/70  Signal level=-45 dBm
      17:21:25.875521888 Link Quality=66/70  Signal level=-44 dBm
      17:21:25.987468448 Link Quality=66/70  Signal level=-44 dBm
      17:21:26.100628151 Link Quality=66/70  Signal level=-44 dBm
      17:21:26.213129671 Link Quality=66/70  Signal level=-44 dBm
      17:21:26.324923070 Link Quality=65/70  Signal level=-45 dBm
      17:21:26.436831357 Link Quality=65/70  Signal level=-45 dBm
      17:21:26.610356973 Link Quality=65/70  Signal level=-45 dBm
      17:21:26.723340047 Link Quality=65/70  Signal level=-45 dBm
      17:21:26.835715293 Link Quality=64/70  Signal level=-46 dBm
      17:21:26.949542748 Link Quality=64/70  Signal level=-46 dBm
      17:21:27.062261613 Link Quality=65/70  Signal level=-45 dBm
      17:21:27.174511563 Link Quality=64/70  Signal level=-46 dBm
      17:21:27.287616232 Link Quality=64/70  Signal level=-46 dBm
      17:21:27.400598119 Link Quality=64/70  Signal level=-46 dBm
      17:21:27.511381404 Link Quality=64/70  Signal level=-46 dBm
      17:21:27.624530421 Link Quality=65/70  Signal level=-45 dBm
      17:21:27.737807109 Link Quality=64/70  Signal level=-46 dBm
      17:21:27.850861352 Link Quality=65/70  Signal level=-45 dBm
      17:21:27.963369436 Link Quality=64/70  Signal level=-46 dBm
      17:21:28.076582289 Link Quality=64/70  Signal level=-46 dBm
      Signed-off-by: NSenthil Balasubramanian <senthilkumar@atheros.com>
      Signed-off-by: NVasanthakumar Thiagarajan <vasanth@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      a59b5a5e
  9. 23 4月, 2009 3 次提交
  10. 28 3月, 2009 1 次提交
  11. 28 2月, 2009 1 次提交
  12. 14 2月, 2009 3 次提交