From: David Brownell <david-b@pacbell.net>
To: Len Brown <len.brown@intel.com>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: PATCH/RFC: driver model/pmcore wakeup hooks (1/4)
Date: Mon, 18 Oct 2004 20:41:02 -0700 [thread overview]
Message-ID: <200410182041.02192.david-b@pacbell.net> (raw)
In-Reply-To: <1097906636.14156.41.camel@d845pe>
On Friday 15 October 2004 11:03 pm, Len Brown wrote:
> > - ACPI (this should probably replace the new /proc/acpi/wakeup)
>
> Agreed. That file is a temporary solution.
> The right solution is for the devices to appear in the right
> place in the device tree and to hang the wakeup capabilities
> off of them there.
So what would that patch need before ACPI could convert to use it?
I didn't notice any obvious associations between the strings in
the acpi/wakeup file and anything in sysfs. Which of USB1..USB4
was which of the three controllers shown by "lspci" (and which
one was "extra"!), as one head-scratcher.
For PCI, I'd kind of expect pci_enable_wake() to trigger the
additional ACPI-specific work to make sure the device can
actually wake that system. Seems like dev->platform_data
might need to combine with some platform-specific API hook.
- Dave
next prev parent reply other threads:[~2004-10-19 3:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410051309.02105.david-b@pacbell.net>
[not found] ` <200410051309.02105.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2004-10-16 6:03 ` PATCH/RFC: driver model/pmcore wakeup hooks (1/4) Len Brown
2004-10-19 3:41 ` David Brownell [this message]
[not found] ` <200410182041.02192.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2004-10-19 4:55 ` Hiroshi 2 Itoh
2004-10-19 5:18 ` [ACPI] " David Brownell
2004-10-20 6:16 ` Len Brown
2004-10-19 9:11 Li, Shaohua
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=200410182041.02192.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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