[lkml]   [2004]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ACPI] [PATCH/RFC 0/4]Bind physical devices with ACPI devices
On Tue, Nov 09, 2004 at 12:08:03AM +0800, Yu, Luming wrote:
> >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.
> 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.

I think we're saying the same thing in different words here ...

Note that an acpi_get_gendev_handle() or map_device_addr_to_acpi_handle()
function doesn't *preclude* putting a void * in struct device. It does
let us choose whether or not to do so.

"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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:07    [W:0.020 / U:1.220 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site