[mirror_ubuntu-zesty-kernel.git] / drivers / usb / gadget / Kconfig

#
# USB Gadget support on a system involves
#    (a) a peripheral controller, and
#    (b) the gadget driver using it.
#
# NOTE:  Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
#
#  - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
#  - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
#  - Some systems have both kinds of controllers.
#
# With help from a special transceiver and a "Mini-AB" jack, systems with
# both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
#

menuconfig USB_GADGET
	tristate "USB Gadget Support"
	select NLS
	help
	   USB is a master/slave protocol, organized with one master
	   host (such as a PC) controlling up to 127 peripheral devices.
	   The USB hardware is asymmetric, which makes it easier to set up:
	   you can't connect a "to-the-host" connector to a peripheral.

	   Linux can run in the host, or in the peripheral.  In both cases
	   you need a low level bus controller driver, and some software
	   talking to it.  Peripheral controllers are often discrete silicon,
	   or are integrated with the CPU in a microcontroller.  The more
	   familiar host side controllers have names like "EHCI", "OHCI",
	   or "UHCI", and are usually integrated into southbridges on PC
	   motherboards.

	   Enable this configuration option if you want to run Linux inside
	   a USB peripheral device.  Configure one hardware driver for your
	   peripheral/device side bus controller, and a "gadget driver" for
	   your peripheral protocol.  (If you use modular gadget drivers,
	   you may configure more than one.)

	   If in doubt, say "N" and don't enable these drivers; most people
	   don't have this kind of hardware (except maybe inside Linux PDAs).

	   For more information, see <http://www.linux-usb.org/gadget> and
	   the kernel DocBook documentation for this API.

if USB_GADGET

config USB_GADGET_DEBUG
	boolean "Debugging messages (DEVELOPMENT)"
	depends on DEBUG_KERNEL
	help
	   Many controller and gadget drivers will print some debugging
	   messages if you use this option to ask for those messages.

	   Avoid enabling these messages, even if you're actively
	   debugging such a driver.  Many drivers will emit so many
	   messages that the driver timings are affected, which will
	   either create new failure modes or remove the one you're
	   trying to track down.  Never enable these messages for a
	   production build.

config USB_GADGET_VERBOSE
	bool "Verbose debugging Messages (DEVELOPMENT)"
	depends on USB_GADGET_DEBUG
	help
	   Many controller and gadget drivers will print verbose debugging
	   messages if you use this option to ask for those messages.

	   Avoid enabling these messages, even if you're actively
	   debugging such a driver.  Many drivers will emit so many
	   messages that the driver timings are affected, which will
	   either create new failure modes or remove the one you're
	   trying to track down.  Never enable these messages for a
	   production build.

config USB_GADGET_DEBUG_FILES
	boolean "Debugging information files (DEVELOPMENT)"
	depends on PROC_FS
	help
	   Some of the drivers in the "gadget" framework can expose
	   debugging information in files such as /proc/driver/udc
	   (for a peripheral controller).  The information in these
	   files may help when you're troubleshooting or bringing up a
	   driver on a new board.   Enable these files by choosing "Y"
	   here.  If in doubt, or to conserve kernel memory, say "N".

config USB_GADGET_DEBUG_FS
	boolean "Debugging information files in debugfs (DEVELOPMENT)"
	depends on DEBUG_FS
	help
	   Some of the drivers in the "gadget" framework can expose
	   debugging information in files under /sys/kernel/debug/.
	   The information in these files may help when you're
	   troubleshooting or bringing up a driver on a new board.
	   Enable these files by choosing "Y" here.  If in doubt, or
	   to conserve kernel memory, say "N".

config USB_GADGET_VBUS_DRAW
	int "Maximum VBUS Power usage (2-500 mA)"
	range 2 500
	default 2
	help
	   Some devices need to draw power from USB when they are
	   configured, perhaps to operate circuitry or to recharge
	   batteries.  This is in addition to any local power supply,
	   such as an AC adapter or batteries.

	   Enter the maximum power your device draws through USB, in
	   milliAmperes.  The permitted range of values is 2 - 500 mA;
	   0 mA would be legal, but can make some hosts misbehave.

	   This value will be used except for system-specific gadget
	   drivers that have more specific information.

