On Mon, Jan 14, 2008 at 10:25:10PM +0000, Carlos Corbacho wrote: > On Monday 14 January 2008 18:27:33 Carlos Corbacho wrote: > > On Monday 14 January 2008 17:41:07 Matthew Garrett wrote: > > > On Thu, Jan 03, 2008 at 11:58:02AM -0500, Dmitry Torokhov wrote: > > > > There is no sysfs device to attach the input device to, by any chance? > > > > > > Not as far as I can tell, but I may be misinterpreting this. Carlos? > > What would be better - to have WMI itself as the parent device, or should I > add something like this to WMI: > > wmi_get_dev(const char *guid, struct device *dev) > > to return the virtual device associated with a GUID, and then allow that to be > used as the parent? (trade off is that this driver would then become > dependent on the WMI sysfs patch going in as well, rather than just on the > in-kernel WMI support). > If there is a [planned] WMI sysfs device then I think input device should use it to form proper sysfs hierarchy. What are the roadblocks for getting WMI sysfs in? -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
