xref: /openbmc/linux/drivers/scsi/Kconfig (revision 5ae75a1a)
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
9config RAID_ATTRS
10	tristate "RAID Transport Class"
11	default n
12	depends on BLOCK
13	depends on SCSI_MOD
14	help
15	  Provides RAID
16
17config SCSI_COMMON
18	tristate
19
20config SCSI
21	tristate "SCSI device support"
22	depends on BLOCK
23	select SCSI_DMA if HAS_DMA
24	select SG_POOL
25	select SCSI_COMMON
26	select BLK_DEV_BSG_COMMON if BLK_DEV_BSG
27	help
28	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
29	  any other SCSI device under Linux, say Y and make sure that you know
30	  the name of your SCSI host adapter (the card inside your computer
31	  that "speaks" the SCSI protocol, also called SCSI controller),
32	  because you will be asked for it.
33
34	  You also need to say Y here if you have a device which speaks
35	  the SCSI protocol.  Examples of this include the parallel port
36	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
37	  Channel, and FireWire storage.
38
39	  To compile this driver as a module, choose M here and read
40	  <file:Documentation/scsi/scsi.rst>.
41	  The module will be called scsi_mod.
42
43	  However, do not compile this as a module if your root file system
44	  (the one containing the directory /) is located on a SCSI device.
45
46config SCSI_DMA
47	bool
48	default n
49
50config SCSI_ESP_PIO
51	bool
52
53config SCSI_NETLINK
54	bool
55	default	n
56	depends on NET
57
58config SCSI_PROC_FS
59	bool "legacy /proc/scsi/ support"
60	depends on SCSI && PROC_FS
61	default y
62	help
63	  This option enables support for the various files in
64	  /proc/scsi.  In Linux 2.6 this has been superseded by
65	  files in sysfs but many legacy applications rely on this.
66
67	  If unsure say Y.
68
69comment "SCSI support type (disk, tape, CD-ROM)"
70	depends on SCSI
71
72config BLK_DEV_SD
73	tristate "SCSI disk support"
74	depends on SCSI
75	select BLK_DEV_INTEGRITY_T10 if BLK_DEV_INTEGRITY
76	help
77	  If you want to use SCSI hard disks, Fibre Channel disks,
78	  Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
79	  USB storage or the SCSI or parallel port version of
80	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
81	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from
82	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
83	  CD-ROMs.
84
85	  To compile this driver as a module, choose M here and read
86	  <file:Documentation/scsi/scsi.rst>.
87	  The module will be called sd_mod.
88
89	  Do not compile this driver as a module if your root file system
90	  (the one containing the directory /) is located on a SCSI disk.
91	  In this case, do not compile the driver for your SCSI host adapter
92	  (below) as a module either.
93
94config CHR_DEV_ST
95	tristate "SCSI tape support"
96	depends on SCSI
97	help
98	  If you want to use a SCSI tape drive under Linux, say Y and read the
99	  SCSI-HOWTO, available from
100	  <http://www.tldp.org/docs.html#howto>, and
101	  <file:Documentation/scsi/st.rst> in the kernel source.  This is NOT
102	  for SCSI CD-ROMs.
103
104	  To compile this driver as a module, choose M here and read
105	  <file:Documentation/scsi/scsi.rst>. The module will be called st.
106
107config BLK_DEV_SR
108	tristate "SCSI CDROM support"
109	depends on SCSI && BLK_DEV
110	select CDROM
111	help
112	  If you want to use a CD or DVD drive attached to your computer
113	  by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
114	  and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
115
116	  Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
117
118	  To compile this driver as a module, choose M here and read
119	  <file:Documentation/scsi/scsi.rst>.
120	  The module will be called sr_mod.
121
122config CHR_DEV_SG
123	tristate "SCSI generic support"
124	depends on SCSI
125	help
126	  If you want to use SCSI scanners, synthesizers or CD-writers or just
127	  about anything having "SCSI" in its name other than hard disks,
128	  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
129	  directly, so you need some additional software which knows how to
130	  talk to these devices using the SCSI protocol:
131
132	  For scanners, look at SANE (<http://www.sane-project.org/>). For CD
133	  writer software look at Cdrtools
134	  (<http://cdrtools.sourceforge.net/>)
135	  and for burning a "disk at once": CDRDAO
136	  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
137	  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
138	  For other devices, it's possible that you'll have to write the
139	  driver software yourself. Please read the file
140	  <file:Documentation/scsi/scsi-generic.rst> for more information.
141
142	  To compile this driver as a module, choose M here and read
143	  <file:Documentation/scsi/scsi.rst>. The module will be called sg.
144
145	  If unsure, say N.
146
147config BLK_DEV_BSG
148	bool "/dev/bsg support (SG v4)"
149	depends on SCSI
150	default y
151	help
152	  Saying Y here will enable generic SG (SCSI generic) v4 support
153	  for any SCSI device.
154
155	  This option is required by UDEV to access device serial numbers, etc.
156
157	  If unsure, say Y.
158
159config CHR_DEV_SCH
160	tristate "SCSI media changer support"
161	depends on SCSI
162	help
163	  This is a driver for SCSI media changers.  Most common devices are
164	  tape libraries and MOD/CDROM jukeboxes.  *Real* jukeboxes, you
165	  don't need this for those tiny 6-slot cdrom changers.  Media
166	  changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
167	  If you have such hardware and want to use it with linux, say Y
168	  here.  Check <file:Documentation/scsi/scsi-changer.rst> for details.
169
170	  If you want to compile this as a module ( = code which can be
171	  inserted in and removed from the running kernel whenever you want),
172	  say M here and read <file:Documentation/kbuild/modules.rst> and
173	  <file:Documentation/scsi/scsi.rst>. The module will be called ch.o.
174	  If unsure, say N.
175
176config SCSI_ENCLOSURE
177	tristate "SCSI Enclosure Support"
178	depends on SCSI && ENCLOSURE_SERVICES
179	depends on m || SCSI_SAS_ATTRS != m
180	help
181	  Enclosures are devices sitting on or in SCSI backplanes that
182	  manage devices.  If you have a disk cage, the chances are that
183	  it has an enclosure device.  Selecting this option will just allow
184	  certain enclosure conditions to be reported and is not required.
185
186config SCSI_CONSTANTS
187	bool "Verbose SCSI error reporting (kernel size += 36K)"
188	depends on SCSI
189	help
190	  The error messages regarding your SCSI hardware will be easier to
191	  understand if you say Y here; it will enlarge your kernel by about
192	  36 KB. If in doubt, say Y.
193
194config SCSI_LOGGING
195	bool "SCSI logging facility"
196	depends on SCSI
197	help
198	  This turns on a logging facility that can be used to debug a number
199	  of SCSI related problems.
200
201	  If you say Y here, no logging output will appear by default, but you
202	  can enable logging by saying Y to "/proc file system support" and
203	  "Sysctl support" below and executing the command
204
205	  echo <bitmask> > /proc/sys/dev/scsi/logging_level
206
207	  where <bitmask> is a four byte value representing the logging type
208	  and logging level for each type of logging selected.
209
210	  There are a number of logging types and you can find them in the
211	  source at <file:drivers/scsi/scsi_logging.h>. The logging levels
212	  are also described in that file and they determine the verbosity of
213	  the logging for each logging type.
214
215	  If you say N here, it may be harder to track down some types of SCSI
216	  problems. If you say Y here your kernel will be somewhat larger, but
217	  there should be no noticeable performance impact as long as you have
218	  logging turned off.
219
220config SCSI_SCAN_ASYNC
221	bool "Asynchronous SCSI scanning"
222	depends on SCSI
223	help
224	  The SCSI subsystem can probe for devices while the rest of the
225	  system continues booting, and even probe devices on different
226	  busses in parallel, leading to a significant speed-up.
227
228	  You can override this choice by specifying "scsi_mod.scan=sync"
229	  or async on the kernel's command line.
230
231	  Note that this setting also affects whether resuming from
232	  system suspend will be performed asynchronously.
233
234menu "SCSI Transports"
235	depends on SCSI
236
237config SCSI_SPI_ATTRS
238	tristate "Parallel SCSI (SPI) Transport Attributes"
239	depends on SCSI
240	help
241	  If you wish to export transport-specific information about
242	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
243
244config SCSI_FC_ATTRS
245	tristate "FiberChannel Transport Attributes"
246	depends on SCSI && NET
247	select BLK_DEV_BSGLIB
248	select SCSI_NETLINK
249	help
250	  If you wish to export transport-specific information about
251	  each attached FiberChannel device to sysfs, say Y.
252	  Otherwise, say N.
253
254config SCSI_ISCSI_ATTRS
255	tristate "iSCSI Transport Attributes"
256	depends on SCSI && NET
257	select BLK_DEV_BSGLIB
258	help
259	  If you wish to export transport-specific information about
260	  each attached iSCSI device to sysfs, say Y.
261	  Otherwise, say N.
262
263config SCSI_SAS_ATTRS
264	tristate "SAS Transport Attributes"
265	depends on SCSI
266	select BLK_DEV_BSGLIB
267	help
268	  If you wish to export transport-specific information about
269	  each attached SAS device to sysfs, say Y.
270
271source "drivers/scsi/libsas/Kconfig"
272
273config SCSI_SRP_ATTRS
274	tristate "SRP Transport Attributes"
275	depends on SCSI
276	help
277	  If you wish to export transport-specific information about
278	  each attached SRP device to sysfs, say Y.
279
280endmenu
281
282menuconfig SCSI_LOWLEVEL
283	bool "SCSI low-level drivers"
284	depends on SCSI!=n
285	default y
286
287if SCSI_LOWLEVEL && SCSI
288
289config ISCSI_TCP
290	tristate "iSCSI Initiator over TCP/IP"
291	depends on SCSI && INET
292	select CRYPTO
293	select CRYPTO_MD5
294	select CRYPTO_CRC32C
295	select SCSI_ISCSI_ATTRS
296	help
297	 The iSCSI Driver provides a host with the ability to access storage
298	 through an IP network. The driver uses the iSCSI protocol to transport
299	 SCSI requests and responses over a TCP/IP network between the host
300	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
301	 combines with the host's TCP/IP stack, network drivers, and Network
302	 Interface Card (NIC) to provide the same functions as a SCSI or a
303	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
304
305	 To compile this driver as a module, choose M here: the
306	 module will be called iscsi_tcp.
307
308	 The userspace component needed to initialize the driver, documentation,
309	 and sample configuration files can be found here:
310
311	 http://open-iscsi.org
312
313config ISCSI_BOOT_SYSFS
314	tristate "iSCSI Boot Sysfs Interface"
315	default	n
316	help
317	  This option enables support for exposing iSCSI boot information
318	  via sysfs to userspace. If you wish to export this information,
319	  say Y. Otherwise, say N.
320
321source "drivers/scsi/cxgbi/Kconfig"
322source "drivers/scsi/bnx2i/Kconfig"
323source "drivers/scsi/bnx2fc/Kconfig"
324source "drivers/scsi/be2iscsi/Kconfig"
325source "drivers/scsi/cxlflash/Kconfig"
326
327config SGIWD93_SCSI
328	tristate "SGI WD93C93 SCSI Driver"
329	depends on SGI_HAS_WD93 && SCSI
330	help
331	  If you have a Western Digital WD93 SCSI controller on
332	  an SGI MIPS system, say Y.  Otherwise, say N.
333
334config BLK_DEV_3W_XXXX_RAID
335	tristate "3ware 5/6/7/8xxx ATA-RAID support"
336	depends on PCI && SCSI
337	help
338	  3ware is the only hardware ATA-Raid product in Linux to date.
339	  This card is 2,4, or 8 channel master mode support only.
340	  SCSI support required!!!
341
342	  <http://www.3ware.com/>
343
344	  Please read the comments at the top of
345	  <file:drivers/scsi/3w-xxxx.c>.
346
347config SCSI_HPSA
348	tristate "HP Smart Array SCSI driver"
349	depends on PCI && SCSI
350	select CHECK_SIGNATURE
351	select SCSI_SAS_ATTRS
352	help
353	  This driver supports HP Smart Array Controllers (circa 2009).
354	  It is a SCSI alternative to the cciss driver, which is a block
355	  driver.  Anyone wishing to use HP Smart Array controllers who
356	  would prefer the devices be presented to linux as SCSI devices,
357	  rather than as generic block devices should say Y here.
358
359config SCSI_3W_9XXX
360	tristate "3ware 9xxx SATA-RAID support"
361	depends on PCI && SCSI
362	help
363	  This driver supports the 9000 series 3ware SATA-RAID cards.
364
365	  <http://www.amcc.com>
366
367	  Please read the comments at the top of
368	  <file:drivers/scsi/3w-9xxx.c>.
369
370config SCSI_3W_SAS
371	tristate "3ware 97xx SAS/SATA-RAID support"
372	depends on PCI && SCSI
373	help
374	  This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
375
376	  <http://www.lsi.com>
377
378	  Please read the comments at the top of
379	  <file:drivers/scsi/3w-sas.c>.
380
381config SCSI_ACARD
382	tristate "ACARD SCSI support"
383	depends on PCI && SCSI
384	help
385	  This driver supports the ACARD SCSI host adapter.
386	  Support Chip <ATP870 ATP876 ATP880 ATP885>
387	  To compile this driver as a module, choose M here: the
388	  module will be called atp870u.
389
390config SCSI_AHA152X
391	tristate "Adaptec AHA152X/2825 support"
392	depends on ISA && SCSI
393	select SCSI_SPI_ATTRS
394	select CHECK_SIGNATURE
395	help
396	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
397	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
398	  must be manually specified in this case.
399
400	  It is explained in section 3.3 of the SCSI-HOWTO, available from
401	  <http://www.tldp.org/docs.html#howto>. You might also want to
402	  read the file <file:Documentation/scsi/aha152x.rst>.
403
404	  To compile this driver as a module, choose M here: the
405	  module will be called aha152x.
406
407config SCSI_AHA1542
408	tristate "Adaptec AHA1542 support"
409	depends on ISA && SCSI && ISA_DMA_API
410	help
411	  This is support for a SCSI host adapter.  It is explained in section
412	  3.4 of the SCSI-HOWTO, available from
413	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
414	  purchased by Adaptec, and some former Trantor products are being
415	  sold under the Adaptec name.  If it doesn't work out of the box, you
416	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
417
418	  To compile this driver as a module, choose M here: the
419	  module will be called aha1542.
420
421config SCSI_AHA1740
422	tristate "Adaptec AHA1740 support"
423	depends on EISA && SCSI
424	help
425	  This is support for a SCSI host adapter.  It is explained in section
426	  3.5 of the SCSI-HOWTO, available from
427	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
428	  of the box, you may have to change some settings in
429	  <file:drivers/scsi/aha1740.h>.
430
431	  To compile this driver as a module, choose M here: the
432	  module will be called aha1740.
433
434config SCSI_AACRAID
435	tristate "Adaptec AACRAID support"
436	depends on SCSI && PCI
437	help
438	  This driver supports a variety of Dell, HP, Adaptec, IBM and
439	  ICP storage products. For a list of supported products, refer
440	  to <file:Documentation/scsi/aacraid.rst>.
441
442	  To compile this driver as a module, choose M here: the module
443	  will be called aacraid.
444
445
446source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
447source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
448source "drivers/scsi/aic94xx/Kconfig"
449source "drivers/scsi/hisi_sas/Kconfig"
450source "drivers/scsi/mvsas/Kconfig"
451
452config SCSI_MVUMI
453	tristate "Marvell UMI driver"
454	depends on SCSI && PCI
455	help
456	  Module for Marvell Universal Message Interface(UMI) driver
457
458	  To compile this driver as a module, choose M here: the
459	  module will be called mvumi.
460
461config SCSI_ADVANSYS
462	tristate "AdvanSys SCSI support"
463	depends on SCSI
464	depends on ISA || EISA || PCI
465	depends on ISA_DMA_API || !ISA
466	help
467	  This is a driver for all SCSI host adapters manufactured by
468	  AdvanSys. It is documented in the kernel source in
469	  <file:drivers/scsi/advansys.c>.
470
471	  To compile this driver as a module, choose M here: the
472	  module will be called advansys.
473
474config SCSI_ARCMSR
475	tristate "ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter"
476	depends on PCI && SCSI
477	help
478	  This driver supports all of ARECA's SATA/SAS RAID controller cards.
479	  This is an ARECA-maintained driver by Erich Chen.
480	  If you have any problems, please mail to: <erich@areca.com.tw>.
481	  Areca supports Linux RAID config tools.
482	  Please link <http://www.areca.com.tw>
483
484	  To compile this driver as a module, choose M here: the
485	  module will be called arcmsr (modprobe arcmsr).
486
487source "drivers/scsi/esas2r/Kconfig"
488source "drivers/scsi/megaraid/Kconfig.megaraid"
489source "drivers/scsi/mpt3sas/Kconfig"
490source "drivers/scsi/mpi3mr/Kconfig"
491source "drivers/scsi/smartpqi/Kconfig"
492
493config SCSI_HPTIOP
494	tristate "HighPoint RocketRAID 3xxx/4xxx Controller support"
495	depends on SCSI && PCI
496	help
497	  This option enables support for HighPoint RocketRAID 3xxx/4xxx
498	  controllers.
499
500	  To compile this driver as a module, choose M here; the module
501	  will be called hptiop. If unsure, say N.
502
503config SCSI_BUSLOGIC
504	tristate "BusLogic SCSI support"
505	depends on PCI && SCSI
506	help
507	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
508	  Adapters. Consult the SCSI-HOWTO, available from
509	  <http://www.tldp.org/docs.html#howto>, and the files
510	  <file:Documentation/scsi/BusLogic.rst> and
511	  <file:Documentation/scsi/FlashPoint.rst> for more information.
512	  Note that support for FlashPoint is only available for 32-bit
513	  x86 configurations.
514
515	  To compile this driver as a module, choose M here: the
516	  module will be called BusLogic.
517
518config SCSI_FLASHPOINT
519	bool "FlashPoint support"
520	depends on SCSI_BUSLOGIC && PCI
521	help
522	  This option allows you to add FlashPoint support to the
523	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
524	  substantial, so users of MultiMaster Host Adapters may not
525	  wish to include it.
526
527config SCSI_MYRB
528	tristate "Mylex DAC960/DAC1100 PCI RAID Controller (Block Interface)"
529	depends on PCI
530	select RAID_ATTRS
531	help
532	  This driver adds support for the Mylex DAC960, AcceleRAID, and
533	  eXtremeRAID PCI RAID controllers. This driver supports the
534	  older, block based interface.
535	  This driver is a reimplementation of the original DAC960
536	  driver. If you have used the DAC960 driver you should enable
537	  this module.
538
539	  To compile this driver as a module, choose M here: the
540	  module will be called myrb.
541
542config SCSI_MYRS
543	tristate "Mylex DAC960/DAC1100 PCI RAID Controller (SCSI Interface)"
544	depends on PCI
545	depends on !CPU_BIG_ENDIAN || COMPILE_TEST
546	select RAID_ATTRS
547	help
548	  This driver adds support for the Mylex DAC960, AcceleRAID, and
549	  eXtremeRAID PCI RAID controllers.  This driver supports the
550	  newer, SCSI-based interface only.
551	  This driver is a reimplementation of the original DAC960
552	  driver. If you have used the DAC960 driver you should enable
553	  this module.
554
555	  To compile this driver as a module, choose M here: the
556	  module will be called myrs.
557
558config VMWARE_PVSCSI
559	tristate "VMware PVSCSI driver support"
560	depends on PCI && SCSI && X86
561	help
562	  This driver supports VMware's para virtualized SCSI HBA.
563	  To compile this driver as a module, choose M here: the
564	  module will be called vmw_pvscsi.
565
566config XEN_SCSI_FRONTEND
567	tristate "XEN SCSI frontend driver"
568	depends on SCSI && XEN
569	select XEN_XENBUS_FRONTEND
570	help
571	  The XEN SCSI frontend driver allows the kernel to access SCSI Devices
572	  within another guest OS (usually Dom0).
573	  Only needed if the kernel is running in a XEN guest and generic
574	  SCSI access to a device is needed.
575
576config HYPERV_STORAGE
577	tristate "Microsoft Hyper-V virtual storage driver"
578	depends on SCSI && HYPERV
579	depends on m || SCSI_FC_ATTRS != m
580	default HYPERV
581	help
582	  Select this option to enable the Hyper-V virtual storage driver.
583
584config LIBFC
585	tristate "LibFC module"
586	depends on SCSI_FC_ATTRS
587	select CRC32
588	help
589	  Fibre Channel library module
590
591config LIBFCOE
592	tristate "LibFCoE module"
593	depends on LIBFC
594	help
595	  Library for Fibre Channel over Ethernet module
596
597config FCOE
598	tristate "FCoE module"
599	depends on PCI
600	depends on LIBFCOE
601	help
602	  Fibre Channel over Ethernet module
603
604config FCOE_FNIC
605	tristate "Cisco FNIC Driver"
606	depends on PCI && X86
607	depends on LIBFCOE
608	help
609	  This is support for the Cisco PCI-Express FCoE HBA.
610
611	  To compile this driver as a module, choose M here and read
612	  <file:Documentation/scsi/scsi.rst>.
613	  The module will be called fnic.
614
615config SCSI_SNIC
616	tristate "Cisco SNIC Driver"
617	depends on PCI && SCSI
618	help
619	  This is support for the Cisco PCI-Express SCSI HBA.
620
621	  To compile this driver as a module, choose M here and read
622	  <file:Documentation/scsi/scsi.rst>.
623	  The module will be called snic.
624
625config SCSI_SNIC_DEBUG_FS
626	bool "Cisco SNIC Driver Debugfs Support"
627	depends on SCSI_SNIC && DEBUG_FS
628	help
629	  This enables to list debugging information from SNIC Driver
630	  available via debugfs file system
631
632config SCSI_DMX3191D
633	tristate "DMX3191D SCSI support"
634	depends on PCI && SCSI
635	select SCSI_SPI_ATTRS
636	help
637	  This is support for Domex DMX3191D SCSI Host Adapters.
638
639	  To compile this driver as a module, choose M here: the
640	  module will be called dmx3191d.
641
642config SCSI_FDOMAIN
643	tristate
644	depends on SCSI
645
646config SCSI_FDOMAIN_PCI
647	tristate "Future Domain TMC-3260/AHA-2920A PCI SCSI support"
648	depends on PCI && SCSI
649	select SCSI_FDOMAIN
650	help
651	  This is support for Future Domain's PCI SCSI host adapters (TMC-3260)
652	  and other adapters with PCI bus based on the Future Domain chipsets
653	  (Adaptec AHA-2920A).
654
655	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
656	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
657	  controller support"). This Future Domain driver works with the older
658	  Adaptec AHA-2920A boards with a Future Domain chip on them.
659
660	  To compile this driver as a module, choose M here: the
661	  module will be called fdomain_pci.
662
663config SCSI_FDOMAIN_ISA
664	tristate "Future Domain 16xx ISA SCSI support"
665	depends on ISA && SCSI
666	select CHECK_SIGNATURE
667	select SCSI_FDOMAIN
668	help
669	  This is support for Future Domain's 16-bit SCSI host adapters
670	  (TMC-1660/1680, TMC-1650/1670, TMC-1610M/MER/MEX) and other adapters
671	  with ISA bus based on the Future Domain chipsets (Quantum ISA-200S,
672	  ISA-250MG; and at least one IBM board).
673
674	  To compile this driver as a module, choose M here: the
675	  module will be called fdomain_isa.
676
677config SCSI_ISCI
678	tristate "Intel(R) C600 Series Chipset SAS Controller"
679	depends on PCI && SCSI
680	depends on X86
681	select SCSI_SAS_LIBSAS
682	help
683	  This driver supports the 6Gb/s SAS capabilities of the storage
684	  control unit found in the Intel(R) C600 series chipset.
685
686config SCSI_GENERIC_NCR5380
687	tristate "Generic NCR5380/53c400 SCSI ISA card support"
688	depends on ISA && SCSI && HAS_IOPORT_MAP
689	select SCSI_SPI_ATTRS
690	help
691	  This is a driver for old ISA card SCSI controllers based on a
692	  NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device.
693	  Most boards such as the Trantor T130 fit this category, as do
694	  various 8-bit and 16-bit ISA cards bundled with SCSI scanners.
695
696	  To compile this driver as a module, choose M here: the
697	  module will be called g_NCR5380.
698
699config SCSI_IPS
700	tristate "IBM ServeRAID support"
701	depends on PCI && SCSI
702	help
703	  This is support for the IBM ServeRAID hardware RAID controllers.
704	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
705	  and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
706	  for more information.  If this driver does not work correctly
707	  without modification please contact the author by email at
708	  <ipslinux@adaptec.com>.
709
710	  To compile this driver as a module, choose M here: the
711	  module will be called ips.
712
713config SCSI_IBMVSCSI
714	tristate "IBM Virtual SCSI support"
715	depends on PPC_PSERIES
716	select SCSI_SRP_ATTRS
717	help
718	  This is the IBM POWER Virtual SCSI Client
719
720	  To compile this driver as a module, choose M here: the
721	  module will be called ibmvscsi.
722
723config SCSI_IBMVSCSIS
724	tristate "IBM Virtual SCSI Server support"
725	depends on PPC_PSERIES && TARGET_CORE && SCSI && PCI
726	help
727	  This is the IBM POWER Virtual SCSI Target Server
728	  This driver uses the SRP protocol for communication between servers
729	  guest and/or the host that run on the same server.
730	  More information on VSCSI protocol can be found at www.power.org
731
732	  The userspace configuration needed to initialize the driver can be
733	  be found here:
734
735	  https://github.com/powervm/ibmvscsis/wiki/Configuration
736
737	  To compile this driver as a module, choose M here: the
738	  module will be called ibmvscsis.
739
740config SCSI_IBMVFC
741	tristate "IBM Virtual FC support"
742	depends on PPC_PSERIES && SCSI
743	depends on SCSI_FC_ATTRS
744	help
745	  This is the IBM POWER Virtual FC Client
746
747	  To compile this driver as a module, choose M here: the
748	  module will be called ibmvfc.
749
750config SCSI_IBMVFC_TRACE
751	bool "enable driver internal trace"
752	depends on SCSI_IBMVFC
753	default y
754	help
755	  If you say Y here, the driver will trace all commands issued
756	  to the adapter. Performance impact is minimal. Trace can be
757	  dumped using /sys/class/scsi_host/hostXX/trace.
758
759config SCSI_INITIO
760	tristate "Initio 9100U(W) support"
761	depends on PCI && SCSI
762	help
763	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
764	  read the SCSI-HOWTO, available from
765	  <http://www.tldp.org/docs.html#howto>.
766
767	  To compile this driver as a module, choose M here: the
768	  module will be called initio.
769
770config SCSI_INIA100
771	tristate "Initio INI-A100U2W support"
772	depends on PCI && SCSI
773	help
774	  This is support for the Initio INI-A100U2W SCSI host adapter.
775	  Please read the SCSI-HOWTO, available from
776	  <http://www.tldp.org/docs.html#howto>.
777
778	  To compile this driver as a module, choose M here: the
779	  module will be called a100u2w.
780
781config SCSI_PPA
782	tristate "IOMEGA parallel port (ppa - older drives)"
783	depends on SCSI && PARPORT_PC
784	help
785	  This driver supports older versions of IOMEGA's parallel port ZIP
786	  drive (a 100 MB removable media device).
787
788	  Note that you can say N here if you have the SCSI version of the ZIP
789	  drive: it will be supported automatically if you said Y to the
790	  generic "SCSI disk support", above.
791
792	  If you have the ZIP Plus drive or a more recent parallel port ZIP
793	  drive (if the supplied cable with the drive is labeled "AutoDetect")
794	  then you should say N here and Y to "IOMEGA parallel port (imm -
795	  newer drives)", below.
796
797	  For more information about this driver and how to use it you should
798	  read the file <file:Documentation/scsi/ppa.rst>.  You should also read
799	  the SCSI-HOWTO, which is available from
800	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
801	  you will still be able to use the parallel port for other tasks,
802	  such as a printer; it is safe to compile both drivers into the
803	  kernel.
804
805	  To compile this driver as a module, choose M here: the
806	  module will be called ppa.
807
808config SCSI_IMM
809	tristate "IOMEGA parallel port (imm - newer drives)"
810	depends on SCSI && PARPORT_PC
811	help
812	  This driver supports newer versions of IOMEGA's parallel port ZIP
813	  drive (a 100 MB removable media device).
814
815	  Note that you can say N here if you have the SCSI version of the ZIP
816	  drive: it will be supported automatically if you said Y to the
817	  generic "SCSI disk support", above.
818
819	  If you have the ZIP Plus drive or a more recent parallel port ZIP
820	  drive (if the supplied cable with the drive is labeled "AutoDetect")
821	  then you should say Y here; if you have an older ZIP drive, say N
822	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
823
824	  For more information about this driver and how to use it you should
825	  read the file <file:Documentation/scsi/ppa.rst>.  You should also read
826	  the SCSI-HOWTO, which is available from
827	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
828	  you will still be able to use the parallel port for other tasks,
829	  such as a printer; it is safe to compile both drivers into the
830	  kernel.
831
832	  To compile this driver as a module, choose M here: the
833	  module will be called imm.
834
835config SCSI_IZIP_EPP16
836	bool "ppa/imm option - Use slow (but safe) EPP-16"
837	depends on SCSI_PPA || SCSI_IMM
838	help
839	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
840	  allows them to act as expansion buses that can handle up to 64
841	  peripheral devices.
842
843	  Some parallel port chipsets are slower than their motherboard, and
844	  so we have to control the state of the chipset's FIFO queue every
845	  now and then to avoid data loss. This will be done if you say Y
846	  here.
847
848	  Generally, saying Y is the safe option and slows things down a bit.
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 && ATA
974	select SATA_HOST
975	select FW_LOADER
976	select IRQ_POLL
977	select SGL_ALLOC
978	help
979	  This driver supports the IBM Power Linux family RAID adapters.
980	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
981	  as IBM iSeries 5702, 5703, 5709, and 570A.
982
983config SCSI_IPR_TRACE
984	bool "enable driver internal trace"
985	depends on SCSI_IPR
986	default y
987	help
988	  If you say Y here, the driver will trace all commands issued
989	  to the adapter. Performance impact is minimal. Trace can be
990	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
991
992config SCSI_IPR_DUMP
993	bool "enable adapter dump support"
994	depends on SCSI_IPR
995	default y
996	help
997	  If you say Y here, the driver will support adapter crash dump.
998	  If you enable this support, the iprdump daemon can be used
999	  to capture adapter failure analysis information.
1000
1001config SCSI_ZALON
1002	tristate "Zalon SCSI support"
1003	depends on GSC && SCSI
1004	select SCSI_SPI_ATTRS
1005	help
1006	  The Zalon is a GSC/HSC bus interface chip that sits between the
1007	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
1008	  C110, J200, J210 and some D, K & R-class machines.  It's also
1009	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
1010	  Say Y here if you have one of these machines or cards.
1011
1012config SCSI_NCR53C8XX_DEFAULT_TAGS
1013	int "default tagged command queue depth"
1014	depends on SCSI_ZALON
1015	default "8"
1016	help
1017	  "Tagged command queuing" is a feature of SCSI-2 which improves
1018	  performance: the host adapter can send several SCSI commands to a
1019	  device's queue even if previous commands haven't finished yet.
1020	  Because the device is intelligent, it can optimize its operations
1021	  (like head positioning) based on its own request queue. Some SCSI
1022	  devices don't implement this properly; if you want to disable this
1023	  feature, enter 0 or 1 here (it doesn't matter which).
1024
1025	  The default value is 8 and should be supported by most hard disks.
1026	  This value can be overridden from the boot command line using the
1027	  'tags' option as follows (example):
1028	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
1029	  4, set queue depth to 16 for target 2 and target 3 on controller 0
1030	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
1031
1032	  The normal answer therefore is to go with the default 8 and to use
1033	  a boot command line option for devices that need to use a different
1034	  command queue depth.
1035
1036	  There is no safe option other than using good SCSI devices.
1037
1038config SCSI_NCR53C8XX_MAX_TAGS
1039	int "maximum number of queued commands"
1040	depends on SCSI_ZALON
1041	default "32"
1042	help
1043	  This option allows you to specify the maximum number of commands
1044	  that can be queued to any device, when tagged command queuing is
1045	  possible. The default value is 32. Minimum is 2, maximum is 64.
1046	  Modern hard disks are able to support 64 tags and even more, but
1047	  do not seem to be faster when more than 32 tags are being used.
1048
1049	  So, the normal answer here is to go with the default value 32 unless
1050	  you are using very large hard disks with large cache (>= 1 MB) that
1051	  are able to take advantage of more than 32 tagged commands.
1052
1053	  There is no safe option and the default answer is recommended.
1054
1055config SCSI_NCR53C8XX_SYNC
1056	int "synchronous transfers frequency in MHz"
1057	depends on SCSI_ZALON
1058	default "20"
1059	help
1060	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
1061	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
1062	  are respectively the maximum data transfer rates in mega-transfers
1063	  per second for each class.  For example, a FAST-20 Wide 16 device is
1064	  able to transfer data at 20 million 16 bit packets per second for a
1065	  total rate of 40 MB/s.
1066
1067	  You may specify 0 if you want to only use asynchronous data
1068	  transfers. This is the safest and slowest option. Otherwise, specify
1069	  a value between 5 and 80, depending on the capability of your SCSI
1070	  controller.  The higher the number, the faster the data transfer.
1071	  Note that 80 should normally be ok since the driver decreases the
1072	  value automatically according to the controller's capabilities.
1073
1074	  Your answer to this question is ignored for controllers with NVRAM,
1075	  since the driver will get this information from the user set-up.  It
1076	  also can be overridden using a boot setup option, as follows
1077	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
1078	  for FAST-20 synchronous data transfer (20 mega-transfers per
1079	  second).
1080
1081	  The normal answer therefore is not to go with the default but to
1082	  select the maximum value 80 allowing the driver to use the maximum
1083	  value supported by each controller. If this causes problems with
1084	  your SCSI devices, you should come back and decrease the value.
1085
1086	  There is no safe option other than using good cabling, right
1087	  terminations and SCSI conformant devices.
1088
1089config SCSI_NCR53C8XX_NO_DISCONNECT
1090	bool "not allow targets to disconnect"
1091	depends on SCSI_ZALON && SCSI_NCR53C8XX_DEFAULT_TAGS=0
1092	help
1093	  This option is only provided for safety if you suspect some SCSI
1094	  device of yours to not support properly the target-disconnect
1095	  feature. In that case, you would say Y here. In general however, to
1096	  not allow targets to disconnect is not reasonable if there is more
1097	  than 1 device on a SCSI bus. The normal answer therefore is N.
1098
1099config SCSI_QLOGIC_FAS
1100	tristate "Qlogic FAS SCSI support"
1101	depends on ISA && SCSI
1102	help
1103	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
1104	  FastSCSI! cards as well as any other card based on the FASXX chip
1105	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
1106
1107	  This driver does NOT support the PCI versions of these cards. The
1108	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
1109	  SCSI support"), below.
1110
1111	  Information about this driver is contained in
1112	  <file:Documentation/scsi/qlogicfas.rst>.  You should also read the
1113	  SCSI-HOWTO, available from
1114	  <http://www.tldp.org/docs.html#howto>.
1115
1116	  To compile this driver as a module, choose M here: the
1117	  module will be called qlogicfas.
1118
1119config SCSI_QLOGIC_1280
1120	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
1121	depends on PCI && SCSI
1122	help
1123	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
1124
1125	  To compile this driver as a module, choose M here: the
1126	  module will be called qla1280.
1127
1128config SCSI_QLOGICPTI
1129	tristate "PTI Qlogic, ISP Driver"
1130	depends on SBUS && SCSI
1131	help
1132	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
1133	  controllers are known under Solaris as qpti and in the openprom as
1134	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
1135	  driven by a different driver.
1136
1137	  To compile this driver as a module, choose M here: the
1138	  module will be called qlogicpti.
1139
1140source "drivers/scsi/qla2xxx/Kconfig"
1141source "drivers/scsi/qla4xxx/Kconfig"
1142source "drivers/scsi/qedi/Kconfig"
1143source "drivers/scsi/qedf/Kconfig"
1144
1145config SCSI_LPFC
1146	tristate "Emulex LightPulse Fibre Channel Support"
1147	depends on PCI && SCSI
1148	depends on CPU_FREQ
1149	depends on SCSI_FC_ATTRS
1150	depends on NVME_TARGET_FC || NVME_TARGET_FC=n
1151	depends on NVME_FC || NVME_FC=n
1152	select CRC_T10DIF
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 && 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
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
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
1527