rjw | 1f88458 | 2022-01-06 17:20:42 +0800 | [diff] [blame^] | 1 | # |
| 2 | # USB device configuration |
| 3 | # |
| 4 | |
| 5 | config USB_OHCI_BIG_ENDIAN_DESC |
| 6 | bool |
| 7 | |
| 8 | config USB_OHCI_BIG_ENDIAN_MMIO |
| 9 | bool |
| 10 | |
| 11 | config USB_OHCI_LITTLE_ENDIAN |
| 12 | bool |
| 13 | default n if STB03xxx || PPC_MPC52xx |
| 14 | default y |
| 15 | |
| 16 | config USB_EHCI_BIG_ENDIAN_MMIO |
| 17 | bool |
| 18 | |
| 19 | config USB_EHCI_BIG_ENDIAN_DESC |
| 20 | bool |
| 21 | |
| 22 | config USB_UHCI_BIG_ENDIAN_MMIO |
| 23 | bool |
| 24 | default y if SPARC_LEON |
| 25 | |
| 26 | config USB_UHCI_BIG_ENDIAN_DESC |
| 27 | bool |
| 28 | default y if SPARC_LEON |
| 29 | |
| 30 | menuconfig USB_SUPPORT |
| 31 | bool "USB support" |
| 32 | depends on HAS_IOMEM |
| 33 | default y |
| 34 | ---help--- |
| 35 | This option adds core support for Universal Serial Bus (USB). |
| 36 | You will also need drivers from the following menu to make use of it. |
| 37 | |
| 38 | if USB_SUPPORT |
| 39 | |
| 40 | config USB_COMMON |
| 41 | tristate |
| 42 | |
| 43 | config USB_ARCH_HAS_HCD |
| 44 | def_bool y |
| 45 | |
| 46 | config USB |
| 47 | tristate "Support for Host-side USB" |
| 48 | depends on USB_ARCH_HAS_HCD |
| 49 | select USB_COMMON |
| 50 | select NLS # for UTF-8 strings |
| 51 | ---help--- |
| 52 | Universal Serial Bus (USB) is a specification for a serial bus |
| 53 | subsystem which offers higher speeds and more features than the |
| 54 | traditional PC serial port. The bus supplies power to peripherals |
| 55 | and allows for hot swapping. Up to 127 USB peripherals can be |
| 56 | connected to a single USB host in a tree structure. |
| 57 | |
| 58 | The USB host is the root of the tree, the peripherals are the |
| 59 | leaves and the inner nodes are special USB devices called hubs. |
| 60 | Most PCs now have USB host ports, used to connect peripherals |
| 61 | such as scanners, keyboards, mice, modems, cameras, disks, |
| 62 | flash memory, network links, and printers to the PC. |
| 63 | |
| 64 | Say Y here if your computer has a host-side USB port and you want |
| 65 | to use USB devices. You then need to say Y to at least one of the |
| 66 | Host Controller Driver (HCD) options below. Choose a USB 1.1 |
| 67 | controller, such as "UHCI HCD support" or "OHCI HCD support", |
| 68 | and "EHCI HCD (USB 2.0) support" except for older systems that |
| 69 | do not have USB 2.0 support. It doesn't normally hurt to select |
| 70 | them all if you are not certain. |
| 71 | |
| 72 | If your system has a device-side USB port, used in the peripheral |
| 73 | side of the USB protocol, see the "USB Gadget" framework instead. |
| 74 | |
| 75 | After choosing your HCD, then select drivers for the USB peripherals |
| 76 | you'll be using. You may want to check out the information provided |
| 77 | in <file:Documentation/usb/> and especially the links given in |
| 78 | <file:Documentation/usb/usb-help.txt>. |
| 79 | |
| 80 | To compile this driver as a module, choose M here: the |
| 81 | module will be called usbcore. |
| 82 | |
| 83 | config USB_PCI |
| 84 | bool "PCI based USB host interface" |
| 85 | depends on PCI |
| 86 | default y |
| 87 | ---help--- |
| 88 | A lot of embeded system SOC (e.g. freescale T2080) have both |
| 89 | PCI and USB modules. But USB module is controlled by registers |
| 90 | directly, it have no relationship with PCI module. |
| 91 | |
| 92 | When say N here it will not build PCI related code in USB driver. |
| 93 | |
| 94 | if USB |
| 95 | |
| 96 | source "drivers/usb/core/Kconfig" |
| 97 | |
| 98 | source "drivers/usb/mon/Kconfig" |
| 99 | |
| 100 | source "drivers/usb/wusbcore/Kconfig" |
| 101 | |
| 102 | source "drivers/usb/host/Kconfig" |
| 103 | |
| 104 | source "drivers/usb/renesas_usbhs/Kconfig" |
| 105 | |
| 106 | source "drivers/usb/class/Kconfig" |
| 107 | |
| 108 | source "drivers/usb/storage/Kconfig" |
| 109 | |
| 110 | source "drivers/usb/image/Kconfig" |
| 111 | |
| 112 | source "drivers/usb/usbip/Kconfig" |
| 113 | |
| 114 | endif |
| 115 | |
| 116 | source "drivers/usb/mtu3/Kconfig" |
| 117 | |
| 118 | source "drivers/usb/musb/Kconfig" |
| 119 | |
| 120 | source "drivers/usb/dwc3/Kconfig" |
| 121 | |
| 122 | source "drivers/usb/dwc2/Kconfig" |
| 123 | |
| 124 | source "drivers/usb/chipidea/Kconfig" |
| 125 | |
| 126 | source "drivers/usb/isp1760/Kconfig" |
| 127 | |
| 128 | comment "USB port drivers" |
| 129 | |
| 130 | if USB |
| 131 | |
| 132 | config USB_USS720 |
| 133 | tristate "USS720 parport driver" |
| 134 | depends on PARPORT |
| 135 | select PARPORT_NOT_PC |
| 136 | ---help--- |
| 137 | This driver is for USB parallel port adapters that use the Lucent |
| 138 | Technologies USS-720 chip. These cables are plugged into your USB |
| 139 | port and provide USB compatibility to peripherals designed with |
| 140 | parallel port interfaces. |
| 141 | |
| 142 | The chip has two modes: automatic mode and manual mode. In automatic |
| 143 | mode, it looks to the computer like a standard USB printer. Only |
| 144 | printers may be connected to the USS-720 in this mode. The generic |
| 145 | USB printer driver ("USB Printer support", above) may be used in |
| 146 | that mode, and you can say N here if you want to use the chip only |
| 147 | in this mode. |
| 148 | |
| 149 | Manual mode is not limited to printers, any parallel port |
| 150 | device should work. This driver utilizes manual mode. |
| 151 | Note however that some operations are three orders of magnitude |
| 152 | slower than on a PCI/ISA Parallel Port, so timing critical |
| 153 | applications might not work. |
| 154 | |
| 155 | Say Y here if you own an USS-720 USB->Parport cable and intend to |
| 156 | connect anything other than a printer to it. |
| 157 | |
| 158 | To compile this driver as a module, choose M here: the |
| 159 | module will be called uss720. |
| 160 | |
| 161 | source "drivers/usb/serial/Kconfig" |
| 162 | |
| 163 | source "drivers/usb/misc/Kconfig" |
| 164 | |
| 165 | source "drivers/usb/atm/Kconfig" |
| 166 | |
| 167 | endif # USB |
| 168 | |
| 169 | source "drivers/usb/phy/Kconfig" |
| 170 | |
| 171 | source "drivers/usb/gadget/Kconfig" |
| 172 | |
| 173 | source "drivers/usb/typec/Kconfig" |
| 174 | |
| 175 | config USB_LED_TRIG |
| 176 | bool "USB LED Triggers" |
| 177 | depends on LEDS_CLASS && LEDS_TRIGGERS |
| 178 | select USB_COMMON |
| 179 | help |
| 180 | This option adds LED triggers for USB host and/or gadget activity. |
| 181 | |
| 182 | Say Y here if you are working on a system with led-class supported |
| 183 | LEDs and you want to use them as activity indicators for USB host or |
| 184 | gadget. |
| 185 | |
| 186 | config USB_ULPI_BUS |
| 187 | tristate "USB ULPI PHY interface support" |
| 188 | select USB_COMMON |
| 189 | help |
| 190 | UTMI+ Low Pin Interface (ULPI) is specification for a commonly used |
| 191 | USB 2.0 PHY interface. The ULPI specification defines a standard set |
| 192 | of registers that can be used to detect the vendor and product which |
| 193 | allows ULPI to be handled as a bus. This module is the driver for that |
| 194 | bus. |
| 195 | |
| 196 | The ULPI interfaces (the buses) are registered by the drivers for USB |
| 197 | controllers which support ULPI register access and have ULPI PHY |
| 198 | attached to them. The ULPI PHY drivers themselves are normal PHY |
| 199 | drivers. |
| 200 | |
| 201 | ULPI PHYs provide often functions such as ADP sensing/probing (OTG |
| 202 | protocol) and USB charger detection. |
| 203 | |
| 204 | To compile this driver as a module, choose M here: the module will |
| 205 | be called ulpi. |
| 206 | |
| 207 | endif # USB_SUPPORT |