config USB_GADGET_STORAGE_NUM_BUFFERS
	int "Number of storage pipeline buffers"
	range 2 4
	default 2
	help
	   Usually 2 buffers are enough to establish a good buffering
	   pipeline. The number may be increased in order to compensate
	   for a bursty VFS behaviour. For instance there may be CPU wake up
	   latencies that makes the VFS to appear bursty in a system with
	   an CPU on-demand governor. Especially if DMA is doing IO to
	   offload the CPU. In this case the CPU will go into power
	   save often and spin up occasionally to move data within VFS.
	   If selecting USB_GADGET_DEBUG_FILES this value may be set by
	   a module parameter as well.
	   If unsure, say 2.

source "drivers/usb/gadget/udc/Kconfig"

#
# USB Gadget Drivers
#

# composite based drivers
config USB_LIBCOMPOSITE
	tristate
	select CONFIGFS_FS
	depends on USB_GADGET

config USB_F_ACM
	tristate

config USB_F_SS_LB
	tristate

config USB_U_SERIAL
	tristate

config USB_U_ETHER
	tristate

config USB_F_SERIAL
	tristate

config USB_F_OBEX
	tristate

config USB_F_NCM
	tristate

config USB_F_ECM
	tristate

config USB_F_PHONET
	tristate

config USB_F_EEM
	tristate

config USB_F_SUBSET
	tristate

config USB_F_RNDIS
	tristate

config USB_F_MASS_STORAGE
	tristate

config USB_F_FS
	tristate

config USB_F_UAC1
	tristate

config USB_F_UAC2
	tristate

choice
	tristate "USB Gadget Drivers"
	default USB_ETH
	help
	  A Linux "Gadget Driver" talks to the USB Peripheral Controller
	  driver through the abstract "gadget" API.  Some other operating
	  systems call these "client" drivers, of which "class drivers"
	  are a subset (implementing a USB device class specification).
	  A gadget driver implements one or more USB functions using
	  the peripheral hardware.

	  Gadget drivers are hardware-neutral, or "platform independent",
	  except that they sometimes must understand quirks or limitations
	  of the particular controllers they work with.  For example, when
	  a controller doesn't support alternate configurations or provide
	  enough of the right types of endpoints, the gadget driver might
	  not be able work with that controller, or might need to implement
	  a less common variant of a device class protocol.

# this first set of drivers all depend on bulk-capable hardware.

config USB_CONFIGFS
	tristate "USB functions configurable through configfs"
	select USB_LIBCOMPOSITE
	help
	  A Linux USB "gadget" can be set up through configfs.
	  If this is the case, the USB functions (which from the host's
	  perspective are seen as interfaces) and configurations are
	  specified simply by creating appropriate directories in configfs.
	  Associating functions with configurations is done by creating
	  appropriate symbolic links.
	  For more information see Documentation/usb/gadget_configfs.txt.

config USB_CONFIGFS_SERIAL
	boolean "Generic serial bulk in/out"
	depends on USB_CONFIGFS
	depends on TTY
	select USB_U_SERIAL
	select USB_F_SERIAL
	help
	  The function talks to the Linux-USB generic serial driver.

config USB_CONFIGFS_ACM
	boolean "Abstract Control Model (CDC ACM)"
	depends on USB_CONFIGFS
	depends on TTY
	select USB_U_SERIAL
	select USB_F_ACM
	help
	  ACM serial link.  This function can be used to interoperate with
	  MS-Windows hosts or with the Linux-USB "cdc-acm" driver.

