From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Suggestion for improving the handling of GPE enabling.
Date: Thu, 10 Mar 2005 13:30:33 +0000 [thread overview]
Message-ID: <1110461434.5918.202.camel@tyrosine> (raw)
In-Reply-To: <1110431446.9336.60.camel@d845pe>
On Thu, 2005-03-10 at 00:10 -0500, Len Brown wrote:
> On Wed, 2005-03-09 at 17:21, Pavel Machek wrote:
>
> > > 4. ACPI devices are in many different physical buses. If we just define
> > > an ACPI bus, we possibly can't show the bus hierarchy.
> >
> > Maybe ACPI device should be "under" real hardware one?
>
> I suspect that the current sysfs device tree hierarchy is largely
> fiction and that Linux would be better served by taking advantage of the
> hierarchy embodied in the DSDT.
>
> The "ACPI devices" such as power, sleep, lid as well as the battery are
> represented at the root level in the DSDT.
Are the ACPI HID names exposed to userspace yet? At the moment userspace
tools need to try loading every ACPI module. If the HIDs were exported
via sysfs and the ACPI drivers exported the devices they could bind to,
we could use hotplug to autoload the correct drivers.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-10 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 22:23 Suggestion for improving the handling of GPE enabling Nigel Cunningham
[not found] ` <1110318037.3663.19.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-03-09 1:31 ` Li Shaohua
[not found] ` <1110331896.12642.16.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-03-09 22:21 ` Pavel Machek
[not found] ` <20050309222122.GA32516-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-10 5:10 ` Len Brown
2005-03-10 10:11 ` Pavel Machek
2005-03-10 13:30 ` Matthew Garrett [this message]
2005-03-10 17:18 ` Karol Kozimor
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 2:30 Li, Shaohua
2005-03-11 4:50 Li, Shaohua
2005-03-11 5:05 Brown, Len
2005-03-11 5:43 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=1110461434.5918.202.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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