From: Zhang Rui <rui.zhang@intel.com>
To: lenb@kernel.org
Cc: "linux-acpi@vger" <linux-acpi@vger.kernel.org>
Subject: [PATCH 0/14] ACPI: make ACPI use driver model
Date: Thu, 07 Dec 2006 20:56:10 +0800 [thread overview]
Message-ID: <1165496170.11485.74.camel@localhost.localdomain> (raw)
The main purpose of this patch series is to make ACPI use driver model
And these are updated patches against 2.6.19.
Patrick has posted patches on rewriting ACPI driver model in November 2005.
And recently Shaohua send me a prototype on making ACPI use driver model.
This patch series bases on both Patrick and Shaohua's previous work.
Two features are gonna be changed by applying this series of patches.
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.
2. ACPI sysfs interface.
As a result of using driver model, ACPI devices is added in the
/sys/device tree. So _EJ0 is added as a property of ACPI device
in device tree. ACPI namespace nodes that used to be shown
under /sys/firm/acpi is deleted.
The corresponding userspace script needs to be changed for
hot removal.
Note that this is only the first step of ACPI sysfs conversion work
The next step is to duplicate ACPI procfs functions in sysfs.
next reply other threads:[~2006-12-07 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 12:56 Zhang Rui [this message]
2006-12-07 16:28 ` [PATCH 0/14] ACPI: make ACPI use driver model Bjorn Helgaas
2006-12-08 1:34 ` Shaohua Li
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=1165496170.11485.74.camel@localhost.localdomain \
--to=rui.zhang@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.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