config USB_CONFIGFS_OBEX
	boolean "Object Exchange Model (CDC OBEX)"
	depends on USB_CONFIGFS
	depends on TTY
	select USB_U_SERIAL
	select USB_F_OBEX
	help
	  You will need a user space OBEX server talking to /dev/ttyGS*,
	  since the kernel itself doesn't implement the OBEX protocol.

config USB_CONFIGFS_NCM
	boolean "Network Control Model (CDC NCM)"
	depends on USB_CONFIGFS
	depends on NET
	select USB_U_ETHER
	select USB_F_NCM
	help
	  NCM is an advanced protocol for Ethernet encapsulation, allows
	  grouping of several ethernet frames into one USB transfer and
	  different alignment possibilities.

config USB_CONFIGFS_ECM
	boolean "Ethernet Control Model (CDC ECM)"
	depends on USB_CONFIGFS
	depends on NET
	select USB_U_ETHER
	select USB_F_ECM
	help
	  The "Communication Device Class" (CDC) Ethernet Control Model.
	  That protocol is often avoided with pure Ethernet adapters, in
	  favor of simpler vendor-specific hardware, but is widely
	  supported by firmware for smart network devices.

config USB_CONFIGFS_ECM_SUBSET
	boolean "Ethernet Control Model (CDC ECM) subset"
	depends on USB_CONFIGFS
	depends on NET
	select USB_U_ETHER
	select USB_F_SUBSET
	help
	  On hardware that can't implement the full protocol,
	  a simple CDC subset is used, placing fewer demands on USB.

config USB_CONFIGFS_RNDIS
	bool "RNDIS"
	depends on USB_CONFIGFS
	depends on NET
	select USB_U_ETHER
	select USB_F_RNDIS
	help
	   Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
	   and Microsoft provides redistributable binary RNDIS drivers for
	   older versions of Windows.

	   To make MS-Windows work with this, use Documentation/usb/linux.inf
	   as the "driver info file".  For versions of MS-Windows older than
	   XP, you'll need to download drivers from Microsoft's website; a URL
	   is given in comments found in that info file.

config USB_CONFIGFS_EEM
	bool "Ethernet Emulation Model (EEM)"
	depends on USB_CONFIGFS
	depends on NET
	select USB_U_ETHER
	select USB_F_EEM
	help
	  CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
	  and therefore can be supported by more hardware.  Technically ECM and
	  EEM are designed for different applications.  The ECM model extends
	  the network interface to the target (e.g. a USB cable modem), and the
	  EEM model is for mobile devices to communicate with hosts using
	  ethernet over USB.  For Linux gadgets, however, the interface with
	  the host is the same (a usbX device), so the differences are minimal.

config USB_CONFIGFS_PHONET
	boolean "Phonet protocol"
	depends on USB_CONFIGFS
	depends on NET
	depends on PHONET
	select USB_U_ETHER
	select USB_F_PHONET
	help
	  The Phonet protocol implementation for USB device.

config USB_CONFIGFS_MASS_STORAGE
	boolean "Mass storage"
	depends on USB_CONFIGFS
	depends on BLOCK
	select USB_F_MASS_STORAGE
	help
	  The Mass Storage Gadget acts as a USB Mass Storage disk drive.
	  As its storage repository it can use a regular file or a block
	  device (in much the same way as the "loop" device driver),
	  specified as a module parameter or sysfs option.

config USB_CONFIGFS_F_LB_SS
	boolean "Loopback and sourcesink function (for testing)"
	depends on USB_CONFIGFS
	select USB_F_SS_LB
	help
	  Loopback function loops back a configurable number of transfers.
	  Sourcesink function either sinks and sources bulk data.
	  It also implements control requests, for "chapter 9" conformance.
	  Make this be the first driver you try using on top of any new
	  USB peripheral controller driver.  Then you can use host-side
	  test software, like the "usbtest" driver, to put your hardware
	  and its driver through a basic set of functional tests.

