add dts config

hc

2023-12-06 08f87f769b595151be1afeff53e144f543faa614

 kernel/drivers/block/Kconfig
..
..
@@ -7,7 +7,7 @@
7
7
 	bool "Block devices"
8
8
 	depends on BLOCK
9
9
 	default y
10
-	---help---
10
+	help
11
11
 	  Say Y here to get to see options for various different block device
12
12
 	  drivers. This option alone does not add any kernel code.
13
13
 
..
..
@@ -27,17 +27,33 @@
27
27
 config BLK_DEV_FD
28
28
 	tristate "Normal floppy disk support"
29
29
 	depends on ARCH_MAY_HAVE_PC_FDC
30
-	---help---
30
+	help
31
31
 	  If you want to use the floppy disk drive(s) of your PC under Linux,
32
32
 	  say Y. Information about this driver, especially important for IBM
33
33
 	  Thinkpad users, is contained in
34
-	  <file:Documentation/blockdev/floppy.txt>.
34
+	  <file:Documentation/admin-guide/blockdev/floppy.rst>.
35
35
 	  That file also contains the location of the Floppy driver FAQ as
36
36
 	  well as location of the fdutils package used to configure additional
37
37
 	  parameters of the driver at run time.
38
38
 
39
39
 	  To compile this driver as a module, choose M here: the
40
40
 	  module will be called floppy.
41
+
42
+config BLK_DEV_FD_RAWCMD
43
+	bool "Support for raw floppy disk commands (DEPRECATED)"
44
+	depends on BLK_DEV_FD
45
+	help
46
+	  If you want to use actual physical floppies and expect to do
47
+	  special low-level hardware accesses to them (access and use
48
+	  non-standard formats, for example), then enable this.
49
+
50
+	  Note that the code enabled by this option is rarely used and
51
+	  might be unstable or insecure, and distros should not enable it.
52
+
53
+	  Note: FDRAWCMD is deprecated and will be removed from the kernel
54
+	  in the near future.
55
+
56
+	  If unsure, say N.
41
57
 
42
58
 config AMIGA_FLOPPY
43
59
 	tristate "Amiga floppy support"
..
..
@@ -91,12 +107,12 @@
91
107
 config PARIDE
92
108
 	tristate "Parallel port IDE device support"
93
109
 	depends on PARPORT_PC
94
-	---help---
110
+	help
95
111
 	  There are many external CD-ROM and disk devices that connect through
96
112
 	  your computer's parallel port. Most of them are actually IDE devices
97
113
 	  using a parallel port IDE adapter. This option enables the PARIDE
98
114
 	  subsystem which contains drivers for many of these external drives.
99
-	  Read <file:Documentation/blockdev/paride.txt> for more information.
115
+	  Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
100
116
 
101
117
 	  If you have said Y to the "Parallel-port support" configuration
102
118
 	  option, you may share a single port between your printer and other
..
..
@@ -121,22 +137,10 @@
121
137
 
122
138
 source "drivers/block/zram/Kconfig"
123
139
 
124
-config BLK_DEV_DAC960
125
-	tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
126
-	depends on PCI
127
-	help
128
-	  This driver adds support for the Mylex DAC960, AcceleRAID, and
129
-	  eXtremeRAID PCI RAID controllers.  See the file
130
-	  <file:Documentation/blockdev/README.DAC960> for further information
131
-	  about this driver.
132
-
133
-	  To compile this driver as a module, choose M here: the
134
-	  module will be called DAC960.
135
-
136
140
 config BLK_DEV_UMEM
137
141
 	tristate "Micro Memory MM5415 Battery Backed RAM support"
138
142
 	depends on PCI
139
-	---help---
143
+	help
140
144
 	  Saying Y here will include support for the MM5415 family of
141
145
 	  battery backed (Non-volatile) RAM cards.
142
146
 	  <http://www.umem.com/>
..
..
@@ -153,7 +157,7 @@
153
157
 config BLK_DEV_UBD
154
158
 	bool "Virtual block device"
155
159
 	depends on UML
156
-	---help---
160
+	help
157
161
           The User-Mode Linux port includes a driver called UBD which will let
158
162
           you access arbitrary files on the host computer as block devices.
159
163
           Unless you know that you do not need such virtual block devices say
..
..
@@ -162,7 +166,7 @@
162
166
 config BLK_DEV_UBD_SYNC
163
167
 	bool "Always do synchronous disk IO for UBD"
164
168
 	depends on BLK_DEV_UBD
165
-	---help---
169
+	help
166
170
 	  Writes to the virtual block device are not immediately written to the
167
171
 	  host's disk; this may cause problems if, for example, the User-Mode
168
172
 	  Linux 'Virtual Machine' uses a journalling filesystem and the host
..
..
@@ -185,7 +189,7 @@
185
189
 
186
190
 config BLK_DEV_LOOP
187
191
 	tristate "Loopback device support"
