From: Randy Dunlap <rdunlap@infradead.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] Add support driver for Intel Rapid Start Technology
Date: Tue, 02 Jul 2013 15:31:38 -0700 [thread overview]
Message-ID: <51D354CA.7010305@infradead.org> (raw)
In-Reply-To: <1372804061-2260-1-git-send-email-mjg59@srcf.ucam.org>
On 07/02/13 15:27, Matthew Garrett wrote:
> Intel Rapid Start Technology is a firmware-based suspend-to-disk
> implementation. Once placed in S3, the device will wake once either a
> timeout elapses or the battery reaches a critical level. It will then resume
> to the firmware and copy the contents of RAM to a specialised partition, and
> then power off the machine. If the user turns the machine back on the
> firmware will copy the contents of the partition back to RAM and then resume
> from S3 as normal.
>
> This driver provides an interface for configuring the wakeup events and
> timeout. It still requires firmware support and an appropriate suspend
> partition.
>
> Signed-off-by: Matthew Garrett <mjg59@srcf.ucam.org>
> ---
> .../ABI/testing/sysfs-driver-intel-rapid-start | 21 +++
> drivers/platform/x86/intel-rst.c | 209 +++++++++++++++++++++
> 2 files changed, 230 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-rapid-start
> create mode 100644 drivers/platform/x86/intel-rst.c
Kconfig and Makefile changes?
Is RST described in the current ACPI spec or somewhere else?
thanks,
--
~Randy
next prev parent reply other threads:[~2013-07-02 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 22:27 [PATCH] Add support driver for Intel Rapid Start Technology Matthew Garrett
2013-07-02 22:31 ` Randy Dunlap [this message]
2013-07-02 22:36 ` Matthew Garrett
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=51D354CA.7010305@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.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 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.