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