Hi Alan, >> I also thought of that. This can be done... >> Just to make sure we're on the same page: >> We can add a "max_sup_speed" field to struct usb_composite_driver. Each >> of >> the Gadget drivers will set this field prior to calling >> usb_composite_probe(). Then, in usb_composite_probe(), we'll update the >> composite_driver.speed as follows: >> >> composite_driver.speed = min(composite_driver.speed, >> driver->max_sup_speed); > > Just call it max_speed. You can mention in the kerneldoc that it is > the maximum speed supported by the driver. No problem. I understand that you agree to this approach? I was going to wait for Felipe to comment but he'll be out of reach for several days so I'll post a new patch set on Sunday. Thanks for you help! Tanya Brokhman -- Sent by an consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the 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
