public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
	lenb@kernel.org, "linux-acpi@vger" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/14] ACPI: make ACPI use driver model
Date: Fri, 08 Dec 2006 09:34:03 +0800	[thread overview]
Message-ID: <1165541643.1369.2.camel@sli10-conroe.sh.intel.com> (raw)
In-Reply-To: <200612070928.30460.bjorn.helgaas@hp.com>

On Fri, 2006-12-08 at 00:28 +0800, Bjorn Helgaas wrote:
> On Thursday 07 December 2006 05:56, Zhang Rui wrote:
> > 1. ACPI driver model. 
> > ACPI driver are made to follow Linux driver model.
> > The main work is to convert the registration interfaces,so that
> > ACPI devices are registered with the global device tree.
> >         Note the new .uevent method mark ACPI drivers by PNPID 
> > instead of by name. Udev script needs to look for "HWID = "
> > or "COMPTID = " to load the right ACPI driver.
> 
> I generally like the direction this is headed.
> 
> But I wonder whether it's right to expose the distinction between
> PNP devices and ACPI devices to userspace.
> 
> Assume you had a box where you can run either PNPBIOS firmware
> or ACPI firmware.  Since the box has exactly the same hardware
> in either case, it would be nice if everything in /sys and udev
> stayed the same.
> 
> Is it possible to extend the PNP model to include ACPI, rather
> than introducing a new ACPI model alongside the PNP model?
Don't think it's easy. ACPI driver uses some acpi helpers and handle
some ACPI specific event like notification/gpe ...

Thanks,
Shaohua

  reply	other threads:[~2006-12-08  1:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 12:56 [PATCH 0/14] ACPI: make ACPI use driver model Zhang Rui
2006-12-07 16:28 ` Bjorn Helgaas
2006-12-08  1:34   ` Shaohua Li [this message]
2006-12-08 10:29   ` Len Brown
2006-12-08 16:50     ` Bjorn Helgaas
2006-12-08 10:31 ` 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=1165541643.1369.2.camel@sli10-conroe.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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