Lines Matching +full:peripheral +full:- +full:controller

3 #    (a) a peripheral controller, and
6 # NOTE:  Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
8 #  - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
9 #  - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
10 #  - Some systems have both kinds of controllers.
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).
20 	   host (such as a PC) controlling up to 127 peripheral devices.
22 	   you can't connect a "to-the-host" connector to a peripheral.
24 	   U-Boot can run in the host, or in the peripheral.  In both cases
25 	   you need a low level bus controller driver, and some software
26 	   talking to it.  Peripheral controllers are often discrete silicon,
32 	   Enable this configuration option if you want to run U-Boot inside
33 	   a USB peripheral device.  Configure one hardware driver for your
34 	   peripheral/device side bus controller, and a "gadget driver" for
35 	   your peripheral protocol.
43 	  CDC-ACM (usbtty) for example.
57 	default "U-Boot"
82 	  USBA is the integrated high-speed USB Device controller on
91 	bool "DesignWare USB2.0 HS OTG controller (gadget mode)"
94 	  The Designware USB2.0 high-speed gadget controller
96 	  driver to operate in Peripheral mode. This option requires
102 	bool "DesignWare USB2.0 HS OTG controller 8-bit PHY bus width"
104 	  Set the Designware USB2.0 high-speed OTG controller
110 	bool "ChipIdea device controller"
113 	  Say Y here to enable device controller functionality of the
117 	int "Maximum VBUS Power usage (2-500 mA)"
127 	   milliAmperes.  The permitted range of values is 2 - 500 mA;
130 	   This value will be used except for system-specific gadget
133 # Selected by UDC drivers that support high-speed operation.
148 	  Enable mass storage protocol support in U-Boot. It allows exporting
162 	  Enable Serial Download Protocol (SDP) device support in U-Boot. This
169 	  Enable Tizen's THOR download protocol support in U-Boot. It
179 	  Creates an Ethernet network device through a USB peripheral
180 	  controller. This will create a network interface on both the device
181 	  (U-Boot) and the host (remote device) that can be used just like any
183 	  It will bind on the peripheral USB controller, ignoring the USB hosts
193 	  devices. The main ones are Microsoft's RNDIS and USB's CDC-Ethernet
194 	  (also called CDC-ECM). RNDIS is obviously compatible with Windows,
195 	  while CDC-ECM is not. Most other operating systems support both, so
196 	  if inter-operability is a concern, RNDIS is to be preferred.
199 	bool "CDC-ECM Protocol"
220 	  Ethernet MAC address of the device-side (ie. local board's) MAC
227 	  Ethernet MAC address of the host-side (ie. remote device's) MAC