config USB_CONFIGFS_F_FS
	boolean "Function filesystem (FunctionFS)"
	depends on USB_CONFIGFS
	select USB_F_FS
	help
	  The Function Filesystem (FunctionFS) lets one create USB
	  composite functions in user space in the same way GadgetFS
	  lets one create USB gadgets in user space.  This allows creation
	  of composite gadgets such that some of the functions are
	  implemented in kernel space (for instance Ethernet, serial or
	  mass storage) and other are implemented in user space.

source "drivers/usb/gadget/legacy/Kconfig"

endchoice

endif # USB_GADGET
Commit	Line	Data
1da177e4 LT	1	#
	2	# USB Gadget support on a system involves
	3	# (a) a peripheral controller, and
	4	# (b) the gadget driver using it.
	5	#
	6	# NOTE: Gadget support DOES NOT depend on host-side CONFIG_USB !!
	7	#
	8	# - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
	9	# - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
cab00891	10	# - Some systems have both kinds of controllers.
1da177e4 LT	11	#
	12	# With help from a special transceiver and a "Mini-AB" jack, systems with
	13	# both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
	14	#
1da177e4	15
b75be4ab DC	16	menuconfig USB_GADGET
b75be4ab DC	17	tristate "USB Gadget Support"
86dc243c	18	select NLS
1da177e4 LT	19	help
	20	USB is a master/slave protocol, organized with one master
	21	host (such as a PC) controlling up to 127 peripheral devices.
	22	The USB hardware is asymmetric, which makes it easier to set up:
	23	you can't connect a "to-the-host" connector to a peripheral.
	24
	25	Linux can run in the host, or in the peripheral. In both cases
	26	you need a low level bus controller driver, and some software
	27	talking to it. Peripheral controllers are often discrete silicon,
	28	or are integrated with the CPU in a microcontroller. The more
e113f29c	29	familiar host side controllers have names like "EHCI", "OHCI",
1da177e4 LT	30	or "UHCI", and are usually integrated into southbridges on PC
	31	motherboards.
	32
	33	Enable this configuration option if you want to run Linux inside
	34	a USB peripheral device. Configure one hardware driver for your
	35	peripheral/device side bus controller, and a "gadget driver" for
	36	your peripheral protocol. (If you use modular gadget drivers,
	37	you may configure more than one.)
	38
	39	If in doubt, say "N" and don't enable these drivers; most people
	40	don't have this kind of hardware (except maybe inside Linux PDAs).
	41
	42	For more information, see <http://www.linux-usb.org/gadget> and
	43	the kernel DocBook documentation for this API.
	44
b75be4ab DC	45	if USB_GADGET
b75be4ab DC	46
70790f63	47	config USB_GADGET_DEBUG
afd0e0f2	48	boolean "Debugging messages (DEVELOPMENT)"
36e893d2	49	depends on DEBUG_KERNEL
70790f63 DB	50	help
	51	Many controller and gadget drivers will print some debugging
	52	messages if you use this option to ask for those messages.
	53
	54	Avoid enabling these messages, even if you're actively
	55	debugging such a driver. Many drivers will emit so many
cd108691 AL	56	messages that the driver timings are affected, which will
	57	either create new failure modes or remove the one you're
	58	trying to track down. Never enable these messages for a
	59	production build.
	60
	61	config USB_GADGET_VERBOSE
	62	bool "Verbose debugging Messages (DEVELOPMENT)"
	63	depends on USB_GADGET_DEBUG
	64	help
	65	Many controller and gadget drivers will print verbose debugging
	66	messages if you use this option to ask for those messages.
	67
	68	Avoid enabling these messages, even if you're actively
	69	debugging such a driver. Many drivers will emit so many
70790f63 DB	70	messages that the driver timings are affected, which will
	71	either create new failure modes or remove the one you're
	72	trying to track down. Never enable these messages for a
	73	production build.
	74
