From: "H. Peter Anvin" <hpa@zytor.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 1/5] mrst_pmu: driver for Intel Moorestown Power Management Unit
Date: Wed, 03 Aug 2011 16:04:32 -0700 [thread overview]
Message-ID: <4E39D400.2080507@zytor.com> (raw)
In-Reply-To: <8e24ed2af46a5d008d85bfeb128d25efc394a3fd.1312400543.git.len.brown@intel.com>
On 08/03/2011 12:44 PM, Len Brown wrote:
> From: Len Brown <len.brown@intel.com>
>
> The Moorestown (MRST) Power Management Unit (PMU) driver
> directs the SOC power states in the "Langwell" south complex (SCU).
>
> It hooks pci_platform_pm_ops[] and thus observes all PCI ".set_state"
> requests. For devices in the SC, the pmu driver translates those
> PCI requests into the appropriate commands for the SCU.
>
> The PMU driver helps implement S0i3, a deep system idle power idle state.
> Entry into S0i3 is via cpuidle, just like regular processor c-states.
> S0i3 depends on pre-conditions including uni-processor, graphics off,
> and certain IO devices in the SC must be off. If those pre-conditions
> are met, then the PMU allows cpuidle to enter S0i3, otherwise such requests
> are demoted, either to Atom C4 or Atom C6.
>
> This driver is based on prototype work by Bruce Flemming,
> Illyas Mansoor, Rajeev D. Muralidhar, Vishwesh M. Rudramuni,
> Hari Seshadri and Sujith Thomas. The current driver also
> includes contributions from H. Peter Anvin, Arjan van de Ven,
> Kristen Accardi, and Yong Wang.
>
> Thanks for additional review feedback from Alan Cox and Randy Dunlap.
>
> Signed-off-by: Len Brown <len.brown@intel.com>
> Acked-by: Alan Cox <alan@linux.intel.com>
> ---
> MAINTAINERS | 6 +
> arch/x86/platform/mrst/Makefile | 1 +
> arch/x86/platform/mrst/pmu.c | 817 +++++++++++++++++++++++++++++++++++++++
> arch/x86/platform/mrst/pmu.h | 234 +++++++++++
> 4 files changed, 1058 insertions(+), 0 deletions(-)
> create mode 100644 arch/x86/platform/mrst/pmu.c
> create mode 100644 arch/x86/platform/mrst/pmu.h
>
Acked-by: H. Peter Anvin <hpa@linux.intel.com>
-hpa
prev parent reply other threads:[~2011-08-03 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 19:44 idle patch queue for Linux 3.1 Len Brown
2011-08-03 19:44 ` [PATCH 1/5] mrst_pmu: driver for Intel Moorestown Power Management Unit Len Brown
2011-08-03 19:44 ` [PATCH 2/5] cpuidle: create bootparam "cpuidle.off=1" Len Brown
2011-08-03 19:44 ` [PATCH 3/5] cpuidle: replace xen access to x86 pm_idle and default_idle Len Brown
2011-08-03 22:35 ` H. Peter Anvin
2011-08-03 19:44 ` [PATCH 4/5] x86 idle: move mwait_idle_with_hints() to where it is used Len Brown
2011-08-03 22:36 ` H. Peter Anvin
2011-08-03 19:44 ` [PATCH 5/5] cpuidle: stop depending on pm_idle Len Brown
2011-08-03 22:36 ` H. Peter Anvin
[not found] ` <CAAXLqgrnRi25WM2HpHxe-R4ePrgdbVROky4+=3Jr489M7zbgUA@mail.gmail.com>
2011-08-05 9:48 ` [linux-pm] " Deepthi Dharwar
2011-08-05 12:18 ` [linux-pm] [PATCH 5/5] cpuidle: stop depending on pm_idle --build break Deepthi Dharwar
2011-08-03 23:04 ` H. Peter Anvin [this message]
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=4E39D400.2080507@zytor.com \
--to=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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