From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Subject: [patch 0/3] driver model wakeup flags
Date: Mon, 12 Sep 2005 19:23:58 -0700 [thread overview]
Message-ID: <200509121923.58993.david-b@pacbell.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
This is a refresh of the patch to add wakeup infrastructure to the
driver model, in three parts. Comments? Merge?
pm-wake.patch ... adds the flags, and sysfs support
pm-usb.patch ... usb devices use it
pm-pci.patch ... pci devices use it
The default gives the current behavior: wakeup is enabled on all
devices that support it. (Assuming ACPI etc don't get in the way...)
This goes back to having the sysfs "wakeup" file be tristate.
Wakeup can be "enabled" or "disabled", and toggled from userspace.
Or it can be unavailable, value "", if the hardware doesn't support
wakeup or if no software has marked the device as supporting wakeup.
I attach a simple script I wrote to show what devices are capable
of wakeup events. On one system, it reports wakeup allowed for
several builtin devices and a USB keyboard/hub:
lan on pci0000:00/0000:00:0a.0/0000:02:01.0
modem on pci0000:00/0000:00:06.1
hub on pci0000:00/0000:00:02.2/usb1
usb_host on pci0000:00/0000:00:02.2
input on pci0000:00/0000:00:02.1/usb3/3-1/3-1.1
hub on pci0000:00/0000:00:02.1/usb3/3-1
hub on pci0000:00/0000:00:02.1/usb3
usb_host on pci0000:00/0000:00:02.1
hub on pci0000:00/0000:00:02.0/usb2
usb_host on pci0000:00/0000:00:02.0
i2c on pci0000:00/0000:00:01.1
On this system /proc/acpi/wakeup says
Device Sleep state Status
USB0 3 disabled
USB1 3 disabled
USB2 3 disabled
MAC0 3 disabled
I'm guessing those are the 00:02.* and 02:01.0 nodes. The hubs and
input device (USB keyboard) use USB-internal wakeups and kick the
usb_host nodes ... ACPI wouldn't know about them. (I understand
that firewire could do the same sort of thing too.) The I2C device
is actually SMBUS, waking up from D3hot or D3cold; I suspect that's
handled by ACPI somehow.
- Dave
[-- Attachment #2: pm-wake --]
[-- Type: application/x-shellscript, Size: 1345 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2005-09-13 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 2:23 David Brownell [this message]
2005-09-13 2:39 ` [patch 1/3] driver model wakeup flags David Brownell
2005-09-13 2:39 ` [patch 2/3] usb device " David Brownell
2005-09-13 2:48 ` [patch 3/3] pci " David Brownell
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=200509121923.58993.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox