linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: "Richard Schütz" <r.schtz@t-online.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k prevents CPU from entering C4 state (kernel 2.6.37 regression)
Date: Sat, 22 Jan 2011 23:52:42 +0100	[thread overview]
Message-ID: <201101222352.42913.chunkeey@googlemail.com> (raw)
In-Reply-To: <4D3B4057.5000206@t-online.de>

On Saturday 22 January 2011 21:38:47 Richard Schütz wrote:
> I noticed that from kernel 2.6.37 on (i've tested 2.6.38-rc2, too) ath9k 
> prevents my CPU (Intel Atom N450) from entering the C4 power state. It 
> only goes down to C2 (there's no C3) instead. In 2.6.36(.3) everything 
> is still fine. The CPU will only go down to C4 with 2.6.37 when the 
> wireless interface is brought down.

"ath9k: Fix a DMA latency issue for Intel Pinetrail platforms."
http://www.spinics.net/lists/linux-wireless/msg58264.html

the pm_qos value will be configurable with 2.6.38: 

"ath9k: Make PM-QOS value as user configurable"
http://www.spinics.net/lists/linux-wireless/msg61259.html

"This will help our customers to configure the pm-qos value according
to the effect in throughput due to the DMA latency problem which was
observed in Intel Pinetrail platforms."


  reply	other threads:[~2011-01-22 22:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 20:38 ath9k prevents CPU from entering C4 state (kernel 2.6.37 regression) Richard Schütz
2011-01-22 22:52 ` Christian Lamparter [this message]
2011-01-22 23:49   ` Thomas Bächler

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=201101222352.42913.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=r.schtz@t-online.de \
    /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).