summaryrefslogtreecommitdiffstats
path: root/drivers/net/mv643xx_eth.c
diff options
context:
space:
mode:
authorRajkumar Manoharan <rmanoharan@atheros.com>2011-05-04 19:37:17 +0530
committerJohn W. Linville <linville@tuxdriver.com>2011-05-05 14:59:20 -0400
commit28ef6450f0182f95c4f50aaa0ab2043a09c72b0a (patch)
tree0696797b7d38136c0dacc9544fbf354a9432a5be /drivers/net/mv643xx_eth.c
parenteecc48000afe2ca6da22122d553b7cad294e42fc (diff)
downloadblackbird-op-linux-28ef6450f0182f95c4f50aaa0ab2043a09c72b0a.tar.gz
blackbird-op-linux-28ef6450f0182f95c4f50aaa0ab2043a09c72b0a.zip
ath9k_hw: do noise floor calibration only on required chains
At present the noise floor calibration is processed in supported control and extension chains rather than required chains. Unnccesarily doing nfcal in all supported chains leads to invalid nf readings on extn chains and these invalid values got updated into history buffer. While loading those values from history buffer is moving the chip to deaf state. This issue was observed in AR9002/AR9003 chips while doing associate/dissociate in HT40 mode and interface up/down in iterative manner. After some iterations, the chip was moved to deaf state. Somehow the pci devices are recovered by poll work after chip reset. Raading the nf values in all supported extension chains when the hw is not yet configured in HT40 mode results invalid values. Cc: stable@kernel.org Signed-off-by: Rajkumar Manoharan <rmanoharan@atheros.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/mv643xx_eth.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud