From: tip-bot for Daniel Drake <dsd@laptop.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
dsd@laptop.org, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:x86/olpc] x86, olpc-xo15-sci: Enable EC wakeup capability
Date: Sun, 24 Jul 2011 20:55:22 GMT [thread overview]
Message-ID: <tip-07d5b38e14b7ff98eb52e4a6db4e20abcc608da3@git.kernel.org> (raw)
In-Reply-To: <20110724173430.BE03C9D401C@zog.reactivated.net>
Commit-ID: 07d5b38e14b7ff98eb52e4a6db4e20abcc608da3
Gitweb: http://git.kernel.org/tip/07d5b38e14b7ff98eb52e4a6db4e20abcc608da3
Author: Daniel Drake <dsd@laptop.org>
AuthorDate: Sun, 24 Jul 2011 18:34:30 +0100
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 24 Jul 2011 20:16:05 +0200
x86, olpc-xo15-sci: Enable EC wakeup capability
Some recent changes to the way that ACPI handles wakeup flags
means that the XO15EC ACPI device is not wakeup-capable by
default so device_set_wakeup_enable() does nothing.
Use device_init_wakeup() to mark the device as wakeup capable,
and to enable wakeups.
Signed-off-by: Daniel Drake <dsd@laptop.org>
Link: http://lkml.kernel.org/r/20110724173430.BE03C9D401C@zog.reactivated.net
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/platform/olpc/olpc-xo15-sci.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/platform/olpc/olpc-xo15-sci.c b/arch/x86/platform/olpc/olpc-xo15-sci.c
index a5990eb..2b235b7 100644
--- a/arch/x86/platform/olpc/olpc-xo15-sci.c
+++ b/arch/x86/platform/olpc/olpc-xo15-sci.c
@@ -120,7 +120,7 @@ static int xo15_sci_add(struct acpi_device *device)
/* Enable wake-on-EC */
if (device->wakeup.flags.valid)
- device_set_wakeup_enable(&device->dev, true);
+ device_init_wakeup(&device->dev, true);
return 0;
}
prev parent reply other threads:[~2011-07-24 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 17:34 [PATCH resend] x86, olpc-xo15-sci: enable EC wakeup capability Daniel Drake
2011-07-24 20:55 ` tip-bot for Daniel Drake [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=tip-07d5b38e14b7ff98eb52e4a6db4e20abcc608da3@git.kernel.org \
--to=dsd@laptop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--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