forked from ~ljy/RK356X_SDK_RELEASE
blame | history | patch | commit | commitdiff
hc
2023-12-11 072de836f53be56a70cecf70b43ae43b7ce17376 
 kernel/drivers/usb/Kconfig
....@@ -30,14 +30,13 @@
3030 	bool "USB support"
3131 	depends on HAS_IOMEM
3232 	default y
33
-	---help---
33
+	help
3434 	  This option adds core support for Universal Serial Bus (USB).
3535 	  You will also need drivers from the following menu to make use of it.
3636 
3737 if USB_SUPPORT
3838 
39
-config USB_COMMON
40
-	tristate
39
+source "drivers/usb/common/Kconfig"
4140 
4241 config USB_ARCH_HAS_HCD
4342 	def_bool y
....@@ -45,9 +44,10 @@
4544 config USB
4645 	tristate "Support for Host-side USB"
4746 	depends on USB_ARCH_HAS_HCD
47
+	select GENERIC_ALLOCATOR
4848 	select USB_COMMON
4949 	select NLS  # for UTF-8 strings
50
-	---help---
50
+	help
5151 	  Universal Serial Bus (USB) is a specification for a serial bus
5252 	  subsystem which offers higher speeds and more features than the
5353 	  traditional PC serial port.  The bus supplies power to peripherals
....@@ -74,7 +74,7 @@
7474 	  After choosing your HCD, then select drivers for the USB peripherals
7575 	  you'll be using.  You may want to check out the information provided
7676 	  in <file:Documentation/usb/> and especially the links given in
77
-	  <file:Documentation/usb/usb-help.txt>.
77
+	  <file:Documentation/usb/usb-help.rst>.
7878 
7979 	  To compile this driver as a module, choose M here: the
8080 	  module will be called usbcore.
....@@ -83,7 +83,7 @@
8383 	bool "PCI based USB host interface"
8484 	depends on PCI
8585 	default y
86
-	---help---
86
+	help
8787 	  Many embedded system SOCs (e.g. freescale T2080) have both
8888 	  PCI and USB modules with the USB module directly controlled by
8989 	  registers and having no relationship to the PCI module.
....@@ -96,8 +96,6 @@
9696 source "drivers/usb/core/Kconfig"
9797 
9898 source "drivers/usb/mon/Kconfig"
99
-
100
-source "drivers/usb/wusbcore/Kconfig"
10199 
102100 source "drivers/usb/host/Kconfig"
103101 
....@@ -112,6 +110,8 @@
112110 source "drivers/usb/usbip/Kconfig"
113111 
114112 endif
113
+
114
+source "drivers/usb/cdns3/Kconfig"
115115 
116116 source "drivers/usb/mtu3/Kconfig"
117117 
....@@ -133,7 +133,7 @@
133133 	tristate "USS720 parport driver"
134134 	depends on PARPORT
135135 	select PARPORT_NOT_PC
136
-	---help---
136
+	help
137137 	  This driver is for USB parallel port adapters that use the Lucent
138138 	  Technologies USS-720 chip. These cables are plugged into your USB
139139 	  port and provide USB compatibility to peripherals designed with
....@@ -173,36 +173,5 @@
173173 source "drivers/usb/typec/Kconfig"
174174 
175175 source "drivers/usb/roles/Kconfig"
176
-
177
-config USB_LED_TRIG
178
-	bool "USB LED Triggers"
179
-	depends on LEDS_CLASS && USB_COMMON && LEDS_TRIGGERS
180
-	help
181
-	  This option adds LED triggers for USB host and/or gadget activity.
182
-
183
-	  Say Y here if you are working on a system with led-class supported
184
-	  LEDs and you want to use them as activity indicators for USB host or
185
-	  gadget.
186
-
187
-config USB_ULPI_BUS
188
-	tristate "USB ULPI PHY interface support"
189
-	select USB_COMMON
190
-	help
191
-	  UTMI+ Low Pin Interface (ULPI) is specification for a commonly used
192
-	  USB 2.0 PHY interface. The ULPI specification defines a standard set
193
-	  of registers that can be used to detect the vendor and product which
194
-	  allows ULPI to be handled as a bus. This module is the driver for that
195
-	  bus.
196
-
197
-	  The ULPI interfaces (the buses) are registered by the drivers for USB
198
-	  controllers which support ULPI register access and have ULPI PHY
199
-	  attached to them. The ULPI PHY drivers themselves are normal PHY
200
-	  drivers.
201
-
202
-	  ULPI PHYs provide often functions such as ADP sensing/probing (OTG
203
-	  protocol) and USB charger detection.
204
-
205
-	  To compile this driver as a module, choose M here: the module will
206
-	  be called ulpi.
207176 
208177 endif # USB_SUPPORT