public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	ncunningham-3EexvZdKGZRWk0Htik3J/w@public.gmane.org,
	ACPI List
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Suggestion for improving the handling of GPE enabling.
Date: Thu, 10 Mar 2005 11:11:36 +0100	[thread overview]
Message-ID: <20050310101133.GD13444@elf.ucw.cz> (raw)
In-Reply-To: <1110431446.9336.60.camel@d845pe>

On Čt 10-03-05 00:10:47, 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.

Funny, I'd say that DSDT hierarchy is fiction and ... :-).

> The "ACPI devices" such as power, sleep, lid as well as the battery are
> represented at the root level in the DSDT.

It probably does not matter where power/sleep/lid are represented, but
things like ide-disk below ide-controller below pci bus make sense to
me (and we need that hierarchy for suspend/resume anyway). For devices
like lid... yeh, there's not much hierarchy there, just select some
place.
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!


-------------------------------------------------------
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_ide95&alloc_id\x14396&op=click

  reply	other threads:[~2005-03-10 10:11 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 [this message]
2005-03-10 13:30             ` Matthew Garrett
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=20050310101133.GD13444@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=ncunningham-3EexvZdKGZRWk0Htik3J/w@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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