Hi everybody, the USB composite gadget framework currently handles EP0 control requests sent to endpoints (bRequestType[4..0] == USB_RECIP_ENDPOINT) down to the current configuration EP0 request handler. Composite drivers thus need to parse the request and call the appropriate function handlers, making functions not self- contained. It should be possible to maintain an association between functions and endpoints for each configuration, much like we already maintain an association between functions and interfaces. The composite EP0 request handler could then handle endpoint requests down to the appropriate function, falling back to the configuration-level handler if no endpoint matches. Is there anything I have overlooked that would prevent this change from working properly ? If nobody objects, I'll submit a patch. Regards, Laurent Pinchart -- 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