1da177e4	75	config USB_GADGET_DEBUG_FILES
afd0e0f2	76	boolean "Debugging information files (DEVELOPMENT)"
36e893d2	77	depends on PROC_FS
1da177e4 LT	78	help
	79	Some of the drivers in the "gadget" framework can expose
	80	debugging information in files such as /proc/driver/udc
	81	(for a peripheral controller). The information in these
	82	files may help when you're troubleshooting or bringing up a
	83	driver on a new board. Enable these files by choosing "Y"
	84	here. If in doubt, or to conserve kernel memory, say "N".
	85
914a3f3b	86	config USB_GADGET_DEBUG_FS
afd0e0f2	87	boolean "Debugging information files in debugfs (DEVELOPMENT)"
36e893d2	88	depends on DEBUG_FS
914a3f3b HS	89	help
	90	Some of the drivers in the "gadget" framework can expose
	91	debugging information in files under /sys/kernel/debug/.
	92	The information in these files may help when you're
	93	troubleshooting or bringing up a driver on a new board.
	94	Enable these files by choosing "Y" here. If in doubt, or
	95	to conserve kernel memory, say "N".
	96
36e893d2 DB	97	config USB_GADGET_VBUS_DRAW
	98	int "Maximum VBUS Power usage (2-500 mA)"
	99	range 2 500
	100	default 2
	101	help
	102	Some devices need to draw power from USB when they are
	103	configured, perhaps to operate circuitry or to recharge
	104	batteries. This is in addition to any local power supply,
	105	such as an AC adapter or batteries.
	106
	107	Enter the maximum power your device draws through USB, in
	108	milliAmperes. The permitted range of values is 2 - 500 mA;
	109	0 mA would be legal, but can make some hosts misbehave.
	110
	111	This value will be used except for system-specific gadget
	112	drivers that have more specific information.
	113
6532c7fd PF	114	config USB_GADGET_STORAGE_NUM_BUFFERS
	115	int "Number of storage pipeline buffers"
	116	range 2 4
	117	default 2
	118	help
	119	Usually 2 buffers are enough to establish a good buffering
	120	pipeline. The number may be increased in order to compensate
	121	for a bursty VFS behaviour. For instance there may be CPU wake up
	122	latencies that makes the VFS to appear bursty in a system with
	123	an CPU on-demand governor. Especially if DMA is doing IO to
	124	offload the CPU. In this case the CPU will go into power
	125	save often and spin up occasionally to move data within VFS.
	126	If selecting USB_GADGET_DEBUG_FILES this value may be set by
	127	a module parameter as well.
	128	If unsure, say 2.
	129
90fccb52	130	source "drivers/usb/gadget/udc/Kconfig"
1da177e4	131
1da177e4 LT	132	#
	133	# USB Gadget Drivers
	134	#
a84d9e53 SAS	135
	136	# composite based drivers
	137	config USB_LIBCOMPOSITE
	138	tristate
88af8bbe	139	select CONFIGFS_FS
a84d9e53 SAS	140	depends on USB_GADGET
a84d9e53 SAS	141
ff47f594 SAS	142	config USB_F_ACM
	143	tristate
	144
cf9a08ae SAS	145	config USB_F_SS_LB
	146	tristate
	147
3249ca22 SAS	148	config USB_U_SERIAL
	149	tristate
	150
f1a1823f AP	151	config USB_U_ETHER
	152	tristate
	153
60540ea2	154	config USB_F_SERIAL
3249ca22 SAS	155	tristate
3249ca22 SAS	156
1d8fc251 AP	157	config USB_F_OBEX
	158	tristate
	159
40d133d7 AP	160	config USB_F_NCM
	161	tristate
	162
fee562a6 AP	163	config USB_F_ECM
	164	tristate
	165
fcbdf12e AP	166	config USB_F_PHONET
	167	tristate
	168
b29002a1 AP	169	config USB_F_EEM
	170	tristate
	171
8cedba7c AP	172	config USB_F_SUBSET
	173	tristate
	174
f466c635 AP	175	config USB_F_RNDIS
	176	tristate
	177
e5eaa0dc AP	178	config USB_F_MASS_STORAGE
	179	tristate
	180
