From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [REGRESSION] usb devices don't wake up the system
Date: Tue, 06 Jul 2010 23:51:46 +0300 [thread overview]
Message-ID: <1278449506.3793.8.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1007061300580.1327-100000@iolanthe.rowland.org>
Ok, it seems that recent changes really did made /proc/acpi/wakeup
unnecessary.
Let me explain from beginning the current situation:
1. Indeed if I enable manually wakeup on both usb controller, wakeup
works.
usb controller = /sys/devices/pci0000:00/0000:00:1a.0/power/wakeup
usb device = /sys/devices/pci0000:00/0000:00:1a.0/usb2/2-2/power/wakeup
UDEV rule to set wakeup on usb controller works:
SUBSYSTEM=="pci", DRIVER=="uhci_hcd", ATTR{power/wakeup}="enabled"
SUBSYSTEM=="pci", DRIVER=="ehci_hcd", ATTR{power/wakeup}="enabled"
UDEV rule to set wakeup on device itself just doesn't work, even though
udev executes it:
ACTION=="add", ENV{DEVTYPE}=="usb_device", ATTR{power/wakeup}="enabled"
I did try to add my usb id for mouse like you did. It of course doesn't
help.
I also found that above rule, *sometimes* works, but very rarely, so
indeed something else sets it. I strongly suspect its kernel.
I also think that I shouldn't need to set wakeup to enabled on usb
controller. This should be done automaticly as soon as I set 'enabled'
on usb device.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-07-06 20:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 23:31 [REGRESSION] usb devices don't wake up the system Maxim Levitsky
2010-06-30 23:40 ` Rafael J. Wysocki
2010-07-01 0:28 ` Maxim Levitsky
2010-07-01 14:42 ` Alan Stern
2010-07-01 18:58 ` Rafael J. Wysocki
2010-07-01 20:44 ` Maxim Levitsky
2010-07-01 21:07 ` Rafael J. Wysocki
2010-07-03 22:41 ` Maxim Levitsky
2010-07-03 22:42 ` Maxim Levitsky
2010-07-03 23:27 ` Rafael J. Wysocki
2010-07-04 12:51 ` Alan Stern
2010-07-04 15:44 ` Maxim Levitsky
2010-07-06 15:17 ` Alan Stern
2010-07-06 16:51 ` Maxim Levitsky
2010-07-06 17:07 ` Alan Stern
2010-07-06 20:51 ` Maxim Levitsky [this message]
2010-07-06 23:05 ` Rafael J. Wysocki
2010-07-07 15:33 ` Alan Stern
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=1278449506.3793.8.camel@localhost.localdomain \
--to=maximlevitsky@gmail.com \
--cc=linux-pm@lists.linux-foundation.org \
--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