]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blame - drivers/block/Kconfig
drivers/block/mtip32xx/mtip32xx.c:1726:5: sparse: symbol 'mtip_send_trim' was not...
[mirror_ubuntu-bionic-kernel.git] / drivers / block / Kconfig
CommitLineData
1da177e4
LT
1#
2# Block device driver configuration
3#
4
fd11d171
JE
5menuconfig BLK_DEV
6 bool "Block devices"
7 depends on BLOCK
8 default y
06bfb7eb
JE
9 ---help---
10 Say Y here to get to see options for various different block device
11 drivers. This option alone does not add any kernel code.
12
13 If you say N, all options in this submenu will be skipped and disabled;
14 only do this if you know what you are doing.
9361401e 15
fd11d171 16if BLK_DEV
1da177e4
LT
17
18config BLK_DEV_FD
19 tristate "Normal floppy disk support"
a08b6b79 20 depends on ARCH_MAY_HAVE_PC_FDC
1da177e4
LT
21 ---help---
22 If you want to use the floppy disk drive(s) of your PC under Linux,
23 say Y. Information about this driver, especially important for IBM
31c00fc1
RD
24 Thinkpad users, is contained in
25 <file:Documentation/blockdev/floppy.txt>.
1da177e4
LT
26 That file also contains the location of the Floppy driver FAQ as
27 well as location of the fdutils package used to configure additional
28 parameters of the driver at run time.
29
30 To compile this driver as a module, choose M here: the
31 module will be called floppy.
32
33config AMIGA_FLOPPY
34 tristate "Amiga floppy support"
35 depends on AMIGA
36
37config ATARI_FLOPPY
38 tristate "Atari floppy support"
39 depends on ATARI
40
1da177e4
LT
41config MAC_FLOPPY
42 tristate "Support for PowerMac floppy"
43 depends on PPC_PMAC && !PPC_PMAC64
44 help
45 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
46 floppy controller, say Y here. Most commonly found in PowerMacs.
47
8852ecd9
LV
48config BLK_DEV_SWIM
49 tristate "Support for SWIM Macintosh floppy"
50 depends on M68K && MAC
51 help
52 You should select this option if you want floppy support
53 and you don't have a II, IIfx, Q900, Q950 or AV series.
54
1da177e4
LT
55config AMIGA_Z2RAM
56 tristate "Amiga Zorro II ramdisk support"
57 depends on ZORRO
58 help
59 This enables support for using Chip RAM and Zorro II RAM as a
60 ramdisk or as a swap partition. Say Y if you want to include this
61 driver in the kernel.
62
63 To compile this driver as a module, choose M here: the
64 module will be called z2ram.
65
1da177e4
LT
66config BLK_DEV_XD
67 tristate "XT hard disk support"
a5532606 68 depends on ISA && ISA_DMA_API
928923c7 69 select CHECK_SIGNATURE
1da177e4
LT
70 help
71 Very old 8 bit hard disk controllers used in the IBM XT computer
72 will be supported if you say Y here.
73
74 To compile this driver as a module, choose M here: the
75 module will be called xd.
76
77 It's pretty unlikely that you have one of these: say N.
78
2395e463
RD
79config GDROM
80 tristate "SEGA Dreamcast GD-ROM drive"
81 depends on SH_DREAMCAST
82 help
83 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
84 "GD-ROM" by SEGA to signify it is capable of reading special disks
85 with up to 1 GB of data. This drive will also read standard CD ROM
86 disks. Select this option to access any disks in your GD ROM drive.
87 Most users will want to say "Y" here.
88 You can also build this as a module which will be called gdrom.
89
1da177e4
LT
90config PARIDE
91 tristate "Parallel port IDE device support"
6a19b41b 92 depends on PARPORT_PC
1da177e4
LT
93 ---help---
94 There are many external CD-ROM and disk devices that connect through
95 your computer's parallel port. Most of them are actually IDE devices
96 using a parallel port IDE adapter. This option enables the PARIDE
97 subsystem which contains drivers for many of these external drives.
31c00fc1 98 Read <file:Documentation/blockdev/paride.txt> for more information.
1da177e4
LT
99
100 If you have said Y to the "Parallel-port support" configuration
101 option, you may share a single port between your printer and other
102 parallel port devices. Answer Y to build PARIDE support into your
103 kernel, or M if you would like to build it as a loadable module. If
104 your parallel port support is in a loadable module, you must build
105 PARIDE as a module. If you built PARIDE support into your kernel,
106 you may still build the individual protocol modules and high-level
107 drivers as loadable modules. If you build this support as a module,
108 it will be called paride.
109
110 To use the PARIDE support, you must say Y or M here and also to at
111 least one high-level driver (e.g. "Parallel port IDE disks",
112 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
113 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
114 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
115 etc.).
116
117source "drivers/block/paride/Kconfig"
118
88523a61
SB
119source "drivers/block/mtip32xx/Kconfig"
120
1da177e4
LT
121config BLK_CPQ_DA
122 tristate "Compaq SMART2 support"
f057eac0 123 depends on PCI && VIRT_TO_BUS
1da177e4
LT
124 help
125 This is the driver for Compaq Smart Array controllers. Everyone
126 using these boards should say Y here. See the file
31c00fc1
RD
127 <file:Documentation/blockdev/cpqarray.txt> for the current list of
128 boards supported by this driver, and for further information on the
129 use of this driver.
1da177e4
LT
130
131config BLK_CPQ_CISS_DA
132 tristate "Compaq Smart Array 5xxx support"
133 depends on PCI
b7010ede 134 select CHECK_SIGNATURE
1da177e4
LT
135 help
136 This is the driver for Compaq Smart Array 5xxx controllers.
137 Everyone using these boards should say Y here.
31c00fc1 138 See <file:Documentation/blockdev/cciss.txt> for the current list of
1da177e4
LT
139 boards supported by this driver, and for further information
140 on the use of this driver.
141
142config CISS_SCSI_TAPE
143 bool "SCSI tape drive support for Smart Array 5xxx"
3e29fe83
RD
144 depends on BLK_CPQ_CISS_DA && PROC_FS
145 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
1da177e4
LT
146 help
147 When enabled (Y), this option allows SCSI tape drives and SCSI medium
148 changers (tape robots) to be accessed via a Compaq 5xxx array
31c00fc1 149 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
1da177e4
LT
150
151 "SCSI support" and "SCSI tape support" must also be enabled for this
152 option to work.
153
154 When this option is disabled (N), the SCSI portion of the driver
155 is not compiled.
156
157config BLK_DEV_DAC960
158 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
159 depends on PCI
160 help
161 This driver adds support for the Mylex DAC960, AcceleRAID, and
162 eXtremeRAID PCI RAID controllers. See the file
31c00fc1
RD
163 <file:Documentation/blockdev/README.DAC960> for further information
164 about this driver.
1da177e4
LT
165
166 To compile this driver as a module, choose M here: the
167 module will be called DAC960.
168
169config BLK_DEV_UMEM
b8977285
KC
170 tristate "Micro Memory MM5415 Battery Backed RAM support"
171 depends on PCI
1da177e4
LT
172 ---help---
173 Saying Y here will include support for the MM5415 family of
174 battery backed (Non-volatile) RAM cards.
175 <http://www.umem.com/>
176
177 The cards appear as block devices that can be partitioned into
178 as many as 15 partitions.
179
180 To compile this driver as a module, choose M here: the
181 module will be called umem.
182
183 The umem driver has not yet been allocated a MAJOR number, so
bf6ee0ae 184 one is chosen dynamically.
1da177e4
LT
185
186config BLK_DEV_UBD
187 bool "Virtual block device"
188 depends on UML
189 ---help---
190 The User-Mode Linux port includes a driver called UBD which will let
191 you access arbitrary files on the host computer as block devices.
192 Unless you know that you do not need such virtual block devices say
193 Y here.
194
195config BLK_DEV_UBD_SYNC
196 bool "Always do synchronous disk IO for UBD"
197 depends on BLK_DEV_UBD
198 ---help---
199 Writes to the virtual block device are not immediately written to the
200 host's disk; this may cause problems if, for example, the User-Mode
201 Linux 'Virtual Machine' uses a journalling filesystem and the host
202 computer crashes.
203
204 Synchronous operation (i.e. always writing data to the host's disk
205 immediately) is configurable on a per-UBD basis by using a special
206 kernel command line option. Alternatively, you can say Y here to
207 turn on synchronous operation by default for all block devices.
208
209 If you're running a journalling file system (like reiserfs, for
210 example) in your virtual machine, you will want to say Y here. If
211 you care for the safety of the data in your virtual machine, Y is a
212 wise choice too. In all other cases (for example, if you're just
213 playing around with User-Mode Linux) you can choose N.
214
215config BLK_DEV_COW_COMMON
216 bool
217 default BLK_DEV_UBD
218
1da177e4
LT
219config BLK_DEV_LOOP
220 tristate "Loopback device support"
221 ---help---
222 Saying Y here will allow you to use a regular file as a block
223 device; you can then create a file system on that block device and
224 mount it just as you would mount other block devices such as hard
225 drive partitions, CD-ROM drives or floppy drives. The loop devices
226 are block special device files with major number 7 and typically
227 called /dev/loop0, /dev/loop1 etc.
228
229 This is useful if you want to check an ISO 9660 file system before
230 burning the CD, or if you want to use floppy images without first
231 writing them to floppy. Furthermore, some Linux distributions avoid
232 the need for a dedicated Linux partition by keeping their complete
233 root file system inside a DOS FAT file using this loop device
234 driver.
235
236 To use the loop device, you need the losetup utility, found in the
237 util-linux package, see
238 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
239
240 The loop device driver can also be used to "hide" a file system in
241 a disk partition, floppy, or regular file, either using encryption
242 (scrambling the data) or steganography (hiding the data in the low
243 bits of, say, a sound file). This is also safe if the file resides
244 on a remote file server.
245
246 There are several ways of encrypting disks. Some of these require
247 kernel patches. The vanilla kernel offers the cryptoloop option
248 and a Device Mapper target (which is superior, as it supports all
249 file systems). If you want to use the cryptoloop, say Y to both
250 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
251 or later) version of util-linux. Additionally, be aware that
252 the cryptoloop is not safe for storing journaled filesystems.
253
254 Note that this loop device has nothing to do with the loopback
255 device used for network connections from the machine to itself.
256
257 To compile this driver as a module, choose M here: the
258 module will be called loop.
259
260 Most users will answer N here.
261
d134b00b
KS
262config BLK_DEV_LOOP_MIN_COUNT
263 int "Number of loop devices to pre-create at init time"
264 depends on BLK_DEV_LOOP
265 default 8
266 help
267 Static number of loop devices to be unconditionally pre-created
268 at init time.
269
270 This default value can be overwritten on the kernel command
271 line or with module-parameter loop.max_loop.
272
273 The historic default is 8. If a late 2011 version of losetup(8)
274 is used, it can be set to 0, since needed loop devices can be
275 dynamically allocated with the /dev/loop-control interface.
276
1da177e4
LT
277config BLK_DEV_CRYPTOLOOP
278 tristate "Cryptoloop Support"
279 select CRYPTO
8df3b0a2 280 select CRYPTO_CBC
1da177e4
LT
281 depends on BLK_DEV_LOOP
282 ---help---
283 Say Y here if you want to be able to use the ciphers that are
284 provided by the CryptoAPI as loop transformation. This might be
285 used as hard disk encryption.
286
287 WARNING: This device is not safe for journaled file systems like
288 ext3 or Reiserfs. Please use the Device Mapper crypto module
289 instead, which can be configured to be on-disk compatible with the
290 cryptoloop device.
291
b411b363
PR
292source "drivers/block/drbd/Kconfig"
293
1da177e4
LT
294config BLK_DEV_NBD
295 tristate "Network block device support"
296 depends on NET
297 ---help---
298 Saying Y here will allow your computer to be a client for network
299 block devices, i.e. it will be able to use block devices exported by
300 servers (mount file systems on them etc.). Communication between
301 client and server works over TCP/IP networking, but to the client
302 program this is hidden: it looks like a regular local file access to
303 a block device special file such as /dev/nd0.
304
305 Network block devices also allows you to run a block-device in
306 userland (making server and client physically the same computer,
307 communicating using the loopback network device).
308
31c00fc1
RD
309 Read <file:Documentation/blockdev/nbd.txt> for more information,
310 especially about where to find the server code, which runs in user
311 space and does not need special kernel support.
1da177e4
LT
312
313 Note that this has nothing to do with the network file systems NFS
314 or Coda; you can say N here even if you intend to use NFS or Coda.
315
316 To compile this driver as a module, choose M here: the
317 module will be called nbd.
318
319 If unsure, say N.
320
b60503ba
MW
321config BLK_DEV_NVME
322 tristate "NVM Express block device"
323 depends on PCI
324 ---help---
325 The NVM Express driver is for solid state drives directly
326 connected to the PCI or PCI Express bus. If you know you
327 don't have one of these, it is safe to answer N.
328
329 To compile this driver as a module, choose M here: the
330 module will be called nvme.
331
2a13877c
JG
332config BLK_DEV_OSD
333 tristate "OSD object-as-blkdev support"
334 depends on SCSI_OSD_ULD
335 ---help---
336 Saying Y or M here will allow the exporting of a single SCSI
337 OSD (object-based storage) object as a Linux block device.
338
339 For example, if you create a 2G object on an OSD device,
340 you can then use this module to present that 2G object as
341 a Linux block device.
342
343 To compile this driver as a module, choose M here: the
344 module will be called osdblk.
345
346 If unsure, say N.
347
1da177e4
LT
348config BLK_DEV_SX8
349 tristate "Promise SATA SX8 support"
350 depends on PCI
351 ---help---
352 Saying Y or M here will enable support for the
353 Promise SATA SX8 controllers.
354
355 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
1da177e4
LT
356
357config BLK_DEV_RAM
9db5579b 358 tristate "RAM block device support"
1da177e4
LT
359 ---help---
360 Saying Y here will allow you to use a portion of your RAM memory as
361 a block device, so that you can make file systems on it, read and
362 write to it and do all the other things that you can do with normal
363 block devices (such as hard drives). It is usually used to load and
364 store a copy of a minimal root file system off of a floppy into RAM
365 during the initial install of Linux.
366
31c00fc1
RD
367 Note that the kernel command line option "ramdisk=XX" is now obsolete.
368 For details, read <file:Documentation/blockdev/ramdisk.txt>.
1da177e4
LT
369
370 To compile this driver as a module, choose M here: the
371 module will be called rd.
372
373 Most normal users won't need the RAM disk functionality, and can
374 thus say N here.
375
376config BLK_DEV_RAM_COUNT
a687fb18 377 int "Default number of RAM disks"
1da177e4 378 default "16"
a687fb18 379 depends on BLK_DEV_RAM
1da177e4 380 help
2e977c85 381 The default value is 16 RAM disks. Change this if you know what you
1da177e4
LT
382 are doing. If you boot from a filesystem that needs to be extracted
383 in memory, you will need at least one RAM disk (e.g. root on cramfs).
384
385config BLK_DEV_RAM_SIZE
386 int "Default RAM disk size (kbytes)"
387 depends on BLK_DEV_RAM
388 default "4096"
389 help
390 The default value is 4096 kilobytes. Only change this if you know
2e977c85 391 what you are doing.
1da177e4 392
75acb9cd
NP
393config BLK_DEV_XIP
394 bool "Support XIP filesystems on RAM block device"
395 depends on BLK_DEV_RAM
396 default n
397 help
398 Support XIP filesystems (such as ext2 with XIP support on) on
399 top of block ram device. This will slightly enlarge the kernel, and
400 will prevent RAM block device backing store memory from being
401 allocated from highmem (only a problem for highmem systems).
402
1da177e4
LT
403config CDROM_PKTCDVD
404 tristate "Packet writing on CD/DVD media"
405 depends on !UML
406 help
2d4eeec5
TM
407 If you have a CDROM/DVD drive that supports packet writing, say
408 Y to include support. It should work with any MMC/Mt Fuji
409 compliant ATAPI or SCSI drive, which is just about any newer
410 DVD/CD writer.
1da177e4 411
2d4eeec5
TM
412 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
413 is possible.
1da177e4
LT
414 DVD-RW disks must be in restricted overwrite mode.
415
2d4eeec5
TM
416 See the file <file:Documentation/cdrom/packet-writing.txt>
417 for further information on the use of this driver.
418
1da177e4
LT
419 To compile this driver as a module, choose M here: the
420 module will be called pktcdvd.
421
422config CDROM_PKTCDVD_BUFFERS
423 int "Free buffers for data gathering"
424 depends on CDROM_PKTCDVD
425 default "8"
426 help
427 This controls the maximum number of active concurrent packets. More
428 concurrent packets can increase write performance, but also require
429 more memory. Each concurrent packet will require approximately 64Kb
e1bc89bc
PO
430 of non-swappable kernel memory, memory which will be allocated when
431 a disc is opened for writing.
1da177e4
LT
432
433config CDROM_PKTCDVD_WCACHE
b8977285
KC
434 bool "Enable write caching"
435 depends on CDROM_PKTCDVD
1da177e4
LT
436 help
437 If enabled, write caching will be set for the CD-R/W device. For now
438 this option is dangerous unless the CD-RW media is known good, as we
439 don't do deferred write error handling yet.
440
1da177e4
LT
441config ATA_OVER_ETH
442 tristate "ATA over Ethernet support"
443 depends on NET
444 help
445 This driver provides Support for ATA over Ethernet block
446 devices like the Coraid EtherDrive (R) Storage Blade.
447
3fbed4c6
K
448config MG_DISK
449 tristate "mGine mflash, gflash support"
8a11a789 450 depends on ARM && GPIOLIB
3fbed4c6
K
451 help
452 mGine mFlash(gFlash) block device driver
453
454config MG_DISK_RES
455 int "Size of reserved area before MBR"
456 depends on MG_DISK
457 default 0
458 help
459 Define size of reserved area that usually used for boot. Unit is KB.
460 All of the block device operation will be taken this value as start
461 offset
462 Examples:
463 1024 => 1 MB
464
667ef3c3
DM
465config SUNVDC
466 tristate "Sun Virtual Disk Client support"
467 depends on SUN_LDOMS
468 help
469 Support for virtual disk devices as a client under Sun
470 Logical Domains.
471
61d48c2c
MS
472source "drivers/s390/block/Kconfig"
473
74489a91
GL
474config XILINX_SYSACE
475 tristate "Xilinx SystemACE support"
6fa612b5 476 depends on 4xx || MICROBLAZE
74489a91
GL
477 help
478 Include support for the Xilinx SystemACE CompactFlash interface
479
9f27ee59
JF
480config XEN_BLKDEV_FRONTEND
481 tristate "Xen virtual block device support"
482 depends on XEN
483 default y
2de06cc1 484 select XEN_XENBUS_FRONTEND
9f27ee59
JF
485 help
486 This driver implements the front-end of the Xen virtual
487 block device driver. It communicates with a back-end driver
488 in another domain which drives the actual block device.
489
dfc07b13 490config XEN_BLKDEV_BACKEND
ea5e1161 491 tristate "Xen block-device backend driver"
dfc07b13
KRW
492 depends on XEN_BACKEND
493 help
494 The block-device backend driver allows the kernel to export its
495 block devices to other guests via a high-performance shared-memory
496 interface.
497
a4c34858
KRW
498 The corresponding Linux frontend driver is enabled by the
499 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
500
501 The backend driver attaches itself to a any block device specified
502 in the XenBus configuration. There are no limits to what the block
503 device as long as it has a major and minor.
504
505 If you are compiling a kernel to run in a Xen block backend driver
506 domain (often this is domain 0) you should say Y here. To
507 compile this driver as a module, chose M here: the module
508 will be called xen-blkback.
509
510
e467cde2 511config VIRTIO_BLK
b8977285
KC
512 tristate "Virtio block driver"
513 depends on VIRTIO
e467cde2 514 ---help---
0ad07ec1
AL
515 This is the virtual block driver for virtio. It can be used with
516 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
e467cde2 517
453ea3ed 518config BLK_DEV_HD
f327c1c3 519 bool "Very old hard disk (MFM/RLL/IDE) driver"
453ea3ed
AB
520 depends on HAVE_IDE
521 depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
522 help
f327c1c3
AB
523 This is a very old hard disk driver that lacks the enhanced
524 functionality of the newer ones.
525
526 It is required for systems with ancient MFM/RLL/ESDI drives.
527
528 If unsure, say N.
453ea3ed 529
602adf40
YS
530config BLK_DEV_RBD
531 tristate "Rados block device (RBD)"
b8977285 532 depends on INET && BLOCK
602adf40
YS
533 select CEPH_LIB
534 select LIBCRC32C
535 select CRYPTO_AES
536 select CRYPTO
537 default n
538 help
539 Say Y here if you want include the Rados block device, which stripes
540 a block device over objects stored in the Ceph distributed object
541 store.
542
543 More information at http://ceph.newdream.net/.
544
545 If unsure, say N.
546
fd11d171 547endif # BLK_DEV