Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [ACPI] [PATCH/RFC 0/4]Bind physical devices with ACPI devices
Date: Mon, 8 Nov 2004 22:46:30 +0800
Message-ID: <3ACA40606221794F80A5670F0AF15F84041AC032@pdsmsx403>
Thread-Topic: [ACPI] [PATCH/RFC 0/4]Bind physical devices with ACPI devices
Thread-Index: AcTFmwaijU5vMXuPQD2CbZw4t8W1XAAA0btA
From: "Yu, Luming" <luming.yu@intel.com>
To: "Matthew Wilcox" <matthew@wil.cx>, "Li, Shaohua" <shaohua.li@intel.com>
Cc: "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>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 897
Lines: 26

>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.
  The fundamental problem here is how to use device's geographical
address( or other information ) to locate the corresponding 
acpi object in namespace.

Thanks,
Luming
 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/