From: Davide Pesavento <davidepesa@gmail.com>
To: Vivek Natarajan <vivek.natraj@gmail.com>
Cc: Kalle Valo <kalle.valo@iki.fi>,
linux-wireless <linux-wireless@vger.kernel.org>,
mcgrof@gmail.com
Subject: Re: ath9k and power management
Date: Tue, 31 Mar 2009 11:40:57 +0200 [thread overview]
Message-ID: <2da21fe50903310240m2f18adf2ma23f095be397a9ea@mail.gmail.com> (raw)
In-Reply-To: <8e92b4100903302354x66276239m48a14f2182d959c7@mail.gmail.com>
On Tue, Mar 31, 2009 at 08:54, Vivek Natarajan <vivek.natraj@gmail.com> wrote:
> On Mon, Mar 30, 2009 at 7:01 PM, Davide Pesavento <davidepesa@gmail.com> wrote:
>> On Mon, Mar 30, 2009 at 11:38, Vivek Natarajan <vivek.natraj@gmail.com> wrote:
>>>
>>> ath9k: No need to abort Rx path when autosleep is enabled.
>>>
>>> For chipsets supporting autosleep feature, there is no need to abort
>>> Rx engine since they are capable of automatically going back to sleep
>>> after receiving a packet.
>>
>> I've applied your patch but unfortunately the behaviour is still the
>> same as before.
>
> One more patch sent:
> ath9k: Disable autosleep feature for AR9285 based chipsets.
>
> I hope you are using one of the AR9285 based. I have unit tested and it seems to
> work consistently now.
>
No, I'm not. Sorry for not reporting the hardware type earlier. My
card is identified as:
phy0: Atheros AR5418 MAC/BB Rev:2 AR5133 RF Rev:81:
mem=0xffffc20005020000, irq=17
Thanks,
Davide
next prev parent reply other threads:[~2009-03-31 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 14:27 ath9k and power management Davide Pesavento
2009-03-27 14:42 ` Kalle Valo
2009-03-27 14:54 ` Davide Pesavento
2009-03-27 15:07 ` Davide Pesavento
2009-03-27 15:13 ` Kalle Valo
2009-03-27 19:08 ` Davide Pesavento
2009-03-27 19:14 ` Luis R. Rodriguez
2009-03-30 9:38 ` Vivek Natarajan
2009-03-30 13:31 ` Davide Pesavento
2009-03-31 6:54 ` Vivek Natarajan
2009-03-31 9:40 ` Davide Pesavento [this message]
2009-04-03 14:11 ` Davide Pesavento
2009-04-17 19:57 ` Davide Pesavento
2009-04-18 2:48 ` Vivek Natarajan
2009-04-20 22:48 ` Davide Pesavento
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=2da21fe50903310240m2f18adf2ma23f095be397a9ea@mail.gmail.com \
--to=davidepesa@gmail.com \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=vivek.natraj@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).