From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Huang Ying <ying.huang@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org, Bjorn Mork <bjorn@mork.no>
Subject: Re: [RFC] PCI/PM: Add ABI document for sysfs file d3cold_allowed
Date: Fri, 27 Jul 2012 21:07:10 +0200 [thread overview]
Message-ID: <201207272107.11080.rjw@sisk.pl> (raw)
In-Reply-To: <1343376454-28520-1-git-send-email-ying.huang@intel.com>
On Friday, July 27, 2012, Huang Ying wrote:
> This patch adds ABI document for the following sysfs file:
>
> /sys/bus/pci/devices/.../d3cold_allowed
>
> Signed-off-by: Huang Ying <ying.huang@intel.com>
Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> Documentation/ABI/testing/sysfs-bus-pci | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> --- a/Documentation/ABI/testing/sysfs-bus-pci
> +++ b/Documentation/ABI/testing/sysfs-bus-pci
> @@ -210,3 +210,15 @@ Users:
> firmware assigned instance number of the PCI
> device that can help in understanding the firmware
> intended order of the PCI device.
> +
> +What: /sys/bus/pci/devices/.../d3cold_allowed
> +Date: July 2012
> +Contact: Huang Ying <ying.huang@intel.com>
> +Description:
> + d3cold_allowed is bit to control whether the corresponding PCI
> + device can be put into D3Cold state. If it is cleared, the
> + device will never be put into D3Cold state. If it is set, the
> + device may be put into D3Cold state if other requirement are
> + satisfied too. Reading this attribute will show the current
> + value of d3cold_allowed bit. Writting this attribute will set
> + the value of d3cold_allowed bit.
>
>
next prev parent reply other threads:[~2012-07-27 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 8:07 [RFC] PCI/PM: Add ABI document for sysfs file d3cold_allowed Huang Ying
2012-07-27 19:07 ` Rafael J. Wysocki [this message]
2012-07-30 18:03 ` Don Dutile
2012-07-31 3:12 ` Huang Ying
2012-07-31 13:50 ` Don Dutile
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=201207272107.11080.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=bhelgaas@google.com \
--cc=bjorn@mork.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ying.huang@intel.com \
/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).