cachepc-linux

Fork of AMDESE/linux with modifications for CachePC side-channel attack
git clone https://git.sinitax.com/sinitax/cachepc-linux
Log | Files | Refs | README | LICENSE | sfeed.txt

Kconfig (6793B)


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