[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1104151034580.2051-100000@iolanthe.rowland.org>
Date: Fri, 15 Apr 2011 10:38:47 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Tino Keitel <tino.keitel@...ei.de>,
ACPI Devel Mailing List <linux-acpi@...r.kernel.org>,
Linux PM mailing list <linux-pm@...ts.linux-foundation.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] /proc/acpi/wakeup regression in 2.6.39-rc3
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?
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists