1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "SCSI device support"
3 
4 config SCSI_MOD
5 	tristate
6 	default y if SCSI=n || SCSI=y
7 	default m if SCSI=m
8 	depends on BLOCK
9 
10 config RAID_ATTRS
11 	tristate "RAID Transport Class"
12 	default n
13 	depends on BLOCK
14 	depends on SCSI_MOD
15 	help
16 	  Provides RAID
17 
18 config SCSI_COMMON
19 	tristate
20 
21 config SCSI
22 	tristate "SCSI device support"
23 	depends on BLOCK
24 	select SCSI_DMA if HAS_DMA
25 	select SG_POOL
26 	select SCSI_COMMON
27 	select BLK_DEV_BSG_COMMON if BLK_DEV_BSG
28 	help
29 	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
30 	  any other SCSI device under Linux, say Y and make sure that you know
31 	  the name of your SCSI host adapter (the card inside your computer
32 	  that "speaks" the SCSI protocol, also called SCSI controller),
33 	  because you will be asked for it.
34 
35 	  You also need to say Y here if you have a device which speaks
36 	  the SCSI protocol.  Examples of this include the parallel port
37 	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
38 	  Channel, and FireWire storage.
39 
40 	  To compile this driver as a module, choose M here and read
41 	  <file:Documentation/scsi/scsi.rst>.
42 	  The module will be called scsi_mod.
43 
44 	  However, do not compile this as a module if your root file system
45 	  (the one containing the directory /) is located on a SCSI device.
46 
47 config SCSI_DMA
48 	bool
49 	default n
50 
51 config SCSI_ESP_PIO
52 	bool
53 
54 config SCSI_NETLINK
55 	bool
56 	default n
57 	depends on NET
58 
59 config SCSI_PROC_FS
60 	bool "legacy /proc/scsi/ support"
61 	depends on SCSI && PROC_FS
62 	default y
63 	help
64 	  This option enables support for the various files in
65 	  /proc/scsi.  In Linux 2.6 this has been superseded by
66 	  files in sysfs but many legacy applications rely on this.
67 
68 	  If unsure say Y.
69 
70 config SCSI_LIB_KUNIT_TEST
71 	tristate "KUnit tests for SCSI Mid Layer's scsi_lib" if !KUNIT_ALL_TESTS
72 	depends on KUNIT
73 	default KUNIT_ALL_TESTS
74 	help
75 	  Run SCSI Mid Layer's KUnit tests for scsi_lib.
76 
77 	  If unsure say N.
78 
79 comment "SCSI support type (disk, tape, CD-ROM)"
80 	depends on SCSI
81 
82 config BLK_DEV_SD
83 	tristate "SCSI disk support"
84 	depends on SCSI
85 	help
86 	  If you want to use SCSI hard disks, Fibre Channel disks,
87 	  Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
88 	  USB storage or the SCSI or parallel port version of
89 	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
90 	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from
91 	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
92 	  CD-ROMs.
93 
94 	  To compile this driver as a module, choose M here and read
95 	  <file:Documentation/scsi/scsi.rst>.
96 	  The module will be called sd_mod.
97 
98 	  Do not compile this driver as a module if your root file system
99 	  (the one containing the directory /) is located on a SCSI disk.
100 	  In this case, do not compile the driver for your SCSI host adapter
101 	  (below) as a module either.
102 
103 config CHR_DEV_ST
104 	tristate "SCSI tape support"
105 	depends on SCSI
106 	help
107 	  If you want to use a SCSI tape drive under Linux, say Y and read the
108 	  SCSI-HOWTO, available from
109 	  <http://www.tldp.org/docs.html#howto>, and
110 	  <file:Documentation/scsi/st.rst> in the kernel source.  This is NOT
111 	  for SCSI CD-ROMs.
112 
113 	  To compile this driver as a module, choose M here and read
114 	  <file:Documentation/scsi/scsi.rst>. The module will be called st.
115 
116 config BLK_DEV_SR
117 	tristate "SCSI CDROM support"
118 	depends on SCSI && BLK_DEV
119 	select CDROM
120 	help
121 	  If you want to use a CD or DVD drive attached to your computer
122 	  by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
123 	  and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
124 
125 	  Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
126 
127 	  To compile this driver as a module, choose M here and read
128 	  <file:Documentation/scsi/scsi.rst>.
129 	  The module will be called sr_mod.
130 
131 config CHR_DEV_SG
132 	tristate "SCSI generic support"
133 	depends on SCSI
134 	help
135 	  If you want to use SCSI scanners, synthesizers or CD-writers or just
136 	  about anything having "SCSI" in its name other than hard disks,
137 	  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
138 	  directly, so you need some additional software which knows how to
139 	  talk to these devices using the SCSI protocol:
140 
141 	  For scanners, look at SANE (<http://www.sane-project.org/>). For CD
142 	  writer software look at Cdrtools
143 	  (<http://cdrtools.sourceforge.net/>)
144 	  and for burning a "disk at once": CDRDAO
145 	  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
146 	  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
147 	  For other devices, it's possible that you'll have to write the
148 	  driver software yourself. Please read the file
149 	  <file:Documentation/scsi/scsi-generic.rst> for more information.
150 
151 	  To compile this driver as a module, choose M here and read
152 	  <file:Documentation/scsi/scsi.rst>. The module will be called sg.
153 
154 	  If unsure, say N.
155 
156 config BLK_DEV_BSG
157 	bool "/dev/bsg support (SG v4)"
158 	depends on SCSI
159 	default y
160 	help
161 	  Saying Y here will enable generic SG (SCSI generic) v4 support
162 	  for any SCSI device.
163 
164 	  This option is required by UDEV to access device serial numbers, etc.
165 
166 	  If unsure, say Y.
167 
168 config CHR_DEV_SCH
169 	tristate "SCSI media changer support"
170 	depends on SCSI
171 	help
172 	  This is a driver for SCSI media changers.  Most common devices are
173 	  tape libraries and MOD/CDROM jukeboxes.  *Real* jukeboxes, you
174 	  don't need this for those tiny 6-slot cdrom changers.  Media
175 	  changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
176 	  If you have such hardware and want to use it with linux, say Y
177 	  here.  Check <file:Documentation/scsi/scsi-changer.rst> for details.
178 
179 	  If you want to compile this as a module ( = code which can be
180 	  inserted in and removed from the running kernel whenever you want),
181 	  say M here and read <file:Documentation/kbuild/modules.rst> and
182 	  <file:Documentation/scsi/scsi.rst>. The module will be called ch.o.
183 	  If unsure, say N.
184 
185 config SCSI_ENCLOSURE
186 	tristate "SCSI Enclosure Support"
187 	depends on SCSI && ENCLOSURE_SERVICES
188 	depends on m || SCSI_SAS_ATTRS != m
189 	help
190 	  Enclosures are devices sitting on or in SCSI backplanes that
191 	  manage devices.  If you have a disk cage, the chances are that
192 	  it has an enclosure device.  Selecting this option will just allow
193 	  certain enclosure conditions to be reported and is not required.
194 
195 config SCSI_CONSTANTS
196 	bool "Verbose SCSI error reporting (kernel size += 36K)"
197 	depends on SCSI
198 	help
199 	  The error messages regarding your SCSI hardware will be easier to
200 	  understand if you say Y here; it will enlarge your kernel by about
201 	  36 KB. If in doubt, say Y.
202 
203 config SCSI_LOGGING
204 	bool "SCSI logging facility"
205 	depends on SCSI
206 	help
207 	  This turns on a logging facility that can be used to debug a number
208 	  of SCSI related problems.
209 
210 	  If you say Y here, no logging output will appear by default, but you
211 	  can enable logging by saying Y to "/proc file system support" and
212 	  "Sysctl support" below and executing the command
213 
214 	  echo <bitmask> > /proc/sys/dev/scsi/logging_level
215 
216 	  where <bitmask> is a four byte value representing the logging type
217 	  and logging level for each type of logging selected.
218 
219 	  There are a number of logging types and you can find them in the
220 	  source at <file:drivers/scsi/scsi_logging.h>. The logging levels
221 	  are also described in that file and they determine the verbosity of
222 	  the logging for each logging type.
223 
224 	  If you say N here, it may be harder to track down some types of SCSI
225 	  problems. If you say Y here your kernel will be somewhat larger, but
226 	  there should be no noticeable performance impact as long as you have
227 	  logging turned off.
228 
229 config SCSI_SCAN_ASYNC
230 	bool "Asynchronous SCSI scanning"
231 	depends on SCSI
232 	help
233 	  The SCSI subsystem can probe for devices while the rest of the
234 	  system continues booting, and even probe devices on different
235 	  busses in parallel, leading to a significant speed-up.
236 
237 	  You can override this choice by specifying "scsi_mod.scan=sync"
238 	  or async on the kernel's command line.
239 
240 	  Note that this setting also affects whether resuming from
241 	  system suspend will be performed asynchronously.
242 
243 config SCSI_PROTO_TEST
244 	tristate "scsi_proto.h unit tests" if !KUNIT_ALL_TESTS
245 	depends on SCSI && KUNIT
246 	default KUNIT_ALL_TESTS
247 
248 menu "SCSI Transports"
249 	depends on SCSI
250 
251 config SCSI_SPI_ATTRS
252 	tristate "Parallel SCSI (SPI) Transport Attributes"
253 	depends on SCSI
254 	help
255 	  If you wish to export transport-specific information about
256 	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
257 
258 config SCSI_FC_ATTRS
259 	tristate "FiberChannel Transport Attributes"
260 	depends on SCSI && NET
261 	select BLK_DEV_BSGLIB
262 	select SCSI_NETLINK
263 	help
264 	  If you wish to export transport-specific information about
265 	  each attached FiberChannel device to sysfs, say Y.
266 	  Otherwise, say N.
267 
268 config SCSI_ISCSI_ATTRS
269 	tristate "iSCSI Transport Attributes"
270 	depends on SCSI && NET
271 	select BLK_DEV_BSGLIB
272 	help
273 	  If you wish to export transport-specific information about
274 	  each attached iSCSI device to sysfs, say Y.
275 	  Otherwise, say N.
276 
277 config SCSI_SAS_ATTRS
278 	tristate "SAS Transport Attributes"
279 	depends on SCSI
280 	select BLK_DEV_BSGLIB
281 	help
282 	  If you wish to export transport-specific information about
283 	  each attached SAS device to sysfs, say Y.
284 
285 source "drivers/scsi/libsas/Kconfig"
286 
287 config SCSI_SRP_ATTRS
288 	tristate "SRP Transport Attributes"
289 	depends on SCSI
290 	help
291 	  If you wish to export transport-specific information about
292 	  each attached SRP device to sysfs, say Y.
293 
294 endmenu
295 
296 menuconfig SCSI_LOWLEVEL
297 	bool "SCSI low-level drivers"
298 	depends on SCSI!=n
299 	default y
300 
301 if SCSI_LOWLEVEL && SCSI
302 
303 config ISCSI_TCP
304 	tristate "iSCSI Initiator over TCP/IP"
305 	depends on SCSI && INET
306 	select CRYPTO
307 	select CRYPTO_MD5
308 	select CRYPTO_CRC32C
309 	select SCSI_ISCSI_ATTRS
310 	help
311 	 The iSCSI Driver provides a host with the ability to access storage
312 	 through an IP network. The driver uses the iSCSI protocol to transport
313 	 SCSI requests and responses over a TCP/IP network between the host
314 	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
315 	 combines with the host's TCP/IP stack, network drivers, and Network
316 	 Interface Card (NIC) to provide the same functions as a SCSI or a
317 	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
318 
319 	 To compile this driver as a module, choose M here: the
320 	 module will be called iscsi_tcp.
321 
322 	 The userspace component needed to initialize the driver, documentation,
323 	 and sample configuration files can be found here:
324 
325 	 http://open-iscsi.org
326 
327 config ISCSI_BOOT_SYSFS
328 	tristate "iSCSI Boot Sysfs Interface"
329 	default n
330 	help
331 	  This option enables support for exposing iSCSI boot information
332 	  via sysfs to userspace. If you wish to export this information,
333 	  say Y. Otherwise, say N.
334 
335 source "drivers/scsi/cxgbi/Kconfig"
336 source "drivers/scsi/bnx2i/Kconfig"
337 source "drivers/scsi/bnx2fc/Kconfig"
338 source "drivers/scsi/be2iscsi/Kconfig"
339 source "drivers/scsi/cxlflash/Kconfig"
340 
341 config SGIWD93_SCSI
342 	tristate "SGI WD93C93 SCSI Driver"
343 	depends on SGI_HAS_WD93 && SCSI
344 	help
345 	  If you have a Western Digital WD93 SCSI controller on
346 	  an SGI MIPS system, say Y.  Otherwise, say N.
347 
348 config BLK_DEV_3W_XXXX_RAID
349 	tristate "3ware 5/6/7/8xxx ATA-RAID support"
350 	depends on PCI && HAS_IOPORT && SCSI
351 	help
352 	  3ware is the only hardware ATA-Raid product in Linux to date.
353 	  This card is 2,4, or 8 channel master mode support only.
354 	  SCSI support required!!!
355 
356 	  <http://www.3ware.com/>
357 
358 	  Please read the comments at the top of
359 	  <file:drivers/scsi/3w-xxxx.c>.
360 
361 config SCSI_HPSA
362 	tristate "HP Smart Array SCSI driver"
363 	depends on PCI && SCSI
364 	select CHECK_SIGNATURE
365 	select SCSI_SAS_ATTRS
366 	help
367 	  This driver supports HP Smart Array Controllers (circa 2009).
368 	  It is a SCSI alternative to the cciss driver, which is a block
369 	  driver.  Anyone wishing to use HP Smart Array controllers who
370 	  would prefer the devices be presented to linux as SCSI devices,
371 	  rather than as generic block devices should say Y here.
372 
373 config SCSI_3W_9XXX
374 	tristate "3ware 9xxx SATA-RAID support"
375 	depends on PCI && SCSI
376 	help
377 	  This driver supports the 9000 series 3ware SATA-RAID cards.
378 
379 	  <http://www.amcc.com>
380 
381 	  Please read the comments at the top of
382 	  <file:drivers/scsi/3w-9xxx.c>.
383 
384 config SCSI_3W_SAS
385 	tristate "3ware 97xx SAS/SATA-RAID support"
386 	depends on PCI && SCSI
387 	help
388 	  This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
389 
390 	  <http://www.lsi.com>
391 
392 	  Please read the comments at the top of
393 	  <file:drivers/scsi/3w-sas.c>.
394 
395 config SCSI_ACARD
396 	tristate "ACARD SCSI support"
397 	depends on PCI && HAS_IOPORT && SCSI
398 	help
399 	  This driver supports the ACARD SCSI host adapter.
400 	  Support Chip <ATP870 ATP876 ATP880 ATP885>
401 	  To compile this driver as a module, choose M here: the
402 	  module will be called atp870u.
403 
404 config SCSI_AHA152X
405 	tristate "Adaptec AHA152X/2825 support"
406 	depends on ISA && SCSI
407 	select SCSI_SPI_ATTRS
408 	select CHECK_SIGNATURE
409 	help
410 	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
411 	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
412 	  must be manually specified in this case.
413 
414 	  It is explained in section 3.3 of the SCSI-HOWTO, available from
415 	  <http://www.tldp.org/docs.html#howto>. You might also want to
416 	  read the file <file:Documentation/scsi/aha152x.rst>.
417 
418 	  To compile this driver as a module, choose M here: the
419 	  module will be called aha152x.
420 
421 config SCSI_AHA1542
422 	tristate "Adaptec AHA1542 support"
423 	depends on ISA && SCSI && ISA_DMA_API
424 	help
425 	  This is support for a SCSI host adapter.  It is explained in section
426 	  3.4 of the SCSI-HOWTO, available from
427 	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
428 	  purchased by Adaptec, and some former Trantor products are being
429 	  sold under the Adaptec name.  If it doesn't work out of the box, you
430 	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
431 
432 	  To compile this driver as a module, choose M here: the
433 	  module will be called aha1542.
434 
435 config SCSI_AHA1740
436 	tristate "Adaptec AHA1740 support"
437 	depends on EISA && SCSI
438 	help
439 	  This is support for a SCSI host adapter.  It is explained in section
440 	  3.5 of the SCSI-HOWTO, available from
441 	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
442 	  of the box, you may have to change some settings in
443 	  <file:drivers/scsi/aha1740.h>.
444 
445 	  To compile this driver as a module, choose M here: the
446 	  module will be called aha1740.
447 
448 config SCSI_AACRAID
449 	tristate "Adaptec AACRAID support"
450 	depends on SCSI && PCI
451 	help
452 	  This driver supports a variety of Dell, HP, Adaptec, IBM and
453 	  ICP storage products. For a list of supported products, refer
454 	  to <file:Documentation/scsi/aacraid.rst>.
455 
456 	  To compile this driver as a module, choose M here: the module
457 	  will be called aacraid.
458 
459 
460 source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
461 source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
462 source "drivers/scsi/aic94xx/Kconfig"
463 source "drivers/scsi/hisi_sas/Kconfig"
464 source "drivers/scsi/mvsas/Kconfig"
465 
466 config SCSI_MVUMI
467 	tristate "Marvell UMI driver"
468 	depends on SCSI && PCI
469 	help
470 	  Module for Marvell Universal Message Interface(UMI) driver
471 
472 	  To compile this driver as a module, choose M here: the
473 	  module will be called mvumi.
474 
475 config SCSI_ADVANSYS
476 	tristate "AdvanSys SCSI support"
477 	depends on SCSI
478 	depends on (ISA || EISA || PCI) && HAS_IOPORT
479 	depends on ISA_DMA_API || !ISA
480 	help
481 	  This is a driver for all SCSI host adapters manufactured by
482 	  AdvanSys. It is documented in the kernel source in
483 	  <file:drivers/scsi/advansys.c>.
484 
485 	  To compile this driver as a module, choose M here: the
486 	  module will be called advansys.
487 
488 config SCSI_ARCMSR
489 	tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
490 	depends on PCI && SCSI
491 	help
492 	  This driver supports all of ARECA's SATA/SAS RAID controller cards.
493 	  This is an ARECA-maintained driver by Erich Chen.
494 	  If you have any problems, please mail to: <erich@areca.com.tw>.
495 	  Areca supports Linux RAID config tools.
496 	  Please link <http://www.areca.com.tw>
497 
498 	  To compile this driver as a module, choose M here: the
499 	  module will be called arcmsr (modprobe arcmsr).
500 
501 source "drivers/scsi/esas2r/Kconfig"
502 source "drivers/scsi/megaraid/Kconfig.megaraid"
503 source "drivers/scsi/mpt3sas/Kconfig"
504 source "drivers/scsi/mpi3mr/Kconfig"
505 source "drivers/scsi/smartpqi/Kconfig"
506 
507 config SCSI_HPTIOP
508 	tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
509 	depends on SCSI && PCI
510 	help
511 	  This option enables support for HighPoint RocketRAID 3xxx/4xxx
512 	  controllers.
513 
514 	  To compile this driver as a module, choose M here; the module
515 	  will be called hptiop. If unsure, say N.
516 
517 config SCSI_BUSLOGIC
518 	tristate "BusLogic SCSI support"
519 	depends on SCSI && PCI && HAS_IOPORT
520 	help
521 	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
522 	  Adapters. Consult the SCSI-HOWTO, available from
523 	  <http://www.tldp.org/docs.html#howto>, and the files
524 	  <file:Documentation/scsi/BusLogic.rst> and
525 	  <file:Documentation/scsi/FlashPoint.rst> for more information.
526 	  Note that support for FlashPoint is only available for 32-bit
527 	  x86 configurations.
528 
529 	  To compile this driver as a module, choose M here: the
530 	  module will be called BusLogic.
531 
532 config SCSI_FLASHPOINT
533 	bool "FlashPoint support"
534 	depends on SCSI_BUSLOGIC && PCI && HAS_IOPORT
535 	help
536 	  This option allows you to add FlashPoint support to the
537 	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
538 	  substantial, so users of MultiMaster Host Adapters may not
539 	  wish to include it.
540 
541 config SCSI_MYRB
542 	tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)"
543 	depends on PCI
544 	select RAID_ATTRS
545 	help
546 	  This driver adds support for the Mylex DAC960, AcceleRAID, and
547 	  eXtremeRAID PCI RAID controllers. This driver supports the
548 	  older, block based interface.
549 	  This driver is a reimplementation of the original DAC960
550 	  driver. If you have used the DAC960 driver you should enable
551 	  this module.
552 
553 	  To compile this driver as a module, choose M here: the
554 	  module will be called myrb.
555 
556 config SCSI_MYRS
557 	tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)"
558 	depends on PCI
559 	depends on !CPU_BIG_ENDIAN || COMPILE_TEST
560 	select RAID_ATTRS
561 	help
562 	  This driver adds support for the Mylex DAC960, AcceleRAID, and
563 	  eXtremeRAID PCI RAID controllers.  This driver supports the
564 	  newer, SCSI-based interface only.
565 	  This driver is a reimplementation of the original DAC960
566 	  driver. If you have used the DAC960 driver you should enable
567 	  this module.
568 
569 	  To compile this driver as a module, choose M here: the
570 	  module will be called myrs.
571 
572 config VMWARE_PVSCSI
573 	tristate "VMware PVSCSI driver support"
574 	depends on PCI && SCSI && X86
575 	help
576 	  This driver supports VMware's para virtualized SCSI HBA.
577 	  To compile this driver as a module, choose M here: the
578 	  module will be called vmw_pvscsi.
579 
580 config XEN_SCSI_FRONTEND
581 	tristate "XEN SCSI frontend driver"
582 	depends on SCSI && XEN
583 	select XEN_XENBUS_FRONTEND
584 	help
585 	  The XEN SCSI frontend driver allows the kernel to access SCSI Devices
586 	  within another guest OS (usually Dom0).
587 	  Only needed if the kernel is running in a XEN guest and generic
588 	  SCSI access to a device is needed.
589 
590 config HYPERV_STORAGE
591 	tristate "Microsoft Hyper-V virtual storage driver"
592 	depends on SCSI && HYPERV
593 	depends on m || SCSI_FC_ATTRS != m
594 	default HYPERV
595 	help
596 	  Select this option to enable the Hyper-V virtual storage driver.
597 
598 config LIBFC
599 	tristate "LibFC module"
600 	depends on SCSI_FC_ATTRS
601 	select CRC32
602 	help
603 	  Fibre Channel library module
604 
605 config LIBFCOE
606 	tristate "LibFCoE module"
607 	depends on LIBFC
608 	help
609 	  Library for Fibre Channel over Ethernet module
610 
611 config FCOE
612 	tristate "FCoE module"
613 	depends on PCI
614 	depends on LIBFCOE
615 	help
616 	  Fibre Channel over Ethernet module
617 
618 config FCOE_FNIC
619 	tristate "Cisco FNIC Driver"
620 	depends on PCI && X86
621 	depends on LIBFCOE
622 	help
623 	  This is support for the Cisco PCI-Express FCoE HBA.
624 
625 	  To compile this driver as a module, choose M here and read
626 	  <file:Documentation/scsi/scsi.rst>.
627 	  The module will be called fnic.
628 
629 config SCSI_SNIC
630 	tristate "Cisco SNIC Driver"
631 	depends on PCI && SCSI
632 	help
633 	  This is support for the Cisco PCI-Express SCSI HBA.
634 
635 	  To compile this driver as a module, choose M here and read
636 	  <file:Documentation/scsi/scsi.rst>.
637 	  The module will be called snic.
638 
639 config SCSI_SNIC_DEBUG_FS
640 	bool "Cisco SNIC Driver Debugfs Support"
641 	depends on SCSI_SNIC && DEBUG_FS
642 	help
643 	  This enables to list debugging information from SNIC Driver
644 	  available via debugfs file system
645 
646 config SCSI_DMX3191D
647 	tristate "DMX3191D SCSI support"
648 	depends on PCI && HAS_IOPORT && SCSI
649 	select SCSI_SPI_ATTRS
650 	help
651 	  This is support for Domex DMX3191D SCSI Host Adapters.
652 
653 	  To compile this driver as a module, choose M here: the
654 	  module will be called dmx3191d.
655 
656 config SCSI_FDOMAIN
657 	tristate
658 	depends on SCSI
659 
660 config SCSI_FDOMAIN_PCI
661 	tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support"
662 	depends on PCI && HAS_IOPORT && SCSI
663 	select SCSI_FDOMAIN
664 	help
665 	  This is support for Future Domain's PCI SCSI host adapters (TMC-3260)
666 	  and other adapters with PCI bus based on the Future Domain chipsets
667 	  (Adaptec AHA-2920A).
668 
669 	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
670 	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
671 	  controller support"). This Future Domain driver works with the older
672 	  Adaptec AHA-2920A boards with a Future Domain chip on them.
673 
674 	  To compile this driver as a module, choose M here: the
675 	  module will be called fdomain_pci.
676 
677 config SCSI_FDOMAIN_ISA
678 	tristate "Future Domain 16xx ISA SCSI support"
679 	depends on ISA && SCSI
680 	select CHECK_SIGNATURE
681 	select SCSI_FDOMAIN
682 	help
683 	  This is support for Future Domain's 16-bit SCSI host adapters
684 	  (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters
685 	  with ISA bus based on the Future Domain chipsets (Quantum ISA-200S,
686 	  ISA-250MG; and at least one IBM board).
687 
688 	  To compile this driver as a module, choose M here: the
689 	  module will be called fdomain_isa.
690 
691 config SCSI_ISCI
692 	tristate "Intel(R) C600 Series Chipset SAS Controller"
693 	depends on PCI && SCSI
694 	depends on X86
695 	select SCSI_SAS_LIBSAS
696 	help
697 	  This driver supports the 6Gb/s SAS capabilities of the storage
698 	  control unit found in the Intel(R) C600 series chipset.
699 
700 config SCSI_GENERIC_NCR5380
701 	tristate "Generic NCR5380/53c400 SCSI ISA card support"
702 	depends on ISA && SCSI && HAS_IOPORT_MAP
703 	select SCSI_SPI_ATTRS
704 	help
705 	  This is a driver for old ISA card SCSI controllers based on a
706 	  NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
707 	  Most boards such as the Trantor T130 fit this category, as do
708 	  various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
709 
710 	  To compile this driver as a module, choose M here: the
711 	  module will be called g_NCR5380.
712 
713 config SCSI_IPS
714 	tristate "IBM ServeRAID support"
715 	depends on PCI && HAS_IOPORT && SCSI
716 	help
717 	  This is support for the IBM ServeRAID hardware RAID controllers.
718 	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
719 	  and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
720 	  for more information.  If this driver does not work correctly
721 	  without modification please contact the author by email at
722 	  <ipslinux@adaptec.com>.
723 
724 	  To compile this driver as a module, choose M here: the
725 	  module will be called ips.
726 
727 config SCSI_IBMVSCSI
728 	tristate "IBM Virtual SCSI support"
729 	depends on PPC_PSERIES
730 	select SCSI_SRP_ATTRS
731 	help
732 	  This is the IBM POWER Virtual SCSI Client
733 
734 	  To compile this driver as a module, choose M here: the
735 	  module will be called ibmvscsi.
736 
737 config SCSI_IBMVSCSIS
738 	tristate "IBM Virtual SCSI Server support"
739 	depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
740 	help
741 	  This is the IBM POWER Virtual SCSI Target Server
742 	  This driver uses the SRP protocol for communication between servers
743 	  guest and/or the host that run on the same server.
744 	  More information on VSCSI protocol can be found at www.power.org
745 
746 	  The userspace configuration needed to initialize the driver can be
747 	  be found here:
748 
749 	  https://github.com/powervm/ibmvscsis/wiki/Configuration
750 
751 	  To compile this driver as a module, choose M here: the
752 	  module will be called ibmvscsis.
753 
754 config SCSI_IBMVFC
755 	tristate "IBM Virtual FC support"
756 	depends on PPC_PSERIES && SCSI
757 	depends on SCSI_FC_ATTRS
758 	help
759 	  This is the IBM POWER Virtual FC Client
760 
761 	  To compile this driver as a module, choose M here: the
762 	  module will be called ibmvfc.
763 
764 config SCSI_IBMVFC_TRACE
765 	bool "enable driver internal trace"
766 	depends on SCSI_IBMVFC
767 	default y
768 	help
769 	  If you say Y here, the driver will trace all commands issued
770 	  to the adapter. Performance impact is minimal. Trace can be
771 	  dumped using /sys/class/scsi_host/hostXX/trace.
772 
773 config SCSI_INITIO
774 	tristate "Initio 9100U(W) support"
775 	depends on PCI && HAS_IOPORT && SCSI
776 	help
777 	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
778 	  read the SCSI-HOWTO, available from
779 	  <http://www.tldp.org/docs.html#howto>.
780 
781 	  To compile this driver as a module, choose M here: the
782 	  module will be called initio.
783 
784 config SCSI_INIA100
785 	tristate "Initio INI-A100U2W support"
786 	depends on PCI && HAS_IOPORT && SCSI
787 	help
788 	  This is support for the Initio INI-A100U2W SCSI host adapter.
789 	  Please read the SCSI-HOWTO, available from
790 	  <http://www.tldp.org/docs.html#howto>.
791 
792 	  To compile this driver as a module, choose M here: the
793 	  module will be called a100u2w.
794 
795 config SCSI_PPA
796 	tristate "IOMEGA parallel port (ppa - older drives)"
797 	depends on SCSI && PARPORT_PC
798 	depends on HAS_IOPORT
799 	help
800 	  This driver supports older versions of IOMEGA's parallel port ZIP
801 	  drive (a 100 MB removable media device).
802 
803 	  Note that you can say N here if you have the SCSI version of the ZIP
804 	  drive: it will be supported automatically if you said Y to the
805 	  generic "SCSI disk support", above.
806 
807 	  If you have the ZIP Plus drive or a more recent parallel port ZIP
808 	  drive (if the supplied cable with the drive is labeled "AutoDetect")
809 	  then you should say N here and Y to "IOMEGA parallel port (imm -
810 	  newer drives)", below.
811 
812 	  For more information about this driver and how to use it you should
813 	  read the file <file:Documentation/scsi/ppa.rst>.  You should also read
814 	  the SCSI-HOWTO, which is available from
815 	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
816 	  you will still be able to use the parallel port for other tasks,
817 	  such as a printer; it is safe to compile both drivers into the
818 	  kernel.
819 
820 	  To compile this driver as a module, choose M here: the
821 	  module will be called ppa.
822 
823 config SCSI_IMM
824 	tristate "IOMEGA parallel port (imm - newer drives)"
825 	depends on SCSI && PARPORT_PC
826 	help
827 	  This driver supports newer versions of IOMEGA's parallel port ZIP
828 	  drive (a 100 MB removable media device).
829 
830 	  Note that you can say N here if you have the SCSI version of the ZIP
831 	  drive: it will be supported automatically if you said Y to the
832 	  generic "SCSI disk support", above.
833 
834 	  If you have the ZIP Plus drive or a more recent parallel port ZIP
835 	  drive (if the supplied cable with the drive is labeled "AutoDetect")
836 	  then you should say Y here; if you have an older ZIP drive, say N
837 	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
838 
839 	  For more information about this driver and how to use it you should
840 	  read the file <file:Documentation/scsi/ppa.rst>.  You should also read
841 	  the SCSI-HOWTO, which is available from
842 	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
843 	  you will still be able to use the parallel port for other tasks,
844 	  such as a printer; it is safe to compile both drivers into the
845 	  kernel.
846 
847 	  To compile this driver as a module, choose M here: the
848 	  module will be called imm.
849 
850 config SCSI_IZIP_SLOW_CTR
851 	bool "ppa/imm option - Assume slow parport control register"
852 	depends on SCSI_PPA || SCSI_IMM
853 	help
854 	  Some parallel ports are known to have excessive delays between
855 	  changing the parallel port control register and good data being
856 	  available on the parallel port data/status register. This option
857 	  forces a small delay (1.0 usec to be exact) after changing the
858 	  control register to let things settle out. Enabling this option may
859 	  result in a big drop in performance but some very old parallel ports
860 	  (found in 386 vintage machines) will not work properly.
861 
862 	  Generally, saying N is fine.
863 
864 config SCSI_LASI700
865 	tristate "HP Lasi SCSI support for 53c700/710"
866 	depends on GSC && SCSI
867 	select SCSI_SPI_ATTRS
868 	help
869 	  This is a driver for the SCSI controller in the Lasi chip found in
870 	  many PA-RISC workstations & servers.  If you do not know whether you
871 	  have a Lasi chip, it is safe to say "Y" here.
872 
873 config SCSI_SNI_53C710
874 	tristate "SNI RM SCSI support for 53c710"
875 	depends on SNI_RM && SCSI
876 	select SCSI_SPI_ATTRS
877 	select 53C700_LE_ON_BE
878 	help
879 	  This is a driver for the onboard SCSI controller found in older
880 	  SNI RM workstations & servers.
881 
882 config 53C700_LE_ON_BE
883 	bool
884 	depends on SCSI_LASI700 || SCSI_SNI_53C710
885 	default y
886 
887 config SCSI_STEX
888 	tristate "Promise SuperTrak EX Series support"
889 	depends on PCI && SCSI
890 	help
891 	  This driver supports Promise SuperTrak EX series storage controllers.
892 
893 	  Promise provides Linux RAID configuration utility for these
894 	  controllers. Please visit <http://www.promise.com> to download.
895 
896 	  To compile this driver as a module, choose M here: the
897 	  module will be called stex.
898 
899 config 53C700_BE_BUS
900 	bool
901 	depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
902 	default y
903 
904 config SCSI_SYM53C8XX_2
905 	tristate "SYM53C8XX Version 2 SCSI support"
906 	depends on PCI && SCSI
907 	select SCSI_SPI_ATTRS
908 	help
909 	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
910 	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
911 	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
912 	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
913 	  controllers; you need to use the Fusion MPT driver for that.
914 
915 	  Please read <file:Documentation/scsi/sym53c8xx_2.rst> for more
916 	  information.
917 
918 config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
919 	int "DMA addressing mode"
920 	depends on SCSI_SYM53C8XX_2
921 	default "1"
922 	help
923 	  This option only applies to PCI-SCSI chips that are PCI DAC
924 	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
925 
926 	  When set to 0, the driver will program the chip to only perform
927 	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
928 	  to addresses up to 1TB.  When set to 2, the driver supports the
929 	  full 64-bit DMA address range, but can only address 16 segments
930 	  of 4 GB each.  This limits the total addressable range to 64 GB.
931 
932 	  Most machines with less than 4GB of memory should use a setting
933 	  of 0 for best performance.  If your machine has 4GB of memory
934 	  or more, you should set this option to 1 (the default).
935 
936 	  The still experimental value 2 (64 bit DMA addressing with 16
937 	  x 4GB segments limitation) can be used on systems that require
938 	  PCI address bits past bit 39 to be set for the addressing of
939 	  memory using PCI DAC cycles.
940 
941 config SCSI_SYM53C8XX_DEFAULT_TAGS
942 	int "Default tagged command queue depth"
943 	depends on SCSI_SYM53C8XX_2
944 	default "16"
945 	help
946 	  This is the default value of the command queue depth the
947 	  driver will announce to the generic SCSI layer for devices
948 	  that support tagged command queueing. This value can be changed
949 	  from the boot command line.  This is a soft limit that cannot
950 	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
951 
952 config SCSI_SYM53C8XX_MAX_TAGS
953 	int "Maximum number of queued commands"
954 	depends on SCSI_SYM53C8XX_2
955 	default "64"
956 	help
957 	  This option allows you to specify the maximum number of commands
958 	  that can be queued to any device, when tagged command queuing is
959 	  possible. The driver supports up to 256 queued commands per device.
960 	  This value is used as a compiled-in hard limit.
961 
962 config SCSI_SYM53C8XX_MMIO
963 	bool "Use memory mapped IO"
964 	depends on SCSI_SYM53C8XX_2
965 	default y
966 	help
967 	  Memory mapped IO is faster than Port IO.  Most people should
968 	  answer Y here, but some machines may have problems.  If you have
969 	  to answer N here, please report the problem to the maintainer.
970 
971 config SCSI_IPR
972 	tristate "IBM Power Linux RAID adapter support"
973 	depends on PCI && SCSI
974 	select FW_LOADER
975 	select IRQ_POLL
976 	select SGL_ALLOC
977 	help
978 	  This driver supports the IBM Power Linux family RAID adapters.
979 	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
980 	  as IBM iSeries 5702, 5703, 5709, and 570A.
981 
982 config SCSI_IPR_TRACE
983 	bool "enable driver internal trace"
984 	depends on SCSI_IPR
985 	default y
986 	help
987 	  If you say Y here, the driver will trace all commands issued
988 	  to the adapter. Performance impact is minimal. Trace can be
989 	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
990 
991 config SCSI_IPR_DUMP
992 	bool "enable adapter dump support"
993 	depends on SCSI_IPR
994 	default y
995 	help
996 	  If you say Y here, the driver will support adapter crash dump.
997 	  If you enable this support, the iprdump daemon can be used
998 	  to capture adapter failure analysis information.
999 
1000 config SCSI_ZALON
1001 	tristate "Zalon SCSI support"
1002 	depends on GSC && SCSI
1003 	select SCSI_SPI_ATTRS
1004 	help
1005 	  The Zalon is a GSC/HSC bus interface chip that sits between the
1006 	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1007 	  C110, J200, J210 and some D, K & R-class machines.  It's also
1008 	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1009 	  Say Y here if you have one of these machines or cards.
1010 
1011 config SCSI_NCR53C8XX_DEFAULT_TAGS
1012 	int "default tagged command queue depth"
1013 	depends on SCSI_ZALON
1014 	default "8"
1015 	help
1016 	  "Tagged command queuing" is a feature of SCSI-2 which improves
1017 	  performance: the host adapter can send several SCSI commands to a
1018 	  device's queue even if previous commands haven't finished yet.
1019 	  Because the device is intelligent, it can optimize its operations
1020 	  (like head positioning) based on its own request queue. Some SCSI
1021 	  devices don't implement this properly; if you want to disable this
1022 	  feature, enter 0 or 1 here (it doesn't matter which).
1023 
1024 	  The default value is 8 and should be supported by most hard disks.
1025 	  This value can be overridden from the boot command line using the
1026 	  'tags' option as follows (example):
1027 	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1028 	  4, set queue depth to 16 for target 2 and target 3 on controller 0
1029 	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
1030 
1031 	  The normal answer therefore is to go with the default 8 and to use
1032 	  a boot command line option for devices that need to use a different
1033 	  command queue depth.
1034 
1035 	  There is no safe option other than using good SCSI devices.
1036 
1037 config SCSI_NCR53C8XX_MAX_TAGS
1038 	int "maximum number of queued commands"
1039 	depends on SCSI_ZALON
1040 	default "32"
1041 	help
1042 	  This option allows you to specify the maximum number of commands
1043 	  that can be queued to any device, when tagged command queuing is
1044 	  possible. The default value is 32. Minimum is 2, maximum is 64.
1045 	  Modern hard disks are able to support 64 tags and even more, but
1046 	  do not seem to be faster when more than 32 tags are being used.
1047 
1048 	  So, the normal answer here is to go with the default value 32 unless
1049 	  you are using very large hard disks with large cache (>= 1 MB) that
1050 	  are able to take advantage of more than 32 tagged commands.
1051 
1052 	  There is no safe option and the default answer is recommended.
1053 
1054 config SCSI_NCR53C8XX_SYNC
1055 	int "synchronous transfers frequency in MHz"
1056 	depends on SCSI_ZALON
1057 	default "20"
1058 	help
1059 	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1060 	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
1061 	  are respectively the maximum data transfer rates in mega-transfers
1062 	  per second for each class.  For example, a FAST-20 Wide 16 device is
1063 	  able to transfer data at 20 million 16 bit packets per second for a
1064 	  total rate of 40 MB/s.
1065 
1066 	  You may specify 0 if you want to only use asynchronous data
1067 	  transfers. This is the safest and slowest option. Otherwise, specify
1068 	  a value between 5 and 80, depending on the capability of your SCSI
1069 	  controller.  The higher the number, the faster the data transfer.
1070 	  Note that 80 should normally be ok since the driver decreases the
1071 	  value automatically according to the controller's capabilities.
1072 
1073 	  Your answer to this question is ignored for controllers with NVRAM,
1074 	  since the driver will get this information from the user set-up.  It
1075 	  also can be overridden using a boot setup option, as follows
1076 	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1077 	  for FAST-20 synchronous data transfer (20 mega-transfers per
1078 	  second).
1079 
1080 	  The normal answer therefore is not to go with the default but to
1081 	  select the maximum value 80 allowing the driver to use the maximum
1082 	  value supported by each controller. If this causes problems with
1083 	  your SCSI devices, you should come back and decrease the value.
1084 
1085 	  There is no safe option other than using good cabling, right
1086 	  terminations and SCSI conformant devices.
1087 
1088 config SCSI_NCR53C8XX_NO_DISCONNECT
1089 	bool "not allow targets to disconnect"
1090 	depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1091 	help
1092 	  This option is only provided for safety if you suspect some SCSI
1093 	  device of yours to not support properly the target-disconnect
1094 	  feature. In that case, you would say Y here. In general however, to
1095 	  not allow targets to disconnect is not reasonable if there is more
1096 	  than 1 device on a SCSI bus. The normal answer therefore is N.
1097 
1098 config SCSI_QLOGIC_FAS
1099 	tristate "Qlogic FAS SCSI support"
1100 	depends on ISA && SCSI
1101 	help
1102 	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1103 	  FastSCSI! cards as well as any other card based on the FASXX chip
1104 	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1105 
1106 	  This driver does NOT support the PCI versions of these cards. The
1107 	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1108 	  SCSI support"), below.
1109 
1110 	  Information about this driver is contained in
1111 	  <file:Documentation/scsi/qlogicfas.rst>.  You should also read the
1112 	  SCSI-HOWTO, available from
1113 	  <http://www.tldp.org/docs.html#howto>.
1114 
1115 	  To compile this driver as a module, choose M here: the
1116 	  module will be called qlogicfas.
1117 
1118 config SCSI_QLOGIC_1280
1119 	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1120 	depends on PCI && SCSI
1121 	help
1122 	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1123 
1124 	  To compile this driver as a module, choose M here: the
1125 	  module will be called qla1280.
1126 
1127 config SCSI_QLOGICPTI
1128 	tristate "PTI Qlogic, ISP Driver"
1129 	depends on SBUS && SCSI
1130 	help
1131 	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
1132 	  controllers are known under Solaris as qpti and in the openprom as
1133 	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1134 	  driven by a different driver.
1135 
1136 	  To compile this driver as a module, choose M here: the
1137 	  module will be called qlogicpti.
1138 
1139 source "drivers/scsi/qla2xxx/Kconfig"
1140 source "drivers/scsi/qla4xxx/Kconfig"
1141 source "drivers/scsi/qedi/Kconfig"
1142 source "drivers/scsi/qedf/Kconfig"
1143 
1144 config SCSI_LPFC
1145 	tristate "Emulex LightPulse Fibre Channel Support"
1146 	depends on PCI && SCSI
1147 	depends on CPU_FREQ
1148 	depends on SCSI_FC_ATTRS
1149 	depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1150 	depends on NVME_FC || NVME_FC=n
1151 	select CRC_T10DIF
1152 	select IRQ_POLL
1153 	help
1154           This lpfc driver supports the Emulex LightPulse
1155           Family of Fibre Channel PCI host adapters.
1156 
1157 config SCSI_LPFC_DEBUG_FS
1158 	bool "Emulex LightPulse Fibre Channel debugfs Support"
1159 	depends on SCSI_LPFC && DEBUG_FS
1160 	help
1161 	  This makes debugging information from the lpfc driver
1162 	  available via the debugfs filesystem.
1163 
1164 source "drivers/scsi/elx/Kconfig"
1165 
1166 config SCSI_SIM710
1167 	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1168 	depends on EISA && SCSI
1169 	select SCSI_SPI_ATTRS
1170 	help
1171 	  This driver is for NCR53c710 based SCSI host adapters.
1172 
1173 	  It currently supports Compaq EISA cards.
1174 
1175 config SCSI_DC395x
1176 	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1177 	depends on PCI && HAS_IOPORT && SCSI
1178 	select SCSI_SPI_ATTRS
1179 	help
1180 	  This driver supports PCI SCSI host adapters based on the ASIC
1181 	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1182 
1183 	  This driver works, but is still in experimental status. So better
1184 	  have a bootable disk and a backup in case of emergency.
1185 
1186 	  Documentation can be found in <file:Documentation/scsi/dc395x.rst>.
1187 
1188 	  To compile this driver as a module, choose M here: the
1189 	  module will be called dc395x.
1190 
1191 config SCSI_AM53C974
1192 	tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1193 	depends on PCI && SCSI
1194 	select SCSI_SPI_ATTRS
1195 	help
1196 	  This driver supports PCI SCSI host adapters based on the Am53C974A
1197 	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1198 	  PCscsi/PCnet (Am53/79C974) solutions.
1199 	  This is a new implementation base on the generic esp_scsi driver.
1200 
1201 	  Note that this driver does NOT support Tekram DC390W/U/F, which are
1202 	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1203 
1204 	  To compile this driver as a module, choose M here: the
1205 	  module will be called am53c974.
1206 
1207 config SCSI_NSP32
1208 	tristate "Workbit NinjaSCSI-32Bi/UDE support"
1209 	depends on PCI && SCSI && !64BIT && HAS_IOPORT
1210 	help
1211 	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1212 	  SCSI host adapter. Please read the SCSI-HOWTO, available from
1213 	  <http://www.tldp.org/docs.html#howto>.
1214 
1215 	  To compile this driver as a module, choose M here: the
1216 	  module will be called nsp32.
1217 
1218 config SCSI_WD719X
1219 	tristate "Western Digital WD7193/7197/7296 support"
1220 	depends on PCI && SCSI
1221 	select EEPROM_93CX6
1222 	help
1223 	  This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1224 	  SCSI controllers (based on WD33C296A chip).
1225 
1226 config SCSI_DEBUG
1227 	tristate "SCSI debugging host and device simulator"
1228 	depends on SCSI
1229 	select CRC_T10DIF
1230 	help
1231 	  This pseudo driver simulates one or more hosts (SCSI initiators),
1232 	  each with one or more targets, each with one or more logical units.
1233 	  Defaults to one of each, creating a small RAM disk device. Many
1234 	  parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1235 	  directory can be tweaked at run time.
1236 	  See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1237 	  Mainly used for testing and best as a module. If unsure, say N.
1238 
1239 config SCSI_MESH
1240 	tristate "MESH (Power Mac internal SCSI) support"
1241 	depends on PPC32 && PPC_PMAC && SCSI
1242 	help
1243 	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1244 	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1245 	  other Power Macintoshes do). Say Y to include support for this SCSI
1246 	  adaptor.
1247 
1248 	  To compile this driver as a module, choose M here: the
1249 	  module will be called mesh.
1250 
1251 config SCSI_MESH_SYNC_RATE
1252 	int "maximum synchronous transfer rate (MB/s) (0 = async)"
1253 	depends on SCSI_MESH
1254 	default "5"
1255 	help
1256 	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1257 	  drives a bus which is entirely internal to the machine (such as the
1258 	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
1259 	  operation at up to 10 MB/s. On machines where the SCSI bus
1260 	  controlled by the MESH can have external devices connected, it is
1261 	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
1262 	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
1263 	  to disable synchronous operation.
1264 
1265 config SCSI_MESH_RESET_DELAY_MS
1266 	int "initial bus reset delay (ms) (0 = no reset)"
1267 	depends on SCSI_MESH
1268 	default "4000"
1269 
1270 config SCSI_MAC53C94
1271 	tristate "53C94 (Power Mac external SCSI) support"
1272 	depends on PPC32 && PPC_PMAC && SCSI
1273 	help
1274 	  On Power Macintoshes (and clones) with two SCSI buses, the external
1275 	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1276 	  machines which only have one SCSI bus, such as the 7200, also use
1277 	  the 53C94. Say Y to include support for the 53C94.
1278 
1279 	  To compile this driver as a module, choose M here: the
1280 	  module will be called mac53c94.
1281 
1282 source "drivers/scsi/arm/Kconfig"
1283 
1284 config JAZZ_ESP
1285 	bool "MIPS JAZZ FAS216 SCSI support"
1286 	depends on MACH_JAZZ && SCSI=y
1287 	select SCSI_SPI_ATTRS
1288 	help
1289 	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
1290 	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1291 	  systems.
1292 
1293 config A3000_SCSI
1294 	tristate "A3000 WD33C93A support"
1295 	depends on AMIGA && SCSI
1296 	help
1297 	  If you have an Amiga 3000 and have SCSI devices connected to the
1298 	  built-in SCSI controller, say Y. Otherwise, say N.
1299 
1300 	  To compile this driver as a module, choose M here: the
1301 	  module will be called a3000.
1302 
1303 config A2091_SCSI
1304 	tristate "A2091/A590 WD33C93A support"
1305 	depends on ZORRO && SCSI
1306 	help
1307 	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1308 	  say N.
1309 
1310 	  To compile this driver as a module, choose M here: the
1311 	  module will be called a2091.
1312 
1313 config GVP11_SCSI
1314 	tristate "GVP Series II WD33C93A support"
1315 	depends on ZORRO && SCSI
1316 	help
1317 	  If you have a Great Valley Products Series II SCSI controller,
1318 	  answer Y. Also say Y if you have a later model of GVP SCSI
1319 	  controller (such as the GVP A4008 or a Combo board). Otherwise,
1320 	  answer N. This driver does NOT work for the T-Rex series of
1321 	  accelerators from TekMagic and GVP-M.
1322 
1323 	  To compile this driver as a module, choose M here: the
1324 	  module will be called gvp11.
1325 
1326 config SCSI_A4000T
1327 	tristate "A4000T NCR53c710 SCSI support"
1328 	depends on AMIGA && SCSI
1329 	select SCSI_SPI_ATTRS
1330 	help
1331 	  If you have an Amiga 4000T and have SCSI devices connected to the
1332 	  built-in SCSI controller, say Y. Otherwise, say N.
1333 
1334 	  To compile this driver as a module, choose M here: the
1335 	  module will be called a4000t.
1336 
1337 config SCSI_ZORRO7XX
1338 	tristate "Zorro NCR53c710 SCSI support"
1339 	depends on ZORRO && SCSI
1340 	select SCSI_SPI_ATTRS
1341 	help
1342 	  Support for various NCR53c710-based SCSI controllers on Zorro
1343 	  expansion boards for the Amiga.
1344 	  This includes:
1345 	    - the Amiga 4091 Zorro III SCSI-2 controller,
1346 	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1347 	      (info at
1348 	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1349 	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1350 	      accelerator card for the Amiga 1200,
1351 	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
1352 
1353 config SCSI_ZORRO_ESP
1354 	tristate "Zorro ESP SCSI support"
1355 	depends on ZORRO && SCSI
1356 	select SCSI_SPI_ATTRS
1357 	select SCSI_ESP_PIO
1358 	help
1359 	  Support for various NCR53C9x (ESP) based SCSI controllers on Zorro
1360 	  expansion boards for the Amiga.
1361 	  This includes:
1362 	    - the Phase5 Blizzard 1230 II and IV SCSI controllers,
1363 	    - the Phase5 Blizzard 2060 SCSI controller,
1364 	    - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI
1365 	      controllers,
1366 	    - the Fastlane Zorro III SCSI controller.
1367 
1368 config ATARI_SCSI
1369 	tristate "Atari native SCSI support"
1370 	depends on ATARI && SCSI
1371 	select SCSI_SPI_ATTRS
1372 	help
1373 	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
1374 	  Falcon, ...) say Y to get it supported. Of course also, if you have
1375 	  a compatible SCSI controller (e.g. for Medusa).
1376 
1377 	  To compile this driver as a module, choose M here: the module will
1378 	  be called atari_scsi. If you also enable NVRAM support, the SCSI
1379 	  host's ID is taken from the setting in TT RTC NVRAM.
1380 
1381 	  This driver supports both styles of NCR integration into the
1382 	  system: the TT style (separate DMA), and the Falcon style (via
1383 	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
1384 	  in the Hades (without DMA).
1385 
1386 config MAC_SCSI
1387 	tristate "Macintosh NCR5380 SCSI"
1388 	depends on MAC && SCSI
1389 	select SCSI_SPI_ATTRS
1390 	help
1391 	  This is the NCR 5380 SCSI controller included on most of the 68030
1392 	  based Macintoshes.  If you have one of these say Y and read the
1393 	  SCSI-HOWTO, available from
1394 	  <http://www.tldp.org/docs.html#howto>.
1395 
1396 config SCSI_MAC_ESP
1397 	tristate "Macintosh NCR53c9[46] SCSI"
1398 	depends on MAC && SCSI
1399 	select SCSI_SPI_ATTRS
1400 	select SCSI_ESP_PIO
1401 	help
1402 	  This is the NCR 53c9x SCSI controller found on most of the 68040
1403 	  based Macintoshes.
1404 
1405 	  To compile this driver as a module, choose M here: the module
1406 	  will be called mac_esp.
1407 
1408 config MVME147_SCSI
1409 	bool "WD33C93 SCSI driver for MVME147"
1410 	depends on MVME147 && SCSI=y
1411 	select SCSI_SPI_ATTRS
1412 	help
1413 	  Support for the on-board SCSI controller on the Motorola MVME147
1414 	  single-board computer.
1415 
1416 config MVME16x_SCSI
1417 	tristate "NCR53C710 SCSI driver for MVME16x"
1418 	depends on MVME16x && SCSI
1419 	select SCSI_SPI_ATTRS
1420 	help
1421 	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1422 	  SCSI controller chip.  Almost everyone using one of these boards
1423 	  will want to say Y to this question.
1424 
1425 config BVME6000_SCSI
1426 	tristate "NCR53C710 SCSI driver for BVME6000"
1427 	depends on BVME6000 && SCSI
1428 	select SCSI_SPI_ATTRS
1429 	help
1430 	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1431 	  SCSI controller chip.  Almost everyone using one of these boards
1432 	  will want to say Y to this question.
1433 
1434 config SUN3_SCSI
1435 	tristate "Sun3 NCR5380 SCSI"
1436 	depends on SUN3 && SCSI
1437 	select SCSI_SPI_ATTRS
1438 	help
1439 	  This option will enable support for the OBIO (onboard io) NCR5380
1440 	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
1441 	  "Sun3" type VME scsi controllers also based on the NCR5380.
1442 	  General Linux information on the Sun 3 series (now discontinued)
1443 	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1444 
1445 config SUN3X_ESP
1446 	bool "Sun3x ESP SCSI"
1447 	depends on SUN3X && SCSI=y
1448 	select SCSI_SPI_ATTRS
1449 	help
1450 	  The ESP was an on-board SCSI controller used on Sun 3/80
1451 	  machines.  Say Y here to compile in support for it.
1452 
1453 config SCSI_SUNESP
1454 	tristate "Sparc ESP Scsi Driver"
1455 	depends on SBUS && SCSI
1456 	select SCSI_SPI_ATTRS
1457 	help
1458 	  This is the driver for the Sun ESP SCSI host adapter. The ESP
1459 	  chipset is present in most SPARC SBUS-based computers and
1460 	  supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1461 	  esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1462 
1463 	  To compile this driver as a module, choose M here: the
1464 	  module will be called sun_esp.
1465 
1466 config ZFCP
1467 	tristate "FCP host bus adapter driver for IBM mainframes"
1468 	depends on S390 && QDIO && SCSI
1469 	depends on SCSI_FC_ATTRS
1470 	help
1471 	  If you want to access SCSI devices attached to your IBM mainframe by
1472 	  means of Fibre Channel Protocol host bus adapters say Y.
1473 
1474 	  Supported HBAs include different models of the FICON Express and FCP
1475 	  Express I/O cards.
1476 
1477 	  For a more complete list, and for more details about setup and
1478 	  operation refer to the IBM publication "Device Drivers, Features, and
1479 	  Commands", SC33-8411.
1480 
1481           This driver is also available as a module. This module will be
1482           called zfcp. If you want to compile it as a module, say M here
1483           and read <file:Documentation/kbuild/modules.rst>.
1484 
1485 config SCSI_PMCRAID
1486 	tristate "PMC SIERRA Linux MaxRAID adapter support"
1487 	depends on PCI && SCSI && NET
1488 	select SGL_ALLOC
1489 	help
1490 	  This driver supports the PMC SIERRA MaxRAID adapters.
1491 
1492 config SCSI_PM8001
1493 	tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1494 	depends on PCI && SCSI
1495 	select SCSI_SAS_LIBSAS
1496 	help
1497 	  This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1498 	  based host adapters.
1499 
1500 config SCSI_BFA_FC
1501 	tristate "Brocade BFA Fibre Channel Support"
1502 	depends on PCI && SCSI
1503 	depends on SCSI_FC_ATTRS
1504 	help
1505 	  This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1506 
1507 	  To compile this driver as a module, choose M here. The module will
1508 	  be called bfa.
1509 
1510 config SCSI_VIRTIO
1511 	tristate "virtio-scsi support"
1512 	depends on VIRTIO
1513 	help
1514           This is the virtual HBA driver for virtio.  If the kernel will
1515           be used in a virtual machine, say Y or M.
1516 
1517 source "drivers/scsi/csiostor/Kconfig"
1518 
1519 source "drivers/scsi/pcmcia/Kconfig"
1520 
1521 endif # SCSI_LOWLEVEL
1522 
1523 source "drivers/scsi/device_handler/Kconfig"
1524 
1525 endmenu
1526