From: Lv Zheng <lv.zheng@intel.com>
To: Len Brown <len.brown@intel.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
linux-acpi@vger.kernel.org, Lv Zheng <lv.zheng@intel.com>
Subject: [PATCH v2 0/2] ACPI: Add userland visibility for identification objects.
Date: Fri, 28 Sep 2012 08:39:52 +0800 [thread overview]
Message-ID: <cover.1348791925.git.lv.zheng@intel.com> (raw)
In-Reply-To: <3f02ff942122d086c4d6e44a9ffa9269300675b3.1348736272.git.lv.zheng@intel.com>
There are four important device identification objects currently used in
the ACPI bus implementation:
_HID/_CID: traditional enumerated devicess use this object for ACPI device
matching.
_ADR: the ACPI device/physical device binding codes will use this to find
non-bridge devices.
_UID: the ACPI enumerated devices require this object to identify itself.
This patch set add the missing stuff useful for _UID in the ACPI devices.
Tow sysfs interfaces are also introduced to allow developers monitor _ADR
and _UID from the user space.
Version 2 of this patch set fixed CodingStyle issues. The two patches are
also combined to form a single patch set.
Lv Zheng (2):
ACPI: Add _UID support for ACPI devices.
ACPI: Add identification objects' user interface.
drivers/acpi/scan.c | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
--
1.7.10
next prev parent reply other threads:[~2012-09-28 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 1:17 [PATCH] ACPI: Add _UID support for ACPI devices Lv Zheng
2012-09-27 1:33 ` Zhang Rui
2012-09-27 1:40 ` [PATCH] ACPI: Add identification objects' user interface Lv Zheng
2012-09-27 1:45 ` Zhang Rui
2012-09-27 5:05 ` Zheng, Lv
2012-09-27 5:02 ` [RESEND PATCH] ACPI: Add _UID support for ACPI devices Lv Zheng
2012-09-28 0:39 ` Lv Zheng [this message]
2012-09-28 0:40 ` [PATCH v2 1/2] " Lv Zheng
2012-09-28 0:40 ` [PATCH v2 2/2] ACPI: Add identification objects' user interface Lv Zheng
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=cover.1348791925.git.lv.zheng@intel.com \
--to=lv.zheng@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mtk.manpages@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.