From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
mingo@redhat.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org,
"alan@linux.intel.com" <alan@linux.intel.com>
Subject: Re: [PATCH] x86: new Intel Atom SoC power management controller driver
Date: Thu, 06 Mar 2014 13:21:24 +0800 [thread overview]
Message-ID: <531805D4.6040806@linux.intel.com> (raw)
In-Reply-To: <5317F044.8080407@linux.intel.com>
On 2014/3/6 11:49, H. Peter Anvin wrote:
> On 03/05/2014 07:31 PM, Li, Aubrey wrote:
>> The Power Management Controller (PMC) controls many of the power
>> management features present in the SoC. This driver provides
>> interface to configure the Power Management Controller (PMC).
>>
>> This driver exposes PMC device state and sleep state residency
>> via debugfs for observation:
>> /sys/kernel/debugfs/pmc_atom/dev_state
>> /sys/kernel/debugfs/pmc_atom/sleep_state
>>
>> This driver also provides a native power off function via PMC PCI
>> IO port.
>>
>
> What is the reason for putting this in debugfs?
S0ix support on Atom SoC needs all of the devices under south complex to
be quiesced, as well as the devices under north complex. This interface
shows all of the devices states under platform control unit. If the
system is not able to enter S0ix, we have a way to diagnose. Or if the
system entered S0ix, we have counters to show S0ix entered and its
residency.
Thanks,
-Aubrey
>
> -hpa
>
>
>
>
next prev parent reply other threads:[~2014-03-06 5:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 3:31 [PATCH] x86: new Intel Atom SoC power management controller driver Li, Aubrey
2014-03-06 3:49 ` H. Peter Anvin
2014-03-06 5:21 ` Li, Aubrey [this message]
2014-03-06 5:28 ` H. Peter Anvin
2014-03-06 5:33 ` Li, Aubrey
2014-03-06 5:52 ` H. Peter Anvin
2014-03-06 5:58 ` Li, Aubrey
2014-03-06 16:30 ` H. Peter Anvin
2014-03-07 0:26 ` Li, Aubrey
2014-03-07 0:41 ` Joe Perches
2014-03-07 2:08 ` Li, Aubrey
2014-03-07 2:21 ` Joe Perches
2014-03-07 3:04 ` Li, Aubrey
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=531805D4.6040806@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=tglx@linutronix.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