From: Tino Keitel <tino.keitel@gmx.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] /proc/acpi/wakeup regression in 2.6.39-rc3
Date: Fri, 15 Apr 2011 16:54:57 +0200 [thread overview]
Message-ID: <20110415145457.GA27650@eazy.amigager.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1104151034580.2051-100000@iolanthe.rowland.org>
On Fri, Apr 15, 2011 at 10:38:47 -0400, Alan Stern wrote:
> On Fri, 15 Apr 2011, Rafael J. Wysocki wrote:
>
> > On Friday, April 15, 2011, Tino Keitel wrote:
> > > Hi,
> > >
> > > with 2.6.38, I enabled wakeup from suspend to RAM with the USB keyboard
> > > this way:
> > >
> > > echo USB2 > /proc/acpi/wakeup
> > >
> > > This does not work anymore with 2.6.39-rc3. Wakeup using the keyboard
> > > won't work, and the USB2 line in /proc/acpi/wakeup doesn't change to
> > > "enabled" after the echo command.
> > >
> > > Is this intended? If yes, what is the new way to enable keyboard
> > > wakeup?
> >
> > No, it's supposed to work IIRC. I'll have a look at that code tomorrow.
>
> Tino, can you check the contents of the power/wakeup files in the
> appropriate sysfs directories? That would be the directory for the
> keyboard device itself and the directory for the USB host controller
> for the bus the keyboard is on.
>
> By default, power/wakeup should be "enabled" for the keyboard device
> and "disabled" for the host controller. If you write "enabled" into
> the host controller's file by hand, does that fix the problem?
I already tried to write "enable" into all USB related wakeup files
yesterday, not change.
I'll check again how these files look like in 2.6.38, what sysfs
wakeup files change when writing into /proc/acpi/wakeup, and what
differences to 2.6.39-rc can be seen.
Regards,
Tino
next prev parent reply other threads:[~2011-04-15 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 22:25 Tino Keitel
2011-04-14 22:53 ` Rafael J. Wysocki
2011-04-15 14:38 ` [linux-pm] " Alan Stern
2011-04-15 14:54 ` Tino Keitel [this message]
2011-04-19 20:22 ` Tino Keitel
2011-04-19 21:28 ` Rafael J. Wysocki
2011-04-20 20:34 ` Rafael J. Wysocki
2011-04-20 23:50 ` Rafael J. Wysocki
2011-04-20 20:57 ` Rafael J. Wysocki
2011-04-17 18:27 ` Maciej Rutecki
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=20110415145457.GA27650@eazy.amigager.de \
--to=tino.keitel@gmx.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®