>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
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.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain