public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-kernel@vger.kernel.org
Cc: linux-usb-devel@lists.sourceforge.net
Subject: PATCH/RFC:  driver model/pmcore wakeup hooks (0/4)
Date: Mon, 4 Oct 2004 13:54:37 -0700	[thread overview]
Message-ID: <200410041354.37932.david-b@pacbell.net> (raw)

There's been some discussion about limitations of the current
pmcore for systems that want to be partially suspended most
of the time.  That is, where the power management needs to
affect ACPI G0 states, not G1 states like S1/S3/S4, and isn't cpufreq.

One significant example involves USB mice.  If they were to be
suspended (usb_suspend_device) after a few seconds of inactivity,
that change could often spread up the device tree and let the
USB host controller stop DMA access.  Some x86 CPUs could
then enter C3 and save a couple Watts of battery power ... until
the mouse moved, and woke that branch of the device tree
for a while (until the mouse went idle again).

Most of the parts for that are now in place.  But trying to use
them will turn up places where the pieces don't fit together
very well yet ... and wakeup support is one of them!  So for
example it's not possible to disable such an autosuspend
mechanism for mice that can't actually issue wakeups.

So here are a few patches that add some driver model support
for wakeup capabilities, and use it for PCI and USB.

 - wake-core.patch, adds two bits and sysfs control over one of them
 - wake-pci.patch, makes pci use those bits
 - wake-usbcore.patch, makes usb do so (replacing code/hacks)
 - wake-ohci.patch, matching wake-usbcore

The patches follow this, going to LKML.

Comments?

- Dave

             reply	other threads:[~2004-10-04 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 20:54 David Brownell [this message]
2004-10-05 19:32 ` PATCH/RFC: driver model/pmcore wakeup hooks (0/4) Pavel Machek
2004-10-05 20:01   ` 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=200410041354.37932.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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