From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Kristoffer Ericson <kristoffer.ericson@gmail.com>,
stable@kernel.org, greg@kroah.com,
linux-wireless@vger.kernel.org, Peter Stuge <peter@stuge.se>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 2.6.32.y] ath9k: re-enable ps by default for new single chip families
Date: Wed, 16 Jun 2010 08:49:24 -0700 [thread overview]
Message-ID: <AANLkTimDp52ULRcO9NMgeV34olfpD97wYfmr_atOQ5AF@mail.gmail.com> (raw)
In-Reply-To: <4C18D2A5.5080702@gmail.com>
On Wed, Jun 16, 2010 at 6:33 AM, Justin P. Mattock
<justinmattock@gmail.com> wrote:
> On 06/16/2010 01:12 AM, Kristoffer Ericson wrote:
>>
>> On Tue, Jun 15, 2010 at 06:19:19PM -0400, Luis R. Rodriguez wrote:
>>>
>>> commit 14acdde6e527950f66c084dbf19bad6fbfcaeedc upstream.
>>>
>>> The newer single chip hardware family of chipsets have not been
>>> experiencing issues with power saving set by default with recent
>>> fixes merged (even into stable). The remaining issues are only
>>> reported with AR5416 and since enabling PS by default can increase
>>> power savings considerably best to take advantage of that feature
>>> as this has been tested properly.
>>
>> I havent had any issues lately. But that said Ive moved on to
>> 2.6.33, 2.6.34 which seems to work fine. Believe you set
>> to disabled by default on those?
>>
>> /Kristoffer
>>
>
> just tried to add this patch to the latest HEAD, but realized
> ath_set_hw_capab is missing(or I cant seem to grep it)
> if you have a patch for the latest tree let me know I can see if I'm hitting
> anything like before.
The patch would already be merged since 2.6.33.y, this patch is a
backport for 2.6.32.y. I just hadn't had time to backport it yet,
until today.
Luis
next prev parent reply other threads:[~2010-06-16 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 22:19 [PATCH 2.6.32.y] ath9k: re-enable ps by default for new single chip families Luis R. Rodriguez
2010-06-16 2:20 ` Justin P. Mattock
2010-06-16 8:12 ` Kristoffer Ericson
2010-06-16 13:33 ` Justin P. Mattock
2010-06-16 15:49 ` Luis R. Rodriguez [this message]
2010-06-16 16:01 ` Justin P. Mattock
2010-06-16 17:53 ` Luis R. Rodriguez
2010-06-16 18:15 ` Justin P. Mattock
2010-06-16 18:16 ` Luis R. Rodriguez
2010-06-16 19:14 ` Justin P. Mattock
2010-06-16 20:06 ` Luis R. Rodriguez
2010-06-16 20:40 ` Justin P. Mattock
2010-06-16 15:48 ` Luis R. Rodriguez
2010-07-27 22:22 ` [stable] " Greg KH
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=AANLkTimDp52ULRcO9NMgeV34olfpD97wYfmr_atOQ5AF@mail.gmail.com \
--to=lrodriguez@atheros.com \
--cc=greg@kroah.com \
--cc=justinmattock@gmail.com \
--cc=kristoffer.ericson@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=peter@stuge.se \
--cc=stable@kernel.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 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).