> > > > Actually if the CONFIG_USB_GADGET_SUPERSPEED is turned off, which is > the > > default of it, the speed won't be updated and all these series won't > be > > functional so I don't see any possibilities for failure in such > > configuration. Or am I missing something? > > dummy_hcd should work when CONFIG_USB_GADGET_SUPERSPEED is enabled, > even if the usb_gadget_driver structure is initialized with the speed > field set to USB_SPEED_HIGH. This will be true for all the standalone > gadget drivers until they are updated. It does. > > Which leaves a question about the composite gadget framework. Should > it be updated with SS support? Probably not until the various function > drivers have all been updated. As I mentioned, updating all of the gadget drivers will take a long time and I don't fill confident enough doing since I'm not familiar with all of them and don't have the ability to test each of them properly. I can add SS descriptors to f_mass_storage, g_zero if it helps and of course f_uasp already has them. I'm a bit confused by this actually... We've been discussing this patch series for quite a while now and I got the impression that except for some minor comments you were all for excepting this. Was I wrong or am I misunderstanding the above? In any case, I don't feel that adding SS support for the Gadget framework should be delayed until all gadget drivers add SS descriptors because this patch series will give the developers the ability to test these gadget drivers at SS. Also, several developers addressed me offline with questions on this series so I know people are using it in their work. And of course we do :) Best regards, Tanya Brokhman Consultant for Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum -- 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
