xref: /openbmc/linux/drivers/block/Kconfig (revision b5f184fbdb03b4fcc1141de34dd5ec964ca5d99e)
1# SPDX-License-Identifier: GPL-2.0
2#
3# Block device driver configuration
4#
5
6menuconfig BLK_DEV
7	bool "Block devices"
8	depends on BLOCK
9	default y
10	help
11	  Say Y here to get to see options for various different block device
12	  drivers. This option alone does not add any kernel code.
13
14	  If you say N, all options in this submenu will be skipped and disabled;
15	  only do this if you know what you are doing.
16
17if BLK_DEV
18
19source "drivers/block/null_blk/Kconfig"
20
21config BLK_DEV_FD
22	tristate "Normal floppy disk support"
23	depends on ARCH_MAY_HAVE_PC_FDC
24	help
25	  If you want to use the floppy disk drive(s) of your PC under Linux,
26	  say Y. Information about this driver, especially important for IBM
27	  Thinkpad users, is contained in
28	  <file:Documentation/admin-guide/blockdev/floppy.rst>.
29	  That file also contains the location of the Floppy driver FAQ as
30	  well as location of the fdutils package used to configure additional
31	  parameters of the driver at run time.
32
33	  To compile this driver as a module, choose M here: the
34	  module will be called floppy.
35
36config AMIGA_FLOPPY
37	tristate "Amiga floppy support"
38	depends on AMIGA
39
40config ATARI_FLOPPY
41	tristate "Atari floppy support"
42	depends on ATARI
43
44config MAC_FLOPPY
45	tristate "Support for PowerMac floppy"
46	depends on PPC_PMAC && !PPC_PMAC64
47	help
48	  If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
49	  floppy controller, say Y here. Most commonly found in PowerMacs.
50
51config BLK_DEV_SWIM
52	tristate "Support for SWIM Macintosh floppy"
53	depends on M68K && MAC
54	help
55	  You should select this option if you want floppy support
56	  and you don't have a II, IIfx, Q900, Q950 or AV series.
57
58config AMIGA_Z2RAM
59	tristate "Amiga Zorro II ramdisk support"
60	depends on ZORRO
61	help
62	  This enables support for using Chip RAM and Zorro II RAM as a
63	  ramdisk or as a swap partition. Say Y if you want to include this
64	  driver in the kernel.
65
66	  To compile this driver as a module, choose M here: the
67	  module will be called z2ram.
68
69config CDROM
70	tristate
71	select BLK_SCSI_REQUEST
72
73config GDROM
74	tristate "SEGA Dreamcast GD-ROM drive"
75	depends on SH_DREAMCAST
76	select CDROM
77	help
78	  A standard SEGA Dreamcast comes with a modified CD ROM drive called a
79	  "GD-ROM" by SEGA to signify it is capable of reading special disks
80	  with up to 1 GB of data. This drive will also read standard CD ROM
81	  disks. Select this option to access any disks in your GD ROM drive.
82	  Most users will want to say "Y" here.
83	  You can also build this as a module which will be called gdrom.
84
85config PARIDE
86	tristate "Parallel port IDE device support"
87	depends on PARPORT_PC
88	help
89	  There are many external CD-ROM and disk devices that connect through
90	  your computer's parallel port. Most of them are actually IDE devices
91	  using a parallel port IDE adapter. This option enables the PARIDE
92	  subsystem which contains drivers for many of these external drives.
93	  Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
94
95	  If you have said Y to the "Parallel-port support" configuration
96	  option, you may share a single port between your printer and other
97	  parallel port devices. Answer Y to build PARIDE support into your
98	  kernel, or M if you would like to build it as a loadable module. If
99	  your parallel port support is in a loadable module, you must build
100	  PARIDE as a module. If you built PARIDE support into your kernel,
101	  you may still build the individual protocol modules and high-level
102	  drivers as loadable modules. If you build this support as a module,
103	  it will be called paride.
104
105	  To use the PARIDE support, you must say Y or M here and also to at
106	  least one high-level driver (e.g. "Parallel port IDE disks",
107	  "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
108	  to at least one protocol driver (e.g. "ATEN EH-100 protocol",
109	  "MicroSolutions backpack protocol", "DataStor Commuter protocol"
110	  etc.).
111
112source "drivers/block/paride/Kconfig"
113
114source "drivers/block/mtip32xx/Kconfig"
115
116source "drivers/block/zram/Kconfig"
117
118config BLK_DEV_UMEM
119	tristate "Micro Memory MM5415 Battery Backed RAM support"
120	depends on PCI
121	help
122	  Saying Y here will include support for the MM5415 family of
123	  battery backed (Non-volatile) RAM cards.
124	  <http://www.umem.com/>
125
126	  The cards appear as block devices that can be partitioned into
127	  as many as 15 partitions.
128
129	  To compile this driver as a module, choose M here: the
130	  module will be called umem.
131
132	  The umem driver has not yet been allocated a MAJOR number, so
133	  one is chosen dynamically.
134
135config BLK_DEV_UBD
136	bool "Virtual block device"
137	depends on UML
138	help
139          The User-Mode Linux port includes a driver called UBD which will let
140          you access arbitrary files on the host computer as block devices.
141          Unless you know that you do not need such virtual block devices say
142          Y here.
143
144config BLK_DEV_UBD_SYNC
145	bool "Always do synchronous disk IO for UBD"
146	depends on BLK_DEV_UBD
147	help
148	  Writes to the virtual block device are not immediately written to the
149	  host's disk; this may cause problems if, for example, the User-Mode
150	  Linux 'Virtual Machine' uses a journalling filesystem and the host
151	  computer crashes.
152
153          Synchronous operation (i.e. always writing data to the host's disk
154          immediately) is configurable on a per-UBD basis by using a special
155          kernel command line option.  Alternatively, you can say Y here to
156          turn on synchronous operation by default for all block devices.
157
158          If you're running a journalling file system (like reiserfs, for
159          example) in your virtual machine, you will want to say Y here.  If
160          you care for the safety of the data in your virtual machine, Y is a
161          wise choice too.  In all other cases (for example, if you're just
162          playing around with User-Mode Linux) you can choose N.
163
164config BLK_DEV_COW_COMMON
165	bool
166	default BLK_DEV_UBD
167
168config BLK_DEV_LOOP
169	tristate "Loopback device support"
170	help
171	  Saying Y here will allow you to use a regular file as a block
172	  device; you can then create a file system on that block device and
173	  mount it just as you would mount other block devices such as hard
174	  drive partitions, CD-ROM drives or floppy drives. The loop devices
175	  are block special device files with major number 7 and typically
176	  called /dev/loop0, /dev/loop1 etc.
177
178	  This is useful if you want to check an ISO 9660 file system before
179	  burning the CD, or if you want to use floppy images without first
180	  writing them to floppy. Furthermore, some Linux distributions avoid
181	  the need for a dedicated Linux partition by keeping their complete
182	  root file system inside a DOS FAT file using this loop device
183	  driver.
184
185	  To use the loop device, you need the losetup utility, found in the
186	  util-linux package, see
187	  <https://www.kernel.org/pub/linux/utils/util-linux/>.
188
189	  The loop device driver can also be used to "hide" a file system in
190	  a disk partition, floppy, or regular file, either using encryption
191	  (scrambling the data) or steganography (hiding the data in the low
192	  bits of, say, a sound file). This is also safe if the file resides
193	  on a remote file server.
194
195	  There are several ways of encrypting disks. Some of these require
196	  kernel patches. The vanilla kernel offers the cryptoloop option
197	  and a Device Mapper target (which is superior, as it supports all
198	  file systems). If you want to use the cryptoloop, say Y to both
199	  LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
200	  or later) version of util-linux. Additionally, be aware that
201	  the cryptoloop is not safe for storing journaled filesystems.
202
203	  Note that this loop device has nothing to do with the loopback
204	  device used for network connections from the machine to itself.
205
206	  To compile this driver as a module, choose M here: the
207	  module will be called loop.
208
209	  Most users will answer N here.
210
211config BLK_DEV_LOOP_MIN_COUNT
212	int "Number of loop devices to pre-create at init time"
213	depends on BLK_DEV_LOOP
214	default 8
215	help
216	  Static number of loop devices to be unconditionally pre-created
217	  at init time.
218
219	  This default value can be overwritten on the kernel command
220	  line or with module-parameter loop.max_loop.
221
222	  The historic default is 8. If a late 2011 version of losetup(8)
223	  is used, it can be set to 0, since needed loop devices can be
224	  dynamically allocated with the /dev/loop-control interface.
225
226config BLK_DEV_CRYPTOLOOP
227	tristate "Cryptoloop Support"
228	select CRYPTO
229	select CRYPTO_CBC
230	depends on BLK_DEV_LOOP
231	help
232	  Say Y here if you want to be able to use the ciphers that are
233	  provided by the CryptoAPI as loop transformation. This might be
234	  used as hard disk encryption.
235
236	  WARNING: This device is not safe for journaled file systems like
237	  ext3 or Reiserfs. Please use the Device Mapper crypto module
238	  instead, which can be configured to be on-disk compatible with the
239	  cryptoloop device.
240
241source "drivers/block/drbd/Kconfig"
242
243config BLK_DEV_NBD
244	tristate "Network block device support"
245	depends on NET
246	help
247	  Saying Y here will allow your computer to be a client for network
248	  block devices, i.e. it will be able to use block devices exported by
249	  servers (mount file systems on them etc.). Communication between
250	  client and server works over TCP/IP networking, but to the client
251	  program this is hidden: it looks like a regular local file access to
252	  a block device special file such as /dev/nd0.
253
254	  Network block devices also allows you to run a block-device in
255	  userland (making server and client physically the same computer,
256	  communicating using the loopback network device).
257
258	  Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
259	  especially about where to find the server code, which runs in user
260	  space and does not need special kernel support.
261
262	  Note that this has nothing to do with the network file systems NFS
263	  or Coda; you can say N here even if you intend to use NFS or Coda.
264
265	  To compile this driver as a module, choose M here: the
266	  module will be called nbd.
267
268	  If unsure, say N.
269
270config BLK_DEV_SX8
271	tristate "Promise SATA SX8 support"
272	depends on PCI
273	help
274	  Saying Y or M here will enable support for the
275	  Promise SATA SX8 controllers.
276
277	  Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
278
279config BLK_DEV_RAM
280	tristate "RAM block device support"
281	help
282	  Saying Y here will allow you to use a portion of your RAM memory as
283	  a block device, so that you can make file systems on it, read and
284	  write to it and do all the other things that you can do with normal
285	  block devices (such as hard drives). It is usually used to load and
286	  store a copy of a minimal root file system off of a floppy into RAM
287	  during the initial install of Linux.
288
289	  Note that the kernel command line option "ramdisk=XX" is now obsolete.
290	  For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
291
292	  To compile this driver as a module, choose M here: the
293	  module will be called brd. An alias "rd" has been defined
294	  for historical reasons.
295
296	  Most normal users won't need the RAM disk functionality, and can
297	  thus say N here.
298
299config BLK_DEV_RAM_COUNT
300	int "Default number of RAM disks"
301	default "16"
302	depends on BLK_DEV_RAM
303	help
304	  The default value is 16 RAM disks. Change this if you know what you
305	  are doing. If you boot from a filesystem that needs to be extracted
306	  in memory, you will need at least one RAM disk (e.g. root on cramfs).
307
308config BLK_DEV_RAM_SIZE
309	int "Default RAM disk size (kbytes)"
310	depends on BLK_DEV_RAM
311	default "4096"
312	help
313	  The default value is 4096 kilobytes. Only change this if you know
314	  what you are doing.
315
316config CDROM_PKTCDVD
317	tristate "Packet writing on CD/DVD media (DEPRECATED)"
318	depends on !UML
319	select CDROM
320	select BLK_SCSI_REQUEST
321	help
322	  Note: This driver is deprecated and will be removed from the
323	  kernel in the near future!
324
325	  If you have a CDROM/DVD drive that supports packet writing, say
326	  Y to include support. It should work with any MMC/Mt Fuji
327	  compliant ATAPI or SCSI drive, which is just about any newer
328	  DVD/CD writer.
329
330	  Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
331	  is possible.
332	  DVD-RW disks must be in restricted overwrite mode.
333
334	  See the file <file:Documentation/cdrom/packet-writing.rst>
335	  for further information on the use of this driver.
336
337	  To compile this driver as a module, choose M here: the
338	  module will be called pktcdvd.
339
340config CDROM_PKTCDVD_BUFFERS
341	int "Free buffers for data gathering"
342	depends on CDROM_PKTCDVD
343	default "8"
344	help
345	  This controls the maximum number of active concurrent packets. More
346	  concurrent packets can increase write performance, but also require
347	  more memory. Each concurrent packet will require approximately 64Kb
348	  of non-swappable kernel memory, memory which will be allocated when
349	  a disc is opened for writing.
350
351config CDROM_PKTCDVD_WCACHE
352	bool "Enable write caching"
353	depends on CDROM_PKTCDVD
354	help
355	  If enabled, write caching will be set for the CD-R/W device. For now
356	  this option is dangerous unless the CD-RW media is known good, as we
357	  don't do deferred write error handling yet.
358
359config ATA_OVER_ETH
360	tristate "ATA over Ethernet support"
361	depends on NET
362	help
363	This driver provides Support for ATA over Ethernet block
364	devices like the Coraid EtherDrive (R) Storage Blade.
365
366config SUNVDC
367	tristate "Sun Virtual Disk Client support"
368	depends on SUN_LDOMS
369	help
370	  Support for virtual disk devices as a client under Sun
371	  Logical Domains.
372
373source "drivers/s390/block/Kconfig"
374
375config XILINX_SYSACE
376	tristate "Xilinx SystemACE support"
377	depends on 4xx || MICROBLAZE
378	help
379	  Include support for the Xilinx SystemACE CompactFlash interface
380
381config XEN_BLKDEV_FRONTEND
382	tristate "Xen virtual block device support"
383	depends on XEN
384	default y
385	select XEN_XENBUS_FRONTEND
386	help
387	  This driver implements the front-end of the Xen virtual
388	  block device driver.  It communicates with a back-end driver
389	  in another domain which drives the actual block device.
390
391config XEN_BLKDEV_BACKEND
392	tristate "Xen block-device backend driver"
393	depends on XEN_BACKEND
394	help
395	  The block-device backend driver allows the kernel to export its
396	  block devices to other guests via a high-performance shared-memory
397	  interface.
398
399	  The corresponding Linux frontend driver is enabled by the
400	  CONFIG_XEN_BLKDEV_FRONTEND configuration option.
401
402	  The backend driver attaches itself to a any block device specified
403	  in the XenBus configuration. There are no limits to what the block
404	  device as long as it has a major and minor.
405
406	  If you are compiling a kernel to run in a Xen block backend driver
407	  domain (often this is domain 0) you should say Y here. To
408	  compile this driver as a module, chose M here: the module
409	  will be called xen-blkback.
410
411
412config VIRTIO_BLK
413	tristate "Virtio block driver"
414	depends on VIRTIO
415	help
416	  This is the virtual block driver for virtio.  It can be used with
417          QEMU based VMMs (like KVM or Xen).  Say Y or M.
418
419config BLK_DEV_RBD
420	tristate "Rados block device (RBD)"
421	depends on INET && BLOCK
422	select CEPH_LIB
423	select LIBCRC32C
424	select CRYPTO_AES
425	select CRYPTO
426	help
427	  Say Y here if you want include the Rados block device, which stripes
428	  a block device over objects stored in the Ceph distributed object
429	  store.
430
431	  More information at http://ceph.newdream.net/.
432
433	  If unsure, say N.
434
435config BLK_DEV_RSXX
436	tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
437	depends on PCI
438	select CRC32
439	help
440	  Device driver for IBM's high speed PCIe SSD
441	  storage device: Flash Adapter 900GB Full Height.
442
443	  To compile this driver as a module, choose M here: the
444	  module will be called rsxx.
445
446source "drivers/block/rnbd/Kconfig"
447
448endif # BLK_DEV
449