> Yes, I'm still thinking about some missing init call.
I finally figured it out and we were right - to enable event reporting
via WMI, a WMI method call with a specially crafted buffer passed as an
argument is needed. (Though the SMI lead was correct as the WMI method
generates an SMI calling a BIOS function specified in the buffer
passed.)
I'll be happy to prepare a patch, though I'll appreciate some guidance
in two areas:
1) The GUID, buffer format and the function to use (DELL_APP_GUID,
struct app_wmi_args and dell_wmi_perform_query(), respectively) are
already defined in drivers/leds/dell-led.c. However, the call to be
made is obviously not related to LEDs, but rather to WMI hotkeys,
which are handled in drivers/platform/x86/dell-wmi.c. Also, the call
should only be made on a Vostro V131 and DMI-based filtering is done
in yet another file, drivers/platform/x86/dell-laptop.c. Where
should the fix be placed?
2) Pressing hotkey #3 on a Dell Vostro V131 generates WMI event 0xe025,
but no keycode. Apparently, Dell XPS L502X generates the same WMI
event for a hotkey which also generates a keycode [1]. What's the
best way to solve this conflict?
[1] commit f1566f0: "dell-wmi: Add keys for Dell XPS L502X"
--
Best regards,
Michał Kępień
--
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
