Hi Costa, please do not top post on this mailing list. Otherwise I am just ignoring your emails from the next time. > For your first comment, > Yes, we can just add device with .driver_info in btusb_table, not in blacklist_table. > > For your other comments, > As the device has 4 USB interfaces and interface 2 is for Bluetooth function. We need to bypass the IF state in btusb.c as follow: > if (intf->cur_altsetting->desc.bInterfaceNuber !=0) > return -ENODEV; > > So we use a composite_device_table matching mechanism and use forward jump to bypass the bInterfaceNumber check. > And other vendors also can add their composite device in the composite_device_table to bypass the check. And this can also be done via the .driver_info to select what interfaces to expect. So please get rid of the composite table. And post the content of /proc/bus/usb/devices so that I see how your enpoints do look like. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