5920cda6 AP	181	config USB_F_FS
	182	tristate
	183
f3a3406b AP	184	config USB_F_UAC1
	185	tristate
	186
f8f93d24 AP	187	config USB_F_UAC2
	188	tristate
	189
1da177e4 LT	190	choice
1da177e4 LT	191	tristate "USB Gadget Drivers"
1da177e4 LT	192	default USB_ETH
	193	help
	194	A Linux "Gadget Driver" talks to the USB Peripheral Controller
	195	driver through the abstract "gadget" API. Some other operating
	196	systems call these "client" drivers, of which "class drivers"
	197	are a subset (implementing a USB device class specification).
	198	A gadget driver implements one or more USB functions using
	199	the peripheral hardware.
	200
	201	Gadget drivers are hardware-neutral, or "platform independent",
	202	except that they sometimes must understand quirks or limitations
	203	of the particular controllers they work with. For example, when
	204	a controller doesn't support alternate configurations or provide
	205	enough of the right types of endpoints, the gadget driver might
	206	not be able work with that controller, or might need to implement
	207	a less common variant of a device class protocol.
	208
	209	# this first set of drivers all depend on bulk-capable hardware.
	210
d1c02452 AP	211	config USB_CONFIGFS
	212	tristate "USB functions configurable through configfs"
	213	select USB_LIBCOMPOSITE
	214	help
	215	A Linux USB "gadget" can be set up through configfs.
	216	If this is the case, the USB functions (which from the host's
	217	perspective are seen as interfaces) and configurations are
	218	specified simply by creating appropriate directories in configfs.
	219	Associating functions with configurations is done by creating
	220	appropriate symbolic links.
9c1d6962	221	For more information see Documentation/usb/gadget_configfs.txt.
d1c02452 AP	222
	223	config USB_CONFIGFS_SERIAL
	224	boolean "Generic serial bulk in/out"
	225	depends on USB_CONFIGFS
	226	depends on TTY
	227	select USB_U_SERIAL
	228	select USB_F_SERIAL
	229	help
	230	The function talks to the Linux-USB generic serial driver.
	231
	232	config USB_CONFIGFS_ACM
	233	boolean "Abstract Control Model (CDC ACM)"
	234	depends on USB_CONFIGFS
	235	depends on TTY
	236	select USB_U_SERIAL
	237	select USB_F_ACM
	238	help
	239	ACM serial link. This function can be used to interoperate with
	240	MS-Windows hosts or with the Linux-USB "cdc-acm" driver.
	241
	242	config USB_CONFIGFS_OBEX
	243	boolean "Object Exchange Model (CDC OBEX)"
	244	depends on USB_CONFIGFS
	245	depends on TTY
	246	select USB_U_SERIAL
	247	select USB_F_OBEX
	248	help
	249	You will need a user space OBEX server talking to /dev/ttyGS*,
	250	since the kernel itself doesn't implement the OBEX protocol.
	251
	252	config USB_CONFIGFS_NCM
	253	boolean "Network Control Model (CDC NCM)"
	254	depends on USB_CONFIGFS
	255	depends on NET
	256	select USB_U_ETHER
	257	select USB_F_NCM
	258	help
	259	NCM is an advanced protocol for Ethernet encapsulation, allows
	260	grouping of several ethernet frames into one USB transfer and
	261	different alignment possibilities.
	262
	263	config USB_CONFIGFS_ECM
	264	boolean "Ethernet Control Model (CDC ECM)"
	265	depends on USB_CONFIGFS
	266	depends on NET
	267	select USB_U_ETHER
	268	select USB_F_ECM
	269	help
	270	The "Communication Device Class" (CDC) Ethernet Control Model.
	271	That protocol is often avoided with pure Ethernet adapters, in
	272	favor of simpler vendor-specific hardware, but is widely
	273	supported by firmware for smart network devices.
	274
