Gal Shalif <gal@xxxxxxxxxx> writes: > Bjoren> You can always unbind the driver, right? And usb_modeswitch will > even do it for you. > I'm not a USB mode switch expert, so please explain what is the mode switch > file that you suggest. > > As I already said before - my kernel configuration will not allow a USB > mode switch (to enterprise mode) without blacklisting the HID interface - > it may be because the HID driver is statically compile into my kernel. > > To summaries: > Without blacklisting - I cannot USB mode switch to USB730L enterprise mode > (product ID 9032). > With blacklisting - it is O.K. > > My kernel configuration: > iMX6 hardware > version 3.14.15 > ARM 32 bit > No IPV6 > Static compile if HID driver It doesn't matter if the driver is a module or built-in. You can still unbind it using the 'unbind' sysfs driver attribute. But I don't think a driver can prevent switching configurations. Please show us what happens when you write 3 to the bConfigurationValue attribute: echo 3 >/sys/bus/usb/devices/x-y/bConfigurationValue where x-y is the usb+port numbers. You can get them from e.g dmesg. And while you are at it: Please show the relevant parts of the dmesg output. lsusb -v output would also be nice to understand what part the HID driver plays here. If driver unbinding is really necessary, then I think you should test if a manual unbind will do. You may be right that some extra magic is needed. But I think it would be good to have a precise description of how that magic works, and not just "With blacklisting - it is O.K.". The hid blacklist connection does not make sense. Or at least it doesn't to me. Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
