If the software is using usbdevice_fs, no, it can simply detach the kernel driver. If the software is using hidraw then this blacklist becomes the issue because even if you unload the special driver the generic HID driver won't load. Is there a mechanism in the HID subsystem for drivers to build on top of the generic one instead of replacing it? On Mon, Aug 3, 2015, 2:25 AM Jiri Kosina <jkosina@xxxxxxxx> wrote: > > On Sun, 2 Aug 2015, Reilly Grant wrote: > > > There is existing user space software (not just mine, also from the > > manufacturer) that does not use the special driver and instead uses hidraw > > or usbdevice_fs to control the device. LED class driver support for this > > device is useful but should be optional. > > Is there any problem for the userspace software to unbind the kernel > driver first? > > -- > Jiri Kosina > SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
