From: Sven Eckelmann <sven@narfation.org>
To: miaoqing@codeaurora.org
Cc: kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org,
ath9k-devel@qca.qualcomm.com, sssa@qti.qualcomm.com,
simon.wunderlich@openmesh.com
Subject: Re: [PATCH 2/2] ath9k: fix tx99 bus error
Date: Mon, 16 Apr 2018 14:57:20 +0200 [thread overview]
Message-ID: <5841149.Pfrk1JVkns@bentobox> (raw)
In-Reply-To: <1497921220-12940-2-git-send-email-miaoqing@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
On Dienstag, 20. Juni 2017 09:13:40 CEST miaoqing@codeaurora.org wrote:
> From: Miaoqing Pan <miaoqing@codeaurora.org>
>
> The hard coded register 0x9864 and 0x9924 are invalid
> for ar9300 chips.
[...]
> - REG_SET_BIT(ah, 0x9864, 0x7f000);
> - REG_SET_BIT(ah, 0x9924, 0x7f00fe);
Sorry that this messages comes so later after the patch was accepted. But what
were these things expected to do? My guess is that 0x9864 is AR_PHY_CCA and
the other one is something else (AR_PHY_TIMING5?). But yes, these would be ar9002
and not AR9003.
What are the problems that we would expect when the CCA threshold and the CYCPWR
threshold are no longer be set to the highest possible value? Are we now expecting
that the device is not transmitting at 99% when it sees other signals?
Btw. why are you writing that ar9300 chips don't have this? It looks to me
like the original code was taken from QCA's 9300 code [1]. Was it always broken
in the AR9300 hal and how was it now fixed with with the newer HALs?
Could it be that newer chips just have it mapped to a different location? AGC
on the 9300 seems to be at 0x9e00 and maybe the cca register should have been
0x9e1c (AR_PHY_CCA_0) and should be set to AR_PHY_CCA_THRESH62? And there is
also a AR_PHY_TIMING5 (0x9810) which might have to be set to
AR_PHY_TIMING5_CYCPWR_THR1 | AR_PHY_TIMING5_CYCPWR_THR1A. Of course, I have
absolutely no idea whether these registers actually control the
same thing and whether the settings are correct.
Kind regards,
Sven
[1] https://github.com/freebsd/freebsd/blob/386ddae58459341ec567604707805814a2128a57/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_tx99_tgt.c#L502
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-16 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 1:13 [PATCH 1/2] ath9k: fix tx99 use after free miaoqing
2017-06-20 1:13 ` [PATCH 2/2] ath9k: fix tx99 bus error miaoqing
2018-04-16 12:57 ` Sven Eckelmann [this message]
2017-06-21 13:52 ` [1/2] ath9k: fix tx99 use after free Kalle Valo
2017-06-28 16:53 ` Kalle Valo
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=5841149.Pfrk1JVkns@bentobox \
--to=sven@narfation.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing@codeaurora.org \
--cc=simon.wunderlich@openmesh.com \
--cc=sssa@qti.qualcomm.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