On Wed, 23 Apr 2014, Benjamin Tissoires wrote: > Currently, hid-rmi drives every Synaptics product, but the touchscreens > on the Windows tablets should be handled through hid-multitouch. > > Instead of providing a long list of PIDs, rely on the scan_report > capability to detect which should go to hid-multitouch, and which > should not go to hid-rmi. > > We introduce a generic HID_GROUP_HAVE_SPECIAL_DRIVER which can be reused > amoung other drivers if they want to have a catch rule but still > have multitouch devices handled through hid-multitouch. > > related bug: > https://bugzilla.kernel.org/show_bug.cgi?id=74241 > https://bugzilla.redhat.com/show_bug.cgi?id=1089583 > > Signed-off-by: Benjamin Tissoires <[email protected]>
Hi Benjamin, sorry for not responding sooner. Yes, I have to say I find HID_GROUP_HAVE_SPECIAL_DRIVER very disgusting. Especially its (non-)relation to hid_have_special_driver[] is very confusing. If you could update this to be RMI-specific (i.e. create a special HID_GROUP for RMI devices), I'll merge it right away. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
