From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
linux-pm@osdl.org, linux-pm@lists.osdl.org
Subject: Re: [linux-pm] [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs
Date: Mon, 8 Jan 2007 14:10:55 +0100 [thread overview]
Message-ID: <20070108131055.GB25933@elf.ucw.cz> (raw)
In-Reply-To: <200701071931.20306.david-b@pacbell.net>
On Sun 2007-01-07 19:31:19, David Brownell wrote:
> On Saturday 06 January 2007 9:54 pm, Matthew Garrett wrote:
> > On Sat, Jan 06, 2007 at 02:21:41PM -0800, David Brownell wrote:
> >
> > > Please tell me you mean "devices with a /sys/devices/.../power/wakeup"
> > > attribute. And that ACPI is finally going to start working with those
> > > attributes ...
> >
> > It's not necessarily possible to map from an ACPI object with a wakeup
> > capability to a Linux device,
>
> That seems singularly useless then. If there's no such mapping, there's
> really no point to the /proc/acpi/wakeup table... why not just always
> enable every possible device as a wakeup source, since that information
> is evidently not designed to be usable for anything?
If that's the case, please keep the interface in /proc. One useless
interface is bad... two of them ... :-).
Anyway yes it can be usefull for debugging unexpected machine
resumes. /proc/acpi/wakeup names are still _somehow_ human readable,
so it is useful for debugging.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-01-08 13:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 11:35 [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs Zhang Rui
2007-01-06 22:21 ` David Brownell
2007-01-07 5:54 ` [linux-pm] " Matthew Garrett
2007-01-08 3:31 ` David Brownell
2007-01-08 13:10 ` Pavel Machek [this message]
2007-01-25 4:14 ` Len Brown
2007-01-25 5:50 ` Matthew Garrett
2007-01-25 9:35 ` David Brownell
2007-01-08 11:40 ` Zhang Rui
2007-01-08 13:13 ` Pavel Machek
2007-01-25 2:28 ` Len Brown
2007-01-25 12:08 ` Pavel Machek
2007-01-25 13:15 ` David Brownell
2007-01-25 19:51 ` Pavel Machek
2007-01-26 1:36 ` Zhang Rui
2007-01-10 20:53 ` David Brownell
2007-01-25 4:17 ` Len Brown
2007-01-25 13:15 ` Pavel Machek
2007-01-25 3:33 ` [linux-pm] " Len Brown
2007-01-25 3:28 ` Len Brown
2007-01-25 9:54 ` David Brownell
2007-01-25 19:37 ` Pavel Machek
2007-01-07 11:15 ` Pavel Machek
2007-01-25 2:03 ` Len Brown
2007-01-25 2:52 ` Nigel Cunningham
2007-01-25 8:17 ` Rafael J. Wysocki
2007-01-25 10:00 ` [linux-pm] " David Brownell
[not found] ` <1169358521.5691.2.camel@localhost.localdomain>
2007-01-25 3:50 ` [PATCH 0/3] " Len Brown
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=20070108131055.GB25933@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=david-b@pacbell.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=linux-pm@osdl.org \
--cc=mjg59@srcf.ucam.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