On Thu, 14 Nov 2019, Andrey Konovalov wrote: > > > As a general rule, gadget drivers don't go directly in > > > drivers/usb/gadget. raw.c counts as a legacy driver (because it's not > > > written to use the composite gadget framework), so it belongs in > > > drivers/usb/gadget/legacy. That's where the gadgetfs driver lives, for > > > example. > > > > Hi Alan! Sure, I'll move it to legacy/ in v2. Thanks! > > Hi Alan, > > Should I move CONFIG_USB_RAW_GADGET into legacy/Kconfig as well? AFAIU > this makes it impossible to turn on e.g. both GadgetFS and Raw Gadget > at the same time, since they both become options of the same choice. We can probably live with that. Not many people will want to build the Raw Gadget driver, and even fewer will want it together with gadgetfs. But if you want to keep the Kconfig option in the higher-level directory, that's probably okay. Alan Stern
