From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
mgross@linux.intel.com, aili@codeaurora.org,
dwalker@codeaurora.org, tiwai@suse.de, bruce.w.allan@intel.com,
davidb@quicinc.com, mcgrof@gmail.com, pavel@ucw.cz,
linux-pm <linux-pm@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]PM QOS refresh against next-20100430
Date: Mon, 3 May 2010 22:39:19 +0100 [thread overview]
Message-ID: <20100503213919.GA18910@srcf.ucam.org> (raw)
In-Reply-To: <87tyqo537l.fsf@deeprootsystems.com>
On Mon, May 03, 2010 at 10:01:50AM -0700, Kevin Hilman wrote:
> Jonathan Corbet <corbet@lwn.net> writes:
> > Well, shallow could mean that the state lacks the CPUIDLE_FLAG_DEEP
> > flag; that should be relatively portable. In any case, it seems
> > more so than "if I put in a 55us latency requirement, I'll stay out
> > of C3".
>
> I guess it depends on your goal. Do you just want to stay out of C3
> on your current platform? or do you want to stay out of any low-power
> state (on any platform) where you'll have a latency of > 55 usecs?
I'd say that one plausible requirement is "DMA works", with another
being "all interrupts work" as distinguished from "wakeup interrupts
work".
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-05-03 21:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 21:20 [PATCH]PM QOS refresh against next-20100430 mark gross
2010-04-30 22:13 ` Rafael J. Wysocki
2010-04-30 23:05 ` mark gross
2010-04-30 23:05 ` mark gross
2010-04-30 23:08 ` Rafael J. Wysocki
2010-04-30 23:08 ` Rafael J. Wysocki
2010-05-04 14:30 ` mark gross
2010-05-04 14:30 ` mark gross
2010-05-05 23:59 ` Rafael J. Wysocki
2010-05-05 23:59 ` Rafael J. Wysocki
2010-04-30 22:13 ` Rafael J. Wysocki
2010-05-03 16:33 ` Jonathan Corbet
2010-05-03 16:33 ` Jonathan Corbet
2010-05-03 16:40 ` Kevin Hilman
2010-05-03 16:42 ` Jonathan Corbet
2010-05-03 16:42 ` Jonathan Corbet
2010-05-03 17:01 ` Kevin Hilman
2010-05-03 17:10 ` Jonathan Corbet
2010-05-03 17:10 ` Jonathan Corbet
2010-05-03 21:39 ` Matthew Garrett
2010-05-03 21:39 ` Matthew Garrett [this message]
2010-05-03 17:01 ` Kevin Hilman
2010-05-04 4:16 ` Pavel Machek
2010-05-04 4:16 ` Pavel Machek
2010-05-03 16:40 ` Kevin Hilman
2010-05-04 4:41 ` [linux-pm] " mark gross
2010-05-04 4:41 ` mark gross
-- strict thread matches above, loose matches on Subject: below --
2010-04-30 21:20 mark gross
2010-04-30 21:17 mark gross
2010-04-30 21:17 mark gross
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=20100503213919.GA18910@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=aili@codeaurora.org \
--cc=bruce.w.allan@intel.com \
--cc=corbet@lwn.net \
--cc=davidb@quicinc.com \
--cc=dwalker@codeaurora.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mcgrof@gmail.com \
--cc=mgross@linux.intel.com \
--cc=pavel@ucw.cz \
--cc=tiwai@suse.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 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.