From: David Brownell <david-b@pacbell.net>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 2.6.21-rc5-git] make /proc/acpi/wakeup more useful
Date: Thu, 5 Apr 2007 03:58:43 -0700 [thread overview]
Message-ID: <200704050358.43689.david-b@pacbell.net> (raw)
In-Reply-To: <1175759995.23121.18.camel@localhost.localdomain>
On Thursday 05 April 2007 12:59 am, Zhang Rui wrote:
> On Wed, 2007-04-04 at 08:41 +0800, David Brownell wrote:
> > In that example, two devices don't actually exist (USB3, S139), one can't
> > issue wakeup events (PCI0), and two seem harmlessly (?) confused (MDM and
> > AUD are the same PCI device, but it's the _modem_ that does wake-on-ring).
> >
> Well, ACPI can't find the sysfs node for all the wakeup-enabled devices.
The only example of that type in the example I provided is SLPB, where the
sysfs node is ACPI-internal; I'm not sure how one can detect such cases.
> In fact, only pci and pnp devices can be found now.
Well, PNP courtesy of a previous patch from me, but remember that I was
using that as an example of a ** BOGUS ACPI TABLE ** as summarized above.
In my observation, such bogus tables are common. (This particular one
was, I believe, copied from a system using a higher end version of the
same southbridge ... but which may well have had its own errors.)
> ACPI needs the ability to distinguish all the physical devices, i.e. map
> ACPI device to physical device nodes in sysfs, which I mentioned before.
For wakeup devices, the main issue I've seen is with button devices.
In my limited set of test sytems, everything else is either PCI, PNP,
or a bug (listing a non-existent device).
If this patch starts to get deployed, I expect other people will find
a few other curiousities ... and likely some things to be fixed.
The /sys/devices/acpi_system:00/ tree is kind of new. I suspect one
way it could be more informative is to set up cross-links in sysfs
between the ACPI devices and the "real" device nodes ... e.g. on the
system I'm using right now .../device:00/PNP0A03:00/device:15/PNP0B00:00
could have a link pointing to /sys/devices/pnp0/00:06 ... and that PNP
node in turn could have an "acpi" link pointing back to the ACPI thing.
Such cross-links would let people see those relationships, and observe
which links are missing or otherwise strange. Fixing the bugs would
seem unlikely until those things become visible.
- Dave
next prev parent reply other threads:[~2007-04-05 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 0:41 [patch 2.6.21-rc5-git] make /proc/acpi/wakeup more useful David Brownell
2007-04-05 7:59 ` Zhang Rui
2007-04-05 10:58 ` David Brownell [this message]
2007-04-06 9:36 ` Zhang Rui
2007-04-06 15:43 ` David Brownell
2007-04-07 5:01 ` Greg KH
2007-04-07 20:08 ` David Brownell
2007-04-09 2:36 ` Zhang Rui
2007-04-09 5:35 ` David Brownell
2007-04-10 23:29 ` David Brownell
2007-04-11 0:10 ` David Brownell
2007-04-13 15:59 ` Pavel Machek
2007-04-17 19:53 ` David Brownell
2007-04-17 21:57 ` David Brownell
2007-04-18 3:03 ` Greg KH
2007-04-18 3:25 ` David Brownell
2007-04-05 9:26 ` Matthew Garrett
2007-04-05 10:35 ` David Brownell
2007-04-25 19:22 ` 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=200704050358.43689.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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