Hi folks, here's a second RFC on my original endpoint feature flag RFC. I have kept the boolean flags even though Michael suggested using a single "supported_transfer_types" bitfield. I did that for a reason which I considered to be quite valid. Recent USB3.0 cores are starting to ship with built-in Trace capability. While that's not a USB-IF specified standard, we still must support such devices. Examples are Texas Instruments' OMAP5 and DRA7xx which come with an internal Trace Buffer. I also know of some Intel devices shipping with the same sort of trace capability. The problem faced there, is that *NOT* *ALL* endpoints are able to acceess such trace buffer. Needless to say we will need another feature flag "has_trace" which will tell epautoconf how to choose such endpoints. I still don't know how the gadget driver will make sure to tell epautoconf that it needs a trace-capable endpoint, however. We shall see, for now, let's keep boolean feature flags and figure out how to handle trace buffer later. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! !! !! COMPILE TESTED ONLY FOLLOWS, USE AT YOUR OWN RISK !! !! !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Felipe Balbi (4): usb: gadget: epautoconf: switch over to usb_endpoint_type() usb: gadget: ep: add feature flags usb: gadget: epautoconf: check feature flags usb: dwc3: gadget: set endpoint feature flags drivers/usb/dwc3/gadget.c | 19 +++++++++++++++++++ drivers/usb/gadget/epautoconf.c | 30 +++++++++++++++++++++++++++--- include/linux/usb/gadget.h | 13 +++++++++++++ 3 files changed, 59 insertions(+), 3 deletions(-) -- 1.8.4.1.559.gdb9bdfb -- 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
