linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: "Jaroslav Fojtik" <jafojtik@seznam.cz>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ATH5k - Signal measurement reports wrong values
Date: Tue, 22 Jun 2010 13:01:02 +0900	[thread overview]
Message-ID: <201006221301.03254.br1@einfach.org> (raw)
In-Reply-To: <4C1FBD42.20217.106AB2@jafojtik.seznam.cz>

On Tue June 22 2010 04:28:02 Jaroslav Fojtik wrote:
> root@dvouramenna:~# dmesg |grep "ath5.*chip"
> [    6.632843] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
> [    7.101528] ath5k phy1: Atheros AR5213A chip found (MAC: 0x59, PHY:
> 0x43)
> 
> Both chipsets suffer with a same problem.

hi jara!

thanks, i was able to reproduce the problem here. can you try this patch, it 
should fix it. it's just one line, so you could also change that 1 to a 4 in 
the code directly. please let me know if it helps...

bruno

commit 36c597b80813988f6a9c47ca4a5cb5306bbc67fa
Author: Bruno Randolf <br1@einfach.org>
Date:   Tue Jun 22 12:37:34 2010 +0900

    ath5k: fix antenna div gc for <= AR5K_SREV_PHY_2413
    
    Commit 39d5b2c83ca8904b6826a0713263a4e5a9c0730a "ath5k: update
    AR5K_PHY_RESTART_DIV_GC values to match masks" introduced a regression on 
PHY
    chips older than AR5K_SREV_PHY_5413, which caused signal values to be 
about
    10dB less that before. This patch reverts the AR5K_PHY_RESTART_DIV_GC 
values to
    the same values which were effectively used before (without the bitmask
    mistake). This brings signal levels back to normal on these PHY chips.
    
    Signed-off-by: Bruno Randolf <br1@einfach.org>

diff --git a/drivers/net/wireless/ath/ath5k/phy.c 
b/drivers/net/wireless/ath/ath5k/phy.c
index 82720fc..2254cd1 100644
--- a/drivers/net/wireless/ath/ath5k/phy.c
+++ b/drivers/net/wireless/ath/ath5k/phy.c
@@ -1768,7 +1768,7 @@ ath5k_hw_set_fast_div(struct ath5k_hw *ah, u8 ee_mode, 
bool enable)
 
 	if (enable) {
 		AR5K_REG_WRITE_BITS(ah, AR5K_PHY_RESTART,
-				AR5K_PHY_RESTART_DIV_GC, 1);
+				AR5K_PHY_RESTART_DIV_GC, 4);
 
 		AR5K_REG_ENABLE_BITS(ah, AR5K_PHY_FAST_ANT_DIV,
 					AR5K_PHY_FAST_ANT_DIV_EN);

  reply	other threads:[~2010-06-22  4:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-20 19:20 ATH5k - Signal measurement reports wrong values Jaroslav Fojtik
2010-06-21  1:26 ` Bruno Randolf
2010-06-21  7:23   ` Jaroslav Fojtik
2010-06-21  7:50     ` Bruno Randolf
2010-06-21 19:28       ` Jaroslav Fojtik
2010-06-22  4:01         ` Bruno Randolf [this message]
2010-06-23  9:03       ` ATH5k - Signal measurement reports wrong values - "calib" did not help Jaroslav Fojtik
2010-06-25  0:47         ` Bruno Randolf
2010-06-26 12:43           ` Jaroslav Fojtik
2010-06-26 16:07             ` Bruno Randolf
2010-06-26 17:54               ` ATH5k - Signal measurement reports wrong values - thanks for a fix Jaroslav Fojtik
2010-06-27  2:20                 ` Bruno Randolf
2010-06-27  7:28                   ` Jaroslav Fojtik
2010-06-28  1:21                     ` Bruno Randolf
2010-06-30  7:15                       ` Jaroslav Fojtik
2010-06-30  7:26                         ` Bruno Randolf
2010-07-01 20:11                           ` ATH5k - Signal measurement drops Jaroslav Fojtik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201006221301.03254.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=jafojtik@seznam.cz \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).