Re: [PATCH 1/4] wmi: add a pair of interfaces to set/get wmi driver data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Apr 09, 2010 at 08:11:07PM +0100, Carlos Corbacho wrote:
> On Friday 09 April 2010 18:49:02 Dmitry Torokhov wrote:
> > On Fri, Apr 09, 2010 at 11:03:20PM +0800, Yong Wang wrote:
> > > Currently there is no easy way to associate driver data kind of thing
> > > with wmi drivers thus global variables have to be used to pass that
> > > information between functions. Add a pair of functions to support
> > > that.
> 
> NAK
> 
> > It looks like once you compete the conversion and have platform device
> > you can attach to it instead of needing driver data in WMI.
> > 
> 

The problem is that how can I retrieve the pointer to the platform device
itself in eeepc_wmi_exit to platform_device_unregister it? Is there any
other way to do it without having to define the platform device as
global variable?

> I'm with Dmitry on this one. Please avoid adding this kind of stuff to WMI - 
> it's just intended to be a thin wrapper around ACPI calls, not a full driver 
> class with its' own mechanisms for data storage, etc.
> 

Thanks for your comments, Carlos. Do you have any suggestions about how
to do that?

Thanks
-Yong

--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux