| 1 | # SPDX-License-Identifier: GPL-2.0 |
| 2 | # |
| 3 | # USB Storage driver configuration |
| 4 | # |
| 5 | |
| 6 | comment "NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed; see USB_STORAGE Help for more info" |
| 7 | |
| 8 | config USB_STORAGE |
| 9 | tristate "USB Mass Storage support" |
| 10 | depends on SCSI |
| 11 | help |
| 12 | Say Y here if you want to connect USB mass storage devices to your |
| 13 | computer's USB port. This is the driver you need for USB |
| 14 | floppy drives, USB hard disks, USB tape drives, USB CD-ROMs, |
| 15 | USB flash devices, and memory sticks, along with |
| 16 | similar devices. This driver may also be used for some cameras |
| 17 | and card readers. |
| 18 | |
| 19 | This option depends on 'SCSI' support being enabled, but you |
| 20 | probably also need 'SCSI device support: SCSI disk support' |
| 21 | (BLK_DEV_SD) for most USB storage devices. |
| 22 | |
| 23 | To compile this driver as a module, choose M here: the |
| 24 | module will be called usb-storage. |
| 25 | |
| 26 | if USB_STORAGE |
| 27 | |
| 28 | config USB_STORAGE_DEBUG |
| 29 | bool "USB Mass Storage verbose debug" |
| 30 | help |
| 31 | Say Y here in order to have the USB Mass Storage code generate |
| 32 | verbose debugging messages. |
| 33 | |
| 34 | config USB_STORAGE_REALTEK |
| 35 | tristate "Realtek Card Reader support" |
| 36 | help |
| 37 | Say Y here to include additional code to support the power-saving function |
| 38 | for Realtek RTS51xx USB card readers. |
| 39 | |
| 40 | If this driver is compiled as a module, it will be named ums-realtek. |
| 41 | |
| 42 | config REALTEK_AUTOPM |
| 43 | bool "Realtek Card Reader autosuspend support" |
| 44 | depends on USB_STORAGE_REALTEK && PM |
| 45 | default y |
| 46 | |
| 47 | config USB_STORAGE_DATAFAB |
| 48 | tristate "Datafab Compact Flash Reader support" |
| 49 | help |
| 50 | Support for certain Datafab CompactFlash readers. |
| 51 | Datafab has a web page at <http://www.datafab.com/>. |
| 52 | |
| 53 | If this driver is compiled as a module, it will be named ums-datafab. |
| 54 | |
| 55 | config USB_STORAGE_FREECOM |
| 56 | tristate "Freecom USB/ATAPI Bridge support" |
| 57 | help |
| 58 | Support for the Freecom USB to IDE/ATAPI adaptor. |
| 59 | Freecom has a web page at <https://www.freecom.de/>. |
| 60 | |
| 61 | If this driver is compiled as a module, it will be named ums-freecom. |
| 62 | |
| 63 | config USB_STORAGE_ISD200 |
| 64 | tristate "ISD-200 USB/ATA Bridge support" |
| 65 | help |
| 66 | Say Y here if you want to use USB Mass Store devices based |
| 67 | on the In-Systems Design ISD-200 USB/ATA bridge. |
| 68 | |
| 69 | Some of the products that use this chip are: |
| 70 | |
| 71 | - Archos Jukebox 6000 |
| 72 | - ISD SmartCable for Storage |
| 73 | - Taiwan Skymaster CD530U/DEL-0241 IDE bridge |
| 74 | - Sony CRX10U CD-R/RW drive |
| 75 | - CyQ've CQ8060A CDRW drive |
| 76 | - Planex eXtreme Drive RX-25HU USB-IDE cable (not model RX-25U) |
| 77 | |
| 78 | If this driver is compiled as a module, it will be named ums-isd200. |
| 79 | |
| 80 | config USB_STORAGE_USBAT |
| 81 | tristate "USBAT/USBAT02-based storage support" |
| 82 | help |
| 83 | Say Y here to include additional code to support storage devices |
| 84 | based on the SCM/Shuttle USBAT/USBAT02 processors. |
| 85 | |
| 86 | Devices reported to work with this driver include: |
| 87 | - CompactFlash reader included with Kodak DC3800 camera |
| 88 | - Dane-Elec Zmate CompactFlash reader |
| 89 | - Delkin Efilm reader2 |
| 90 | - HP 8200e/8210e/8230e CD-Writer Plus drives |
| 91 | - I-JAM JS-50U |
| 92 | - Jessops CompactFlash JESDCFRU BLACK |
| 93 | - Kingston Technology PCREAD-USB/CF |
| 94 | - Maxell UA4 CompactFlash reader |
| 95 | - Memorex UCF-100 |
| 96 | - Microtech ZiO! ICS-45 CF2 |
| 97 | - RCA LYRA MP3 portable |
| 98 | - Sandisk ImageMate SDDR-05b |
| 99 | |
| 100 | If this driver is compiled as a module, it will be named ums-usbat. |
| 101 | |
| 102 | config USB_STORAGE_SDDR09 |
| 103 | tristate "SanDisk SDDR-09 (and other SmartMedia, including DPCM) support" |
| 104 | help |
| 105 | Say Y here to include additional code to support the Sandisk SDDR-09 |
| 106 | SmartMedia reader in the USB Mass Storage driver. |
| 107 | Also works for the Microtech Zio! CompactFlash/SmartMedia reader. |
| 108 | |
| 109 | If this driver is compiled as a module, it will be named ums-sddr09. |
| 110 | |
| 111 | config USB_STORAGE_SDDR55 |
| 112 | tristate "SanDisk SDDR-55 SmartMedia support" |
| 113 | help |
| 114 | Say Y here to include additional code to support the Sandisk SDDR-55 |
| 115 | SmartMedia reader in the USB Mass Storage driver. |
| 116 | |
| 117 | If this driver is compiled as a module, it will be named ums-sddr55. |
| 118 | |
| 119 | config USB_STORAGE_JUMPSHOT |
| 120 | tristate "Lexar Jumpshot Compact Flash Reader" |
| 121 | help |
| 122 | Say Y here to include additional code to support the Lexar Jumpshot |
| 123 | USB CompactFlash reader. |
| 124 | |
| 125 | If this driver is compiled as a module, it will be named ums-jumpshot. |
| 126 | |
| 127 | config USB_STORAGE_ALAUDA |
| 128 | tristate "Olympus MAUSB-10/Fuji DPC-R1 support" |
| 129 | help |
| 130 | Say Y here to include additional code to support the Olympus MAUSB-10 |
| 131 | and Fujifilm DPC-R1 USB Card reader/writer devices. |
| 132 | |
| 133 | These devices are based on the Alauda chip and support both |
| 134 | XD and SmartMedia cards. |
| 135 | |
| 136 | If this driver is compiled as a module, it will be named ums-alauda. |
| 137 | |
| 138 | config USB_STORAGE_ONETOUCH |
| 139 | tristate "Support OneTouch Button on Maxtor Hard Drives" |
| 140 | depends on INPUT=y || INPUT=USB_STORAGE |
| 141 | help |
| 142 | Say Y here to include additional code to support the Maxtor OneTouch |
| 143 | USB hard drive's onetouch button. |
| 144 | |
| 145 | This code registers the button on the front of Maxtor OneTouch USB |
| 146 | hard drive's as an input device. An action can be associated with |
| 147 | this input in any keybinding software. (e.g. gnome's keyboard short- |
| 148 | cuts) |
| 149 | |
| 150 | If this driver is compiled as a module, it will be named ums-onetouch. |
| 151 | |
| 152 | config USB_STORAGE_KARMA |
| 153 | tristate "Support for Rio Karma music player" |
| 154 | help |
| 155 | Say Y here to include additional code to support the Rio Karma |
| 156 | USB interface. |
| 157 | |
| 158 | This code places the Rio Karma into mass storage mode, enabling |
| 159 | it to be mounted as an ordinary filesystem. Performing an eject |
| 160 | on the resulting scsi device node returns the Karma to normal |
| 161 | operation. |
| 162 | |
| 163 | If this driver is compiled as a module, it will be named ums-karma. |
| 164 | |
| 165 | config USB_STORAGE_CYPRESS_ATACB |
| 166 | tristate "SAT emulation on Cypress USB/ATA Bridge with ATACB" |
| 167 | help |
| 168 | Say Y here if you want to use SAT (ata pass through) on devices based |
| 169 | on the Cypress USB/ATA bridge supporting ATACB. This will allow you |
| 170 | to use tools to tune and monitor your drive (like hdparm or smartctl). |
| 171 | |
| 172 | If you say no here your device will still work with the standard usb |
| 173 | mass storage class. |
| 174 | |
| 175 | If this driver is compiled as a module, it will be named ums-cypress. |
| 176 | |
| 177 | config USB_STORAGE_ENE_UB6250 |
| 178 | tristate "USB ENE card reader support" |
| 179 | help |
| 180 | Say Y here if you wish to control a ENE SD/MS Card reader. |
| 181 | Note that this driver does not support SM cards. |
| 182 | |
| 183 | To compile this driver as a module, choose M here: the |
| 184 | module will be called ums-eneub6250. |
| 185 | |
| 186 | endif # USB_STORAGE |
| 187 | |
| 188 | config USB_UAS |
| 189 | tristate "USB Attached SCSI" |
| 190 | depends on SCSI && USB_STORAGE |
| 191 | help |
| 192 | The USB Attached SCSI protocol is supported by some USB |
| 193 | storage devices. It permits higher performance by supporting |
| 194 | multiple outstanding commands. |
| 195 | |
| 196 | If you don't know whether you have a UAS device, it is safe to |
| 197 | say 'Y' or 'M' here and the kernel will use the right driver. |
| 198 | |
| 199 | If you compile this driver as a module, it will be named uas. |