From: Gabor Juhos <juhosg@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 1/2] ath9k: wake up the chip for PS config changes
Date: Thu, 23 Jul 2009 11:35:31 +0200 [thread overview]
Message-ID: <4A682EE3.9010407@openwrt.org> (raw)
In-Reply-To: <20090723084442.GB9186@vasanth-laptop>
Vasanthakumar Thiagarajan ?rta:
> On Thu, Jul 23, 2009 at 02:04:11PM +0530, Gabor Juhos wrote:
>> If we are in NETWORK_SLEEP state, calling of 'ath9k_hw_setrxabort' in
>> 'ath9k_config' will fail with the following error:
>>
>> ath9k: timeout (100000 us) on reg 0x806c: 0xdeadbeef & 0x01f00000 != 0x00000000
>> ath9k: RX failed to go idle in 10 ms RXSM=0xdeadbeef
>>
>> Fix it by waking up the chip, and set 'ps_restore_mode' directly instead
>> of calling the 'ath9k_hw_setpower' routine..
>>
>> The problem is reported by Luis:
>> http://article.gmane.org/gmane.linux.kernel.wireless.general/34363
>>
>> Changes-licensed-under: ISC
>> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
>> ---
>> if (changed & IEEE80211_CONF_CHANGE_PS) {
>> + ath9k_ps_wakeup(sc);
>
> This seems to be a workaround. chip should not be sleeping when
> mac80211 thinks it is awake.
Hm, first I thought this is a bug in ath9k:
ath9k: AWAKE -> NETWORK SLEEP
ath9k: timeout (100000 us) on reg 0x806c: 0xdeadbeef & 0x01f00000 != 0x00000000
ath9k: RX failed to go idle in 10 ms RXSM=0xdeadbeef
ath9k: NETWORK SLEEP -> NETWORK SLEEP
You are righ probably, this can happen when mac80211 tells us to enter PS mode,
even if we are in it currently. Although I have no idea yet how this may happen.
Gabor
WARNING: multiple messages have this Message-ID (diff)
From: Gabor Juhos <juhosg@openwrt.org>
To: Vasanthakumar Thiagarajan <vasanth@atheros.com>
Cc: John Linville <linville@tuxdriver.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Jouni Malinen <Jouni.Malinen@Atheros.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] ath9k: wake up the chip for PS config changes
Date: Thu, 23 Jul 2009 11:35:31 +0200 [thread overview]
Message-ID: <4A682EE3.9010407@openwrt.org> (raw)
In-Reply-To: <20090723084442.GB9186@vasanth-laptop>
Vasanthakumar Thiagarajan írta:
> On Thu, Jul 23, 2009 at 02:04:11PM +0530, Gabor Juhos wrote:
>> If we are in NETWORK_SLEEP state, calling of 'ath9k_hw_setrxabort' in
>> 'ath9k_config' will fail with the following error:
>>
>> ath9k: timeout (100000 us) on reg 0x806c: 0xdeadbeef & 0x01f00000 != 0x00000000
>> ath9k: RX failed to go idle in 10 ms RXSM=0xdeadbeef
>>
>> Fix it by waking up the chip, and set 'ps_restore_mode' directly instead
>> of calling the 'ath9k_hw_setpower' routine..
>>
>> The problem is reported by Luis:
>> http://article.gmane.org/gmane.linux.kernel.wireless.general/34363
>>
>> Changes-licensed-under: ISC
>> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
>> ---
>> if (changed & IEEE80211_CONF_CHANGE_PS) {
>> + ath9k_ps_wakeup(sc);
>
> This seems to be a workaround. chip should not be sleeping when
> mac80211 thinks it is awake.
Hm, first I thought this is a bug in ath9k:
ath9k: AWAKE -> NETWORK SLEEP
ath9k: timeout (100000 us) on reg 0x806c: 0xdeadbeef & 0x01f00000 != 0x00000000
ath9k: RX failed to go idle in 10 ms RXSM=0xdeadbeef
ath9k: NETWORK SLEEP -> NETWORK SLEEP
You are righ probably, this can happen when mac80211 tells us to enter PS mode,
even if we are in it currently. Although I have no idea yet how this may happen.
Gabor
next prev parent reply other threads:[~2009-07-23 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 8:34 [ath9k-devel] [PATCH 1/2] ath9k: wake up the chip for PS config changes Gabor Juhos
2009-07-23 8:34 ` Gabor Juhos
2009-07-23 8:34 ` [ath9k-devel] [PATCH 2/2] ath9k: get rid of unnecessary setpower calls Gabor Juhos
2009-07-23 8:34 ` Gabor Juhos
2009-07-23 8:44 ` [ath9k-devel] [PATCH 1/2] ath9k: wake up the chip for PS config changes Vasanthakumar Thiagarajan
2009-07-23 8:44 ` Vasanthakumar Thiagarajan
2009-07-23 9:35 ` Gabor Juhos [this message]
2009-07-23 9:35 ` Gabor Juhos
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=4A682EE3.9010407@openwrt.org \
--to=juhosg@openwrt.org \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.