188
-	---help---
192
+	help
189
193
 	  Saying Y here will allow you to use a regular file as a block
190
194
 	  device; you can then create a file system on that block device and
191
195
 	  mount it just as you would mount other block devices such as hard
..
..
@@ -246,7 +250,7 @@
246
250
 	select CRYPTO
247
251
 	select CRYPTO_CBC
248
252
 	depends on BLK_DEV_LOOP
249
-	---help---
253
+	help
250
254
 	  Say Y here if you want to be able to use the ciphers that are 
251
255
 	  provided by the CryptoAPI as loop transformation. This might be
252
256
 	  used as hard disk encryption.
..
..
@@ -261,7 +265,7 @@
261
265
 config BLK_DEV_NBD
262
266
 	tristate "Network block device support"
263
267
 	depends on NET
264
-	---help---
268
+	help
265
269
 	  Saying Y here will allow your computer to be a client for network
266
270
 	  block devices, i.e. it will be able to use block devices exported by
267
271
 	  servers (mount file systems on them etc.). Communication between
..
..
@@ -273,7 +277,7 @@
273
277
 	  userland (making server and client physically the same computer,
274
278
 	  communicating using the loopback network device).
275
279
 
276
-	  Read <file:Documentation/blockdev/nbd.txt> for more information,
280
+	  Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
277
281
 	  especially about where to find the server code, which runs in user
278
282
 	  space and does not need special kernel support.
279
283
 
..
..
@@ -289,7 +293,7 @@
289
293
 	tristate "STEC S1120 Block Driver"
290
294
 	depends on PCI
291
295
 	depends on 64BIT
292
-	---help---
296
+	help
293
297
 	Saying Y or M here will enable support for the
294
298
 	STEC, Inc. S1120 PCIe SSD.
295
299
 
..
..
@@ -298,7 +302,7 @@
298
302
 config BLK_DEV_SX8
299
303
 	tristate "Promise SATA SX8 support"
300
304
 	depends on PCI
301
-	---help---
305
+	help
302
306
 	  Saying Y or M here will enable support for the 
303
307
 	  Promise SATA SX8 controllers.
304
308
 
..
..
@@ -306,7 +310,7 @@
306
310
 
307
311
 config BLK_DEV_RAM
308
312
 	tristate "RAM block device support"
309
-	---help---
313
+	help
310
314
 	  Saying Y here will allow you to use a portion of your RAM memory as
311
315
 	  a block device, so that you can make file systems on it, read and
312
316
 	  write to it and do all the other things that you can do with normal
..
..
@@ -315,7 +319,7 @@
315
319
 	  during the initial install of Linux.
316
320
 
317
321
 	  Note that the kernel command line option "ramdisk=XX" is now obsolete.
318
-	  For details, read <file:Documentation/blockdev/ramdisk.txt>.
322
+	  For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
319
323
 
320
324
 	  To compile this driver as a module, choose M here: the
321
325
 	  module will be called brd. An alias "rd" has been defined
..
..
@@ -359,7 +363,7 @@
359
363
 	  is possible.
360
364
 	  DVD-RW disks must be in restricted overwrite mode.
361
365
 
362
-	  See the file <file:Documentation/cdrom/packet-writing.txt>
366
+	  See the file <file:Documentation/cdrom/packet-writing.rst>
363
367
 	  for further information on the use of this driver.
364
368
 
365
369
 	  To compile this driver as a module, choose M here: the
..
..
@@ -440,19 +444,9 @@
440
444
 config VIRTIO_BLK
441
445
 	tristate "Virtio block driver"
442
446
 	depends on VIRTIO
443
-	---help---
447
+	help
444
448
 	  This is the virtual block driver for virtio.  It can be used with
445
449
           QEMU based VMMs (like KVM or Xen).  Say Y or M.
446
-
447
-config VIRTIO_BLK_SCSI
448
-	bool "SCSI passthrough request for the Virtio block driver"
449
-	depends on VIRTIO_BLK
450
-	select BLK_SCSI_REQUEST
451
-	---help---
452
-	  Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on
453
-	  virtio-blk devices.  This is only supported for the legacy
454
-	  virtio protocol and not enabled by default by any hypervisor.
455
-	  You probably want to use virtio-scsi instead.
456
450
 
457
451
 config BLK_DEV_RBD
458
452
 	tristate "Rados block device (RBD)"
..
..
@@ -461,7 +455,6 @@
461
455
 	select LIBCRC32C
462
456
 	select CRYPTO_AES
463
457
 	select CRYPTO
464
-	default n
465
458
 	help
466
459
 	  Say Y here if you want include the Rados block device, which stripes
467
460
 	  a block device over objects stored in the Ceph distributed object
..
..
@@ -482,4 +475,6 @@
482
475
 	  To compile this driver as a module, choose M here: the
483
476
 	  module will be called rsxx.
484
477
 
478
+source "drivers/block/rnbd/Kconfig"
479
+
485
480
 endif # BLK_DEV