From: "Yu, Luming" <luming.yu@intel.com>
To: "Matthew Wilcox" <matthew@wil.cx>
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
"ACPI-DEV" <acpi-devel@lists.sourceforge.net>,
"lkml" <linux-kernel@vger.kernel.org>,
"Brown, Len" <len.brown@intel.com>, "Greg" <greg@kroah.com>,
"Patrick Mochel" <mochel@digitalimplant.org>
Subject: RE: [ACPI] [PATCH/RFC 0/4]Bind physical devices with ACPI devices
Date: Tue, 9 Nov 2004 00:08:03 +0800 [thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F84041AC033@pdsmsx403> (raw)
>On Mon, Nov 08, 2004 at 10:46:30PM +0800, Yu, Luming wrote:
>> >All we need is an acpi_get_gendev_handle that takes a
>struct device and
>> >returns the acpi_handle for it. Now, maybe that'd be best
>> >done by placing
>> >a pointer in the struct device, but I bet it'd be just as
>good to walk
>> >the namespace looking for the corresponding device.
>>
>> It will fail if you just simply walk namespace to find out
>> the corresponding acpi object, because there are NO
>> hardware id or compatible id can be passed in.
>> Please check function acpi_bus_match.
>
>It doesn't need the HID or CID. Look at Shaohua's patches --
>they don't
>use HID or CID either.
>
Yes, I made a mistake, please forget that point.
But another statement I made should be valid.
That is how to use geographical address to
locate corresponding acpi object.
For example, ACPI define IDE as the following:
Device (IDE0){ /* primary controller */
Name (_ADR, 0)
Method (_GTM )
...
Device(PRIM) /* primary adapter */
Name (_ADR, 0)
Method(_GTM)
...
Device(MSTR) /* master channel */
Name (_ADR,0)
Method(_GTF)
We need not only able to locate acpi object IDE0
but also we need to locate object PRIM underneath
IDE0, and MSTR underneath PRIM. Thus, IDE driver
can fully take advantage from ACPI, in terms of
configuration and power management.
Maybe we need to invent a method called
map_device_addr_to_acpi_handle to be generic solution.
Thanks,
Luming
next reply other threads:[~2004-11-08 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 16:08 Yu, Luming [this message]
2004-11-08 16:38 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2004-11-08 14:46 Yu, Luming
2004-11-08 14:59 ` Matthew Wilcox
2004-11-08 4:11 Li Shaohua
2004-11-08 13:56 ` [ACPI] " Matthew Wilcox
2004-11-09 1:10 ` 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=3ACA40606221794F80A5670F0AF15F84041AC033@pdsmsx403 \
--to=luming.yu@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mochel@digitalimplant.org \
--cc=shaohua.li@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
all inboxes | Powered by JetHome®