Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1# SPDX-License-Identifier: GPL-2.0-only
2menu "SCSI device support"
3
4config SCSI_MOD
5 tristate
6 default y if SCSI=n || SCSI=y
7 default m if SCSI=m
8 depends on BLOCK
9
10config 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
18config SCSI_COMMON
19 tristate
20
21config 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
47config SCSI_DMA
48 bool
49 default n
50
51config SCSI_ESP_PIO
52 bool
53
54config SCSI_NETLINK
55 bool
56 default n
57 depends on NET
58
59config 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
70config 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
79comment "SCSI support type (disk, tape, CD-ROM)"
80 depends on SCSI
81
82config 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
103config 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
116config 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
131config 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
156config 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
168config 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
185config 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
195config 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
203config 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
229config 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
243config 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
248menu "SCSI Transports"
249 depends on SCSI
250
251config 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
258config 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
268config 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
277config 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
285source "drivers/scsi/libsas/Kconfig"
286
287config 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
294endmenu
295
296menuconfig SCSI_LOWLEVEL
297 bool "SCSI low-level drivers"
298 depends on SCSI!=n
299 default y
300
301if SCSI_LOWLEVEL && SCSI
302
303config ISCSI_TCP
304 tristate "iSCSI Initiator over TCP/IP"
305 depends on SCSI && INET
306 select CRC32
307 select SCSI_ISCSI_ATTRS
308 help
309 The iSCSI Driver provides a host with the ability to access storage
310 through an IP network. The driver uses the iSCSI protocol to transport
311 SCSI requests and responses over a TCP/IP network between the host
312 (the "initiator") and "targets". Architecturally, the iSCSI driver
313 combines with the host's TCP/IP stack, network drivers, and Network
314 Interface Card (NIC) to provide the same functions as a SCSI or a
315 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
316
317 To compile this driver as a module, choose M here: the
318 module will be called iscsi_tcp.
319
320 The userspace component needed to initialize the driver, documentation,
321 and sample configuration files can be found here:
322
323 http://open-iscsi.org
324
325config ISCSI_BOOT_SYSFS
326 tristate "iSCSI Boot Sysfs Interface"
327 default n
328 help
329 This option enables support for exposing iSCSI boot information
330 via sysfs to userspace. If you wish to export this information,
331 say Y. Otherwise, say N.
332
333source "drivers/scsi/cxgbi/Kconfig"
334source "drivers/scsi/bnx2i/Kconfig"
335source "drivers/scsi/bnx2fc/Kconfig"
336source "drivers/scsi/be2iscsi/Kconfig"
337
338config SGIWD93_SCSI
339 tristate "SGI WD93C93 SCSI Driver"
340 depends on SGI_HAS_WD93 && SCSI
341 help
342 If you have a Western Digital WD93 SCSI controller on
343 an SGI MIPS system, say Y. Otherwise, say N.
344
345config BLK_DEV_3W_XXXX_RAID
346 tristate "3ware 5/6/7/8xxx ATA-RAID support"
347 depends on PCI && HAS_IOPORT && SCSI
348 help
349 3ware is the only hardware ATA-Raid product in Linux to date.
350 This card is 2,4, or 8 channel master mode support only.
351 SCSI support required!!!
352
353 <http://www.3ware.com/>
354
355 Please read the comments at the top of
356 <file:drivers/scsi/3w-xxxx.c>.
357
358config SCSI_HPSA
359 tristate "HP Smart Array SCSI driver"
360 depends on PCI && SCSI
361 select CHECK_SIGNATURE
362 select SCSI_SAS_ATTRS
363 help
364 This driver supports HP Smart Array Controllers (circa 2009).
365 It is a SCSI alternative to the cciss driver, which is a block
366 driver. Anyone wishing to use HP Smart Array controllers who
367 would prefer the devices be presented to linux as SCSI devices,
368 rather than as generic block devices should say Y here.
369
370config SCSI_3W_9XXX
371 tristate "3ware 9xxx SATA-RAID support"
372 depends on PCI && SCSI
373 help
374 This driver supports the 9000 series 3ware SATA-RAID cards.
375
376 <http://www.amcc.com>
377
378 Please read the comments at the top of
379 <file:drivers/scsi/3w-9xxx.c>.
380
381config SCSI_3W_SAS
382 tristate "3ware 97xx SAS/SATA-RAID support"
383 depends on PCI && SCSI
384 help
385 This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
386
387 <http://www.lsi.com>
388
389 Please read the comments at the top of
390 <file:drivers/scsi/3w-sas.c>.
391
392config SCSI_ACARD
393 tristate "ACARD SCSI support"
394 depends on PCI && HAS_IOPORT && SCSI
395 help
396 This driver supports the ACARD SCSI host adapter.
397 Support Chip <ATP870 ATP876 ATP880 ATP885>
398 To compile this driver as a module, choose M here: the
399 module will be called atp870u.
400
401config SCSI_AHA152X
402 tristate "Adaptec AHA152X/2825 support"
403 depends on ISA && SCSI
404 depends on !HIGHMEM
405 select SCSI_SPI_ATTRS
406 select CHECK_SIGNATURE
407 help
408 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
409 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
410 must be manually specified in this case.
411
412 It is explained in section 3.3 of the SCSI-HOWTO, available from
413 <http://www.tldp.org/docs.html#howto>. You might also want to
414 read the file <file:Documentation/scsi/aha152x.rst>.
415
416 To compile this driver as a module, choose M here: the
417 module will be called aha152x.
418
419config SCSI_AHA1542
420 tristate "Adaptec AHA1542 support"
421 depends on ISA && SCSI && ISA_DMA_API
422 help
423 This is support for a SCSI host adapter. It is explained in section
424 3.4 of the SCSI-HOWTO, available from
425 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
426 purchased by Adaptec, and some former Trantor products are being
427 sold under the Adaptec name. If it doesn't work out of the box, you
428 may have to change some settings in <file:drivers/scsi/aha1542.h>.
429
430 To compile this driver as a module, choose M here: the
431 module will be called aha1542.
432
433config SCSI_AHA1740
434 tristate "Adaptec AHA1740 support"
435 depends on EISA && SCSI
436 help
437 This is support for a SCSI host adapter. It is explained in section
438 3.5 of the SCSI-HOWTO, available from
439 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
440 of the box, you may have to change some settings in
441 <file:drivers/scsi/aha1740.h>.
442
443 To compile this driver as a module, choose M here: the
444 module will be called aha1740.
445
446config SCSI_AACRAID
447 tristate "Adaptec AACRAID support"
448 depends on SCSI && PCI
449 help
450 This driver supports a variety of Dell, HP, Adaptec, IBM and
451 ICP storage products. For a list of supported products, refer
452 to <file:Documentation/scsi/aacraid.rst>.
453
454 To compile this driver as a module, choose M here: the module
455 will be called aacraid.
456
457
458source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
459source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
460source "drivers/scsi/aic94xx/Kconfig"
461source "drivers/scsi/hisi_sas/Kconfig"
462source "drivers/scsi/mvsas/Kconfig"
463
464config SCSI_MVUMI
465 tristate "Marvell UMI driver"
466 depends on SCSI && PCI
467 help
468 Module for Marvell Universal Message Interface(UMI) driver
469
470 To compile this driver as a module, choose M here: the
471 module will be called mvumi.
472
473config SCSI_ADVANSYS
474 tristate "AdvanSys SCSI support"
475 depends on SCSI
476 depends on (ISA || EISA || PCI) && HAS_IOPORT
477 depends on ISA_DMA_API || !ISA
478 help
479 This is a driver for all SCSI host adapters manufactured by
480 AdvanSys. It is documented in the kernel source in
481 <file:drivers/scsi/advansys.c>.
482
483 To compile this driver as a module, choose M here: the
484 module will be called advansys.
485
486config SCSI_ARCMSR
487 tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
488 depends on PCI && SCSI
489 help
490 This driver supports all of ARECA's SATA/SAS RAID controller cards.
491 This is an ARECA-maintained driver by Erich Chen.
492 If you have any problems, please mail to: <erich@areca.com.tw>.
493 Areca supports Linux RAID config tools.
494 Please link <http://www.areca.com.tw>
495
496 To compile this driver as a module, choose M here: the
497 module will be called arcmsr (modprobe arcmsr).
498
499source "drivers/scsi/esas2r/Kconfig"
500source "drivers/scsi/megaraid/Kconfig.megaraid"
501source "drivers/scsi/mpt3sas/Kconfig"
502source "drivers/scsi/mpi3mr/Kconfig"
503source "drivers/scsi/smartpqi/Kconfig"
504
505config SCSI_HPTIOP
506 tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
507 depends on SCSI && PCI
508 help
509 This option enables support for HighPoint RocketRAID 3xxx/4xxx
510 controllers.
511
512 To compile this driver as a module, choose M here; the module
513 will be called hptiop. If unsure, say N.
514
515config SCSI_BUSLOGIC
516 tristate "BusLogic SCSI support"
517 depends on SCSI && PCI && HAS_IOPORT
518 help
519 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
520 Adapters. Consult the SCSI-HOWTO, available from
521 <http://www.tldp.org/docs.html#howto>, and the files
522 <file:Documentation/scsi/BusLogic.rst> and
523 <file:Documentation/scsi/FlashPoint.rst> for more information.
524 Note that support for FlashPoint is only available for 32-bit
525 x86 configurations.
526
527 To compile this driver as a module, choose M here: the
528 module will be called BusLogic.
529
530config SCSI_FLASHPOINT
531 bool "FlashPoint support"
532 depends on SCSI_BUSLOGIC && PCI && HAS_IOPORT
533 help
534 This option allows you to add FlashPoint support to the
535 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
536 substantial, so users of MultiMaster Host Adapters may not
537 wish to include it.
538
539config SCSI_MYRB
540 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)"
541 depends on PCI
542 select RAID_ATTRS
543 help
544 This driver adds support for the Mylex DAC960, AcceleRAID, and
545 eXtremeRAID PCI RAID controllers. This driver supports the
546 older, block based interface.
547 This driver is a reimplementation of the original DAC960
548 driver. If you have used the DAC960 driver you should enable
549 this module.
550
551 To compile this driver as a module, choose M here: the
552 module will be called myrb.
553
554config SCSI_MYRS
555 tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)"
556 depends on PCI
557 depends on !CPU_BIG_ENDIAN || COMPILE_TEST
558 select RAID_ATTRS
559 help
560 This driver adds support for the Mylex DAC960, AcceleRAID, and
561 eXtremeRAID PCI RAID controllers. This driver supports the
562 newer, SCSI-based interface only.
563 This driver is a reimplementation of the original DAC960
564 driver. If you have used the DAC960 driver you should enable
565 this module.
566
567 To compile this driver as a module, choose M here: the
568 module will be called myrs.
569
570config VMWARE_PVSCSI
571 tristate "VMware PVSCSI driver support"
572 depends on PCI && SCSI && X86
573 help
574 This driver supports VMware's para virtualized SCSI HBA.
575 To compile this driver as a module, choose M here: the
576 module will be called vmw_pvscsi.
577
578config XEN_SCSI_FRONTEND
579 tristate "XEN SCSI frontend driver"
580 depends on SCSI && XEN
581 select XEN_XENBUS_FRONTEND
582 help
583 The XEN SCSI frontend driver allows the kernel to access SCSI Devices
584 within another guest OS (usually Dom0).
585 Only needed if the kernel is running in a XEN guest and generic
586 SCSI access to a device is needed.
587
588config HYPERV_STORAGE
589 tristate "Microsoft Hyper-V virtual storage driver"
590 depends on SCSI && HYPERV_VMBUS
591 depends on m || SCSI_FC_ATTRS != m
592 default HYPERV
593 help
594 Select this option to enable the Hyper-V virtual storage driver.
595
596config LIBFC
597 tristate "LibFC module"
598 depends on SCSI_FC_ATTRS
599 select CRC32
600 help
601 Fibre Channel library module
602
603config LIBFCOE
604 tristate "LibFCoE module"
605 depends on LIBFC
606 help
607 Library for Fibre Channel over Ethernet module
608
609config FCOE
610 tristate "FCoE module"
611 depends on PCI
612 depends on LIBFCOE
613 help
614 Fibre Channel over Ethernet module
615
616config FCOE_FNIC
617 tristate "Cisco FNIC Driver"
618 depends on PCI && X86
619 depends on LIBFCOE
620 help
621 This is support for the Cisco PCI-Express FCoE HBA.
622
623 To compile this driver as a module, choose M here and read
624 <file:Documentation/scsi/scsi.rst>.
625 The module will be called fnic.
626
627config SCSI_SNIC
628 tristate "Cisco SNIC Driver"
629 depends on PCI && SCSI
630 help
631 This is support for the Cisco PCI-Express SCSI HBA.
632
633 To compile this driver as a module, choose M here and read
634 <file:Documentation/scsi/scsi.rst>.
635 The module will be called snic.
636
637config SCSI_SNIC_DEBUG_FS
638 bool "Cisco SNIC Driver Debugfs Support"
639 depends on SCSI_SNIC && DEBUG_FS
640 help
641 This enables to list debugging information from SNIC Driver
642 available via debugfs file system
643
644config SCSI_DMX3191D
645 tristate "DMX3191D SCSI support"
646 depends on PCI && HAS_IOPORT && SCSI
647 select SCSI_SPI_ATTRS
648 help
649 This is support for Domex DMX3191D SCSI Host Adapters.
650
651 To compile this driver as a module, choose M here: the
652 module will be called dmx3191d.
653
654config SCSI_FDOMAIN
655 tristate
656 depends on SCSI
657
658config SCSI_FDOMAIN_PCI
659 tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support"
660 depends on PCI && HAS_IOPORT && SCSI
661 select SCSI_FDOMAIN
662 help
663 This is support for Future Domain's PCI SCSI host adapters (TMC-3260)
664 and other adapters with PCI bus based on the Future Domain chipsets
665 (Adaptec AHA-2920A).
666
667 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
668 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
669 controller support"). This Future Domain driver works with the older
670 Adaptec AHA-2920A boards with a Future Domain chip on them.
671
672 To compile this driver as a module, choose M here: the
673 module will be called fdomain_pci.
674
675config SCSI_FDOMAIN_ISA
676 tristate "Future Domain 16xx ISA SCSI support"
677 depends on ISA && SCSI
678 select CHECK_SIGNATURE
679 select SCSI_FDOMAIN
680 help
681 This is support for Future Domain's 16-bit SCSI host adapters
682 (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters
683 with ISA bus based on the Future Domain chipsets (Quantum ISA-200S,
684 ISA-250MG; and at least one IBM board).
685
686 To compile this driver as a module, choose M here: the
687 module will be called fdomain_isa.
688
689config SCSI_ISCI
690 tristate "Intel(R) C600 Series Chipset SAS Controller"
691 depends on PCI && SCSI
692 depends on X86
693 select SCSI_SAS_LIBSAS
694 help
695 This driver supports the 6Gb/s SAS capabilities of the storage
696 control unit found in the Intel(R) C600 series chipset.
697
698config SCSI_GENERIC_NCR5380
699 tristate "Generic NCR5380/53c400 SCSI ISA card support"
700 depends on ISA && SCSI && HAS_IOPORT_MAP
701 select SCSI_SPI_ATTRS
702 help
703 This is a driver for old ISA card SCSI controllers based on a
704 NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
705 Most boards such as the Trantor T130 fit this category, as do
706 various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
707
708 To compile this driver as a module, choose M here: the
709 module will be called g_NCR5380.
710
711config SCSI_IPS
712 tristate "IBM ServeRAID support"
713 depends on PCI && HAS_IOPORT && SCSI
714 help
715 This is support for the IBM ServeRAID hardware RAID controllers.
716 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
717 and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
718 for more information. If this driver does not work correctly
719 without modification please contact the author by email at
720 <ipslinux@adaptec.com>.
721
722 To compile this driver as a module, choose M here: the
723 module will be called ips.
724
725config SCSI_IBMVSCSI
726 tristate "IBM Virtual SCSI support"
727 depends on PPC_PSERIES
728 select SCSI_SRP_ATTRS
729 help
730 This is the IBM POWER Virtual SCSI Client
731
732 To compile this driver as a module, choose M here: the
733 module will be called ibmvscsi.
734
735config SCSI_IBMVSCSIS
736 tristate "IBM Virtual SCSI Server support"
737 depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
738 help
739 This is the IBM POWER Virtual SCSI Target Server
740 This driver uses the SRP protocol for communication between servers
741 guest and/or the host that run on the same server.
742 More information on VSCSI protocol can be found at www.power.org
743
744 The userspace configuration needed to initialize the driver can be
745 be found here:
746
747 https://github.com/powervm/ibmvscsis/wiki/Configuration
748
749 To compile this driver as a module, choose M here: the
750 module will be called ibmvscsis.
751
752config SCSI_IBMVFC
753 tristate "IBM Virtual FC support"
754 depends on PPC_PSERIES && SCSI
755 depends on SCSI_FC_ATTRS
756 help
757 This is the IBM POWER Virtual FC Client
758
759 To compile this driver as a module, choose M here: the
760 module will be called ibmvfc.
761
762config SCSI_IBMVFC_TRACE
763 bool "enable driver internal trace"
764 depends on SCSI_IBMVFC
765 default y
766 help
767 If you say Y here, the driver will trace all commands issued
768 to the adapter. Performance impact is minimal. Trace can be
769 dumped using /sys/class/scsi_host/hostXX/trace.
770
771config SCSI_INITIO
772 tristate "Initio 9100U(W) support"
773 depends on PCI && HAS_IOPORT && SCSI
774 help
775 This is support for the Initio 91XXU(W) SCSI host adapter. Please
776 read the SCSI-HOWTO, available from
777 <http://www.tldp.org/docs.html#howto>.
778
779 To compile this driver as a module, choose M here: the
780 module will be called initio.
781
782config SCSI_INIA100
783 tristate "Initio INI-A100U2W support"
784 depends on PCI && HAS_IOPORT && SCSI
785 help
786 This is support for the Initio INI-A100U2W SCSI host adapter.
787 Please read the SCSI-HOWTO, available from
788 <http://www.tldp.org/docs.html#howto>.
789
790 To compile this driver as a module, choose M here: the
791 module will be called a100u2w.
792
793config SCSI_PPA
794 tristate "IOMEGA parallel port (ppa - older drives)"
795 depends on SCSI && PARPORT_PC
796 depends on HAS_IOPORT
797 depends on !HIGHMEM
798 help
799 This driver supports older versions of IOMEGA's parallel port ZIP
800 drive (a 100 MB removable media device).
801
802 Note that you can say N here if you have the SCSI version of the ZIP
803 drive: it will be supported automatically if you said Y to the
804 generic "SCSI disk support", above.
805
806 If you have the ZIP Plus drive or a more recent parallel port ZIP
807 drive (if the supplied cable with the drive is labeled "AutoDetect")
808 then you should say N here and Y to "IOMEGA parallel port (imm -
809 newer drives)", below.
810
811 For more information about this driver and how to use it you should
812 read the file <file:Documentation/scsi/ppa.rst>. You should also read
813 the SCSI-HOWTO, which is available from
814 <http://www.tldp.org/docs.html#howto>. If you use this driver,
815 you will still be able to use the parallel port for other tasks,
816 such as a printer; it is safe to compile both drivers into the
817 kernel.
818
819 To compile this driver as a module, choose M here: the
820 module will be called ppa.
821
822config SCSI_IMM
823 tristate "IOMEGA parallel port (imm - newer drives)"
824 depends on SCSI && PARPORT_PC
825 depends on !HIGHMEM
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
850config 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
864config 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
873config 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
882config 53C700_LE_ON_BE
883 bool
884 depends on SCSI_LASI700 || SCSI_SNI_53C710
885 default y
886
887config 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
899config 53C700_BE_BUS
900 bool
901 depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
902 default y
903
904config 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
918config 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
941config 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
952config 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
962config 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
971config 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
982config 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
991config 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
1000config 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
1011config 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
1037config 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
1054config 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
1088config 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
1098config 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
1118config 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
1127config 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
1139source "drivers/scsi/qla2xxx/Kconfig"
1140source "drivers/scsi/qla4xxx/Kconfig"
1141source "drivers/scsi/qedi/Kconfig"
1142source "drivers/scsi/qedf/Kconfig"
1143
1144config 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 CRC32
1153 select IRQ_POLL
1154 help
1155 This lpfc driver supports the Emulex LightPulse
1156 Family of Fibre Channel PCI host adapters.
1157
1158config SCSI_LPFC_DEBUG_FS
1159 bool "Emulex LightPulse Fibre Channel debugfs Support"
1160 depends on SCSI_LPFC && DEBUG_FS
1161 help
1162 This makes debugging information from the lpfc driver
1163 available via the debugfs filesystem.
1164
1165source "drivers/scsi/elx/Kconfig"
1166
1167config SCSI_SIM710
1168 tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
1169 depends on EISA && SCSI
1170 select SCSI_SPI_ATTRS
1171 help
1172 This driver is for NCR53c710 based SCSI host adapters.
1173
1174 It currently supports Compaq EISA cards.
1175
1176config SCSI_DC395x
1177 tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support"
1178 depends on PCI && HAS_IOPORT && SCSI
1179 select SCSI_SPI_ATTRS
1180 help
1181 This driver supports PCI SCSI host adapters based on the ASIC
1182 TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
1183
1184 This driver works, but is still in experimental status. So better
1185 have a bootable disk and a backup in case of emergency.
1186
1187 Documentation can be found in <file:Documentation/scsi/dc395x.rst>.
1188
1189 To compile this driver as a module, choose M here: the
1190 module will be called dc395x.
1191
1192config SCSI_AM53C974
1193 tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)"
1194 depends on PCI && SCSI
1195 select SCSI_SPI_ATTRS
1196 help
1197 This driver supports PCI SCSI host adapters based on the Am53C974A
1198 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
1199 PCscsi/PCnet (Am53/79C974) solutions.
1200 This is a new implementation base on the generic esp_scsi driver.
1201
1202 Note that this driver does NOT support Tekram DC390W/U/F, which are
1203 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
1204
1205 To compile this driver as a module, choose M here: the
1206 module will be called am53c974.
1207
1208config SCSI_NSP32
1209 tristate "Workbit NinjaSCSI-32Bi/UDE support"
1210 depends on PCI && SCSI && !64BIT && HAS_IOPORT
1211 help
1212 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
1213 SCSI host adapter. Please read the SCSI-HOWTO, available from
1214 <http://www.tldp.org/docs.html#howto>.
1215
1216 To compile this driver as a module, choose M here: the
1217 module will be called nsp32.
1218
1219config SCSI_WD719X
1220 tristate "Western Digital WD7193/7197/7296 support"
1221 depends on PCI && SCSI
1222 select EEPROM_93CX6
1223 help
1224 This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI
1225 SCSI controllers (based on WD33C296A chip).
1226
1227config SCSI_DEBUG
1228 tristate "SCSI debugging host and device simulator"
1229 depends on SCSI
1230 select CRC_T10DIF
1231 help
1232 This pseudo driver simulates one or more hosts (SCSI initiators),
1233 each with one or more targets, each with one or more logical units.
1234 Defaults to one of each, creating a small RAM disk device. Many
1235 parameters found in the /sys/bus/pseudo/drivers/scsi_debug
1236 directory can be tweaked at run time.
1237 See <http://sg.danny.cz/sg/sdebug26.html> for more information.
1238 Mainly used for testing and best as a module. If unsure, say N.
1239
1240config SCSI_MESH
1241 tristate "MESH (Power Mac internal SCSI) support"
1242 depends on PPC32 && PPC_PMAC && SCSI
1243 help
1244 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
1245 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
1246 other Power Macintoshes do). Say Y to include support for this SCSI
1247 adaptor.
1248
1249 To compile this driver as a module, choose M here: the
1250 module will be called mesh.
1251
1252config SCSI_MESH_SYNC_RATE
1253 int "maximum synchronous transfer rate (MB/s) (0 = async)"
1254 depends on SCSI_MESH
1255 default "5"
1256 help
1257 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
1258 drives a bus which is entirely internal to the machine (such as the
1259 7500, 7600, 8500, etc.), the MESH is capable of synchronous
1260 operation at up to 10 MB/s. On machines where the SCSI bus
1261 controlled by the MESH can have external devices connected, it is
1262 usually rated at 5 MB/s. 5 is a safe value here unless you know the
1263 MESH SCSI bus is internal only; in that case you can say 10. Say 0
1264 to disable synchronous operation.
1265
1266config SCSI_MESH_RESET_DELAY_MS
1267 int "initial bus reset delay (ms) (0 = no reset)"
1268 depends on SCSI_MESH
1269 default "4000"
1270
1271config SCSI_MAC53C94
1272 tristate "53C94 (Power Mac external SCSI) support"
1273 depends on PPC32 && PPC_PMAC && SCSI
1274 help
1275 On Power Macintoshes (and clones) with two SCSI buses, the external
1276 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
1277 machines which only have one SCSI bus, such as the 7200, also use
1278 the 53C94. Say Y to include support for the 53C94.
1279
1280 To compile this driver as a module, choose M here: the
1281 module will be called mac53c94.
1282
1283source "drivers/scsi/arm/Kconfig"
1284
1285config JAZZ_ESP
1286 bool "MIPS JAZZ FAS216 SCSI support"
1287 depends on MACH_JAZZ && SCSI=y
1288 select SCSI_SPI_ATTRS
1289 help
1290 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1291 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1292 systems.
1293
1294config A3000_SCSI
1295 tristate "A3000 WD33C93A support"
1296 depends on AMIGA && SCSI
1297 help
1298 If you have an Amiga 3000 and have SCSI devices connected to the
1299 built-in SCSI controller, say Y. Otherwise, say N.
1300
1301 To compile this driver as a module, choose M here: the
1302 module will be called a3000.
1303
1304config A2091_SCSI
1305 tristate "A2091/A590 WD33C93A support"
1306 depends on ZORRO && SCSI
1307 help
1308 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
1309 say N.
1310
1311 To compile this driver as a module, choose M here: the
1312 module will be called a2091.
1313
1314config GVP11_SCSI
1315 tristate "GVP Series II WD33C93A support"
1316 depends on ZORRO && SCSI
1317 help
1318 If you have a Great Valley Products Series II SCSI controller,
1319 answer Y. Also say Y if you have a later model of GVP SCSI
1320 controller (such as the GVP A4008 or a Combo board). Otherwise,
1321 answer N. This driver does NOT work for the T-Rex series of
1322 accelerators from TekMagic and GVP-M.
1323
1324 To compile this driver as a module, choose M here: the
1325 module will be called gvp11.
1326
1327config SCSI_A4000T
1328 tristate "A4000T NCR53c710 SCSI support"
1329 depends on AMIGA && SCSI
1330 select SCSI_SPI_ATTRS
1331 help
1332 If you have an Amiga 4000T and have SCSI devices connected to the
1333 built-in SCSI controller, say Y. Otherwise, say N.
1334
1335 To compile this driver as a module, choose M here: the
1336 module will be called a4000t.
1337
1338config SCSI_ZORRO7XX
1339 tristate "Zorro NCR53c710 SCSI support"
1340 depends on ZORRO && SCSI
1341 select SCSI_SPI_ATTRS
1342 help
1343 Support for various NCR53c710-based SCSI controllers on Zorro
1344 expansion boards for the Amiga.
1345 This includes:
1346 - the Amiga 4091 Zorro III SCSI-2 controller,
1347 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
1348 (info at
1349 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
1350 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
1351 accelerator card for the Amiga 1200,
1352 - the SCSI controller on the GVP Turbo 040/060 accelerator.
1353
1354config SCSI_ZORRO_ESP
1355 tristate "Zorro ESP SCSI support"
1356 depends on ZORRO && SCSI
1357 select SCSI_SPI_ATTRS
1358 select SCSI_ESP_PIO
1359 help
1360 Support for various NCR53C9x (ESP) based SCSI controllers on Zorro
1361 expansion boards for the Amiga.
1362 This includes:
1363 - the Phase5 Blizzard 1230 II and IV SCSI controllers,
1364 - the Phase5 Blizzard 2060 SCSI controller,
1365 - the Phase5 Blizzard Cyberstorm and Cyberstorm II SCSI
1366 controllers,
1367 - the Fastlane Zorro III SCSI controller.
1368
1369config ATARI_SCSI
1370 tristate "Atari native SCSI support"
1371 depends on ATARI && SCSI
1372 select SCSI_SPI_ATTRS
1373 help
1374 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1375 Falcon, ...) say Y to get it supported. Of course also, if you have
1376 a compatible SCSI controller (e.g. for Medusa).
1377
1378 To compile this driver as a module, choose M here: the module will
1379 be called atari_scsi. If you also enable NVRAM support, the SCSI
1380 host's ID is taken from the setting in TT RTC NVRAM.
1381
1382 This driver supports both styles of NCR integration into the
1383 system: the TT style (separate DMA), and the Falcon style (via
1384 ST-DMA, replacing ACSI). It does NOT support other schemes, like
1385 in the Hades (without DMA).
1386
1387config MAC_SCSI
1388 tristate "Macintosh NCR5380 SCSI"
1389 depends on MAC && SCSI
1390 select SCSI_SPI_ATTRS
1391 help
1392 This is the NCR 5380 SCSI controller included on most of the 68030
1393 based Macintoshes. If you have one of these say Y and read the
1394 SCSI-HOWTO, available from
1395 <http://www.tldp.org/docs.html#howto>.
1396
1397config SCSI_MAC_ESP
1398 tristate "Macintosh NCR53c9[46] SCSI"
1399 depends on MAC && SCSI
1400 select SCSI_SPI_ATTRS
1401 select SCSI_ESP_PIO
1402 help
1403 This is the NCR 53c9x SCSI controller found on most of the 68040
1404 based Macintoshes.
1405
1406 To compile this driver as a module, choose M here: the module
1407 will be called mac_esp.
1408
1409config MVME147_SCSI
1410 bool "WD33C93 SCSI driver for MVME147"
1411 depends on MVME147 && SCSI=y
1412 select SCSI_SPI_ATTRS
1413 help
1414 Support for the on-board SCSI controller on the Motorola MVME147
1415 single-board computer.
1416
1417config MVME16x_SCSI
1418 tristate "NCR53C710 SCSI driver for MVME16x"
1419 depends on MVME16x && SCSI
1420 select SCSI_SPI_ATTRS
1421 help
1422 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1423 SCSI controller chip. Almost everyone using one of these boards
1424 will want to say Y to this question.
1425
1426config BVME6000_SCSI
1427 tristate "NCR53C710 SCSI driver for BVME6000"
1428 depends on BVME6000 && SCSI
1429 select SCSI_SPI_ATTRS
1430 help
1431 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1432 SCSI controller chip. Almost everyone using one of these boards
1433 will want to say Y to this question.
1434
1435config SUN3_SCSI
1436 tristate "Sun3 NCR5380 SCSI"
1437 depends on SUN3 && SCSI
1438 select SCSI_SPI_ATTRS
1439 help
1440 This option will enable support for the OBIO (onboard io) NCR5380
1441 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1442 "Sun3" type VME scsi controllers also based on the NCR5380.
1443 General Linux information on the Sun 3 series (now discontinued)
1444 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1445
1446config SUN3X_ESP
1447 bool "Sun3x ESP SCSI"
1448 depends on SUN3X && SCSI=y
1449 select SCSI_SPI_ATTRS
1450 help
1451 The ESP was an on-board SCSI controller used on Sun 3/80
1452 machines. Say Y here to compile in support for it.
1453
1454config SCSI_SUNESP
1455 tristate "Sparc ESP Scsi Driver"
1456 depends on SBUS && SCSI
1457 select SCSI_SPI_ATTRS
1458 help
1459 This is the driver for the Sun ESP SCSI host adapter. The ESP
1460 chipset is present in most SPARC SBUS-based computers and
1461 supports the Emulex family of ESP SCSI chips (esp100, esp100A,
1462 esp236, fas101, fas236) as well as the Qlogic fas366 SCSI chip.
1463
1464 To compile this driver as a module, choose M here: the
1465 module will be called sun_esp.
1466
1467config ZFCP
1468 tristate "FCP host bus adapter driver for IBM mainframes"
1469 depends on S390 && QDIO && SCSI
1470 depends on SCSI_FC_ATTRS
1471 help
1472 If you want to access SCSI devices attached to your IBM mainframe by
1473 means of Fibre Channel Protocol host bus adapters say Y.
1474
1475 Supported HBAs include different models of the FICON Express and FCP
1476 Express I/O cards.
1477
1478 For a more complete list, and for more details about setup and
1479 operation refer to the IBM publication "Device Drivers, Features, and
1480 Commands", SC33-8411.
1481
1482 This driver is also available as a module. This module will be
1483 called zfcp. If you want to compile it as a module, say M here
1484 and read <file:Documentation/kbuild/modules.rst>.
1485
1486config SCSI_PMCRAID
1487 tristate "PMC SIERRA Linux MaxRAID adapter support"
1488 depends on PCI && SCSI && NET
1489 select SGL_ALLOC
1490 help
1491 This driver supports the PMC SIERRA MaxRAID adapters.
1492
1493config SCSI_PM8001
1494 tristate "PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver"
1495 depends on PCI && SCSI
1496 select SCSI_SAS_LIBSAS
1497 help
1498 This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
1499 based host adapters.
1500
1501config SCSI_BFA_FC
1502 tristate "Brocade BFA Fibre Channel Support"
1503 depends on PCI && SCSI
1504 depends on SCSI_FC_ATTRS
1505 help
1506 This bfa driver supports all Brocade PCIe FC/FCOE host adapters.
1507
1508 To compile this driver as a module, choose M here. The module will
1509 be called bfa.
1510
1511config SCSI_VIRTIO
1512 tristate "virtio-scsi support"
1513 depends on VIRTIO
1514 help
1515 This is the virtual HBA driver for virtio. If the kernel will
1516 be used in a virtual machine, say Y or M.
1517
1518source "drivers/scsi/csiostor/Kconfig"
1519
1520source "drivers/scsi/pcmcia/Kconfig"
1521
1522endif # SCSI_LOWLEVEL
1523
1524source "drivers/scsi/device_handler/Kconfig"
1525
1526endmenu