From: "Nick Kossifidis" <mickflemm@gmail.com>
To: "Bob Copeland" <me@bobcopeland.com>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] [PATCH] ath5k: write beacon control register twice when resetting tsf
Date: Mon, 29 Sep 2008 19:30:01 +0300 [thread overview]
Message-ID: <40f31dec0809290930t350ac275j42e53fac60829fa@mail.gmail.com> (raw)
In-Reply-To: <20080928160943.GA30901@hash.localnet>
2008/9/28 Bob Copeland <me@bobcopeland.com>:
> According to the newly-released Atheros HAL code, asserting the
> TSF reset bit will toggle a hardware internal state, resulting in a
> spurious reset on the next chip reset. Whenever we force a TSF bit,
> write the bit twice to clear the internal signal.
>
> Signed-off-by: Bob Copeland <me@bobcopeland.com>
> ---
>
> This was the only major difference I found between code we're currently
> using in pcu.c and its equivalents in the HAL. See comment in
> ar5212ResetTsf. This is only compile-tested.
>
> (There are other differences but they are in the key setup code or
> beacon setup code that we are not using right now.)
>
> drivers/net/wireless/ath5k/pcu.c | 14 +++++++++++++-
> 1 files changed, 13 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/ath5k/pcu.c b/drivers/net/wireless/ath5k/pcu.c
> index c77cee2..c8f9170 100644
> --- a/drivers/net/wireless/ath5k/pcu.c
> +++ b/drivers/net/wireless/ath5k/pcu.c
> @@ -633,8 +633,20 @@ u64 ath5k_hw_get_tsf64(struct ath5k_hw *ah)
> */
> void ath5k_hw_reset_tsf(struct ath5k_hw *ah)
> {
> + u32 val;
> +
> ATH5K_TRACE(ah->ah_sc);
> - AR5K_REG_ENABLE_BITS(ah, AR5K_BEACON, AR5K_BEACON_RESET_TSF);
> +
> + val = ath5k_hw_reg_read(ah, AR5K_BEACON) | AR5K_BEACON_RESET_TSF;
> +
> + /*
> + * Each write to the RESET_TSF bit toggles a hardware internal
> + * signal to reset TSF, but if left high it will cause a TSF reset
> + * on the next chip reset as well. Thus we always write the value
> + * twice to clear the signal.
> + */
> + ath5k_hw_reg_write(ah, val, AR5K_BEACON);
> + ath5k_hw_reg_write(ah, val, AR5K_BEACON);
> }
>
> /*
> --
> 1.5.4.2.182.gb3092
>
> --
> Bob Copeland %% www.bobcopeland.com
>
> _______________________________________________
> ath5k-devel mailing list
> ath5k-devel@lists.ath5k.org
> https://lists.ath5k.org/mailman/listinfo/ath5k-devel
>
Acked-by: Nick Kossifidis <mickflemm@gmail.com>
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
prev parent reply other threads:[~2008-09-29 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 16:09 [PATCH] ath5k: write beacon control register twice when resetting tsf Bob Copeland
2008-09-29 16:30 ` Nick Kossifidis [this message]
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=40f31dec0809290930t350ac275j42e53fac60829fa@mail.gmail.com \
--to=mickflemm@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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).