02832e56 AP	275	config USB_CONFIGFS_ECM_SUBSET
	276	boolean "Ethernet Control Model (CDC ECM) subset"
	277	depends on USB_CONFIGFS
	278	depends on NET
	279	select USB_U_ETHER
	280	select USB_F_SUBSET
	281	help
	282	On hardware that can't implement the full protocol,
	283	a simple CDC subset is used, placing fewer demands on USB.
	284
b3df2faa AP	285	config USB_CONFIGFS_RNDIS
	286	bool "RNDIS"
	287	depends on USB_CONFIGFS
	288	depends on NET
	289	select USB_U_ETHER
	290	select USB_F_RNDIS
	291	help
	292	Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
	293	and Microsoft provides redistributable binary RNDIS drivers for
	294	older versions of Windows.
	295
	296	To make MS-Windows work with this, use Documentation/usb/linux.inf
	297	as the "driver info file". For versions of MS-Windows older than
	298	XP, you'll need to download drivers from Microsoft's website; a URL
	299	is given in comments found in that info file.
	300
17b80976 AP	301	config USB_CONFIGFS_EEM
	302	bool "Ethernet Emulation Model (EEM)"
	303	depends on USB_CONFIGFS
	304	depends on NET
	305	select USB_U_ETHER
	306	select USB_F_EEM
	307	help
	308	CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
	309	and therefore can be supported by more hardware. Technically ECM and
	310	EEM are designed for different applications. The ECM model extends
	311	the network interface to the target (e.g. a USB cable modem), and the
	312	EEM model is for mobile devices to communicate with hosts using
	313	ethernet over USB. For Linux gadgets, however, the interface with
	314	the host is the same (a usbX device), so the differences are minimal.
	315
83408745 AP	316	config USB_CONFIGFS_PHONET
	317	boolean "Phonet protocol"
	318	depends on USB_CONFIGFS
	319	depends on NET
	320	depends on PHONET
	321	select USB_U_ETHER
	322	select USB_F_PHONET
	323	help
	324	The Phonet protocol implementation for USB device.
	325
ef0aa4b9 AP	326	config USB_CONFIGFS_MASS_STORAGE
	327	boolean "Mass storage"
	328	depends on USB_CONFIGFS
bc912b0d	329	depends on BLOCK
ef0aa4b9 AP	330	select USB_F_MASS_STORAGE
	331	help
	332	The Mass Storage Gadget acts as a USB Mass Storage disk drive.
	333	As its storage repository it can use a regular file or a block
	334	device (in much the same way as the "loop" device driver),
	335	specified as a module parameter or sysfs option.
	336
25d80151 AP	337	config USB_CONFIGFS_F_LB_SS
25d80151 AP	338	boolean "Loopback and sourcesink function (for testing)"
c0501f47 AP	339	depends on USB_CONFIGFS
	340	select USB_F_SS_LB
	341	help
25d80151 AP	342	Loopback function loops back a configurable number of transfers.
25d80151 AP	343	Sourcesink function either sinks and sources bulk data.
c0501f47 AP	344	It also implements control requests, for "chapter 9" conformance.
	345	Make this be the first driver you try using on top of any new
	346	USB peripheral controller driver. Then you can use host-side
	347	test software, like the "usbtest" driver, to put your hardware
	348	and its driver through a basic set of functional tests.
	349
b658499f AP	350	config USB_CONFIGFS_F_FS
	351	boolean "Function filesystem (FunctionFS)"
	352	depends on USB_CONFIGFS
	353	select USB_F_FS
	354	help
	355	The Function Filesystem (FunctionFS) lets one create USB
	356	composite functions in user space in the same way GadgetFS
	357	lets one create USB gadgets in user space. This allows creation
	358	of composite gadgets such that some of the functions are
	359	implemented in kernel space (for instance Ethernet, serial or
	360	mass storage) and other are implemented in user space.
	361
8443f2d2	362	source "drivers/usb/gadget/legacy/Kconfig"
1da177e4 LT	363
	364	endchoice
	365
b75be4ab	366	endif # USB_GADGET