linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elias Oltmanns <eo@nebensachen.de>
To: "Nick Kossifidis" <mickflemm@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Jiri Slaby" <jirislaby@gmail.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k: Fix reset sequence for AR5212 in general and RF5111 in particular
Date: Sun, 26 Oct 2008 23:52:47 +0100	[thread overview]
Message-ID: <87r663t1ds.fsf@denkblock.local> (raw)
In-Reply-To: <40f31dec0810261533g3143bd9bue0f3eff88c6936e9@mail.gmail.com> (Nick Kossifidis's message of "Mon, 27 Oct 2008 00:33:40 +0200")

"Nick Kossifidis" <mickflemm@gmail.com> wrote:
> 2008/10/26 Elias Oltmanns <eo@nebensachen.de>:
>>
>
>>                /*
>>                 * Write some more initial register settings
>>                 */
>> -               if (ah->ah_version == AR5K_AR5212) {
>> +               if (ah->ah_version == AR5K_AR5212 &&
>> +                   ah->ah_radio > AR5K_RF5111) {
>
> even better: ah->ah_phy_revision > AR5K_SREV_PHY_5212

Just to be absolutely sure: ah->ah_phy_revision >= AR5K_SREV_PHY_5212
right?

>
>>                        ath5k_hw_reg_write(ah, 0x0002a002, 0x982c);
>>
>>                        if (channel->hw_value == CHANNEL_G)
>> @@ -858,6 +859,7 @@ int ath5k_hw_reset(struct ath5k_hw *ah, enum ieee80211_if_types op_mode,
>>
>>                        data = ath5k_hw_reg_read(ah, 0xa228);
>>                        data &= 0xfffe03ff;
>> +                       data |= 0x00000800;
>>                        ath5k_hw_reg_write(ah, data, 0xa228);
>>                        data = 0;
>>
>
> Can you please use the macros from ath5k.h to set these parameters ?
> (i got the above from decompiling binary HAL that's why i have fixed
> masks -no magic values- but now that we know what's going on we must
> make the code human-readable)
> And also please change 0xa228 with it's name from reg.h :
>
> 2557 #define AR5K_PHY_DAG_CCK_CTL                    0xa228
> 2558 #define AR5K_PHY_DAG_CCK_CTL_EN_RSSI_THR        0x00000200
> 2559 #define AR5K_PHY_DAG_CCK_CTL_RSSI_THR           0x0001fc00
> 2560 #define AR5K_PHY_DAG_CCK_CTL_RSSI_THR_S         10
>
> Normaly i'll update reset.c this week so you can always wait for a
> more generic fix ;-)

Well, I'm always happy to leave the work to others ;-). The only reason
why I kept resending patches was to make sure that a minimal fix would
get merged into a stable release eventually. Presumably, a rework of the
reset sequence in itself would not be appropriate for stable. Still, if
you'll take care get something into stable, that's fine with me.
Otherwise, just let me know and I'll keep those patches coming and you
occupied reviewing them ;-).

Regards,

Elias

  reply	other threads:[~2008-10-26 22:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87prlr9mna.fsf@denkblock.local>
2008-10-25 23:21 ` [PATCH] ath5k: Fix reset sequence for AR5212 in general and RF5111 in particular Nick Kossifidis
2008-10-26 17:52   ` Elias Oltmanns
2008-10-26 18:32     ` Nick Kossifidis
2008-10-26 20:47       ` Elias Oltmanns
2008-10-26 22:33         ` Nick Kossifidis
2008-10-26 22:52           ` Elias Oltmanns [this message]
2008-10-27 20:31             ` Nick Kossifidis
2008-10-29 13:25               ` Elias Oltmanns
2008-10-29 14:49                 ` Nick Kossifidis
2008-10-29 15:07                   ` Elias Oltmanns
2008-10-29 15:28                     ` Bob Copeland
2008-10-29 17:51                       ` Nick Kossifidis
2008-10-29 23:25                         ` Elias Oltmanns
2008-10-29 23:34                           ` John W. Linville
2008-10-29 23:56                             ` Elias Oltmanns
2008-10-30  0:04                             ` Elias Oltmanns
2008-10-27 18:36     ` Nils

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=87r663t1ds.fsf@denkblock.local \
    --to=eo@nebensachen.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=mickflemm@gmail.com \
    /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).