In order to easily model that enabling CMD_USB_MASS_STORAGE implies a need to have USB_FUNCTION_MASS_STORAGE enabled, we first need to migrate USB_FUNCTION_MASS_STORAGE to Kconfig.
Signed-off-by: Philipp Tomsich philipp.tomsich@theobroma-systems.com
---
Changes in v2: - ran 'tabify' on newly added lines to fix a spaces vs. tabs issues
drivers/usb/gadget/Kconfig | 9 +++++++++ 1 file changed, 9 insertions(+)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconfig index 261ed12..8d1cd57 100644 --- a/drivers/usb/gadget/Kconfig +++ b/drivers/usb/gadget/Kconfig @@ -34,6 +34,15 @@ menuconfig USB_GADGET peripheral/device side bus controller, and a "gadget driver" for your peripheral protocol.
+config USB_FUNCTION_MASS_STORAGE + bool "USB mass-storage class implementation" + help + The Mass Storage Function acts as a USB Mass Storage device + appearing to the host as a disk drive or as a CD-ROM drive. + + This is required (and implied) by the USB mass-storage emulation + command ('ums'). + if USB_GADGET
config USB_GADGET_ATMEL_USBA