Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # Character device configuration |
| 3 | # |
| 4 | |
| 5 | menu "Character devices" |
| 6 | |
Greg Kroah-Hartman | bdcffc5 | 2011-02-22 15:41:47 -0800 | [diff] [blame] | 7 | source "drivers/tty/Kconfig" |
Antonino A. Daplas | 13ae664 | 2006-06-26 00:27:12 -0700 | [diff] [blame] | 8 | |
Robert Love | 1fcada3 | 2008-04-29 16:44:10 -0400 | [diff] [blame] | 9 | config DEVMEM |
| 10 | bool "Memory device driver" |
| 11 | default y |
| 12 | help |
| 13 | The memory driver provides two character devices, mem and kmem, which |
| 14 | provide access to the system's memory. The mem device is a view of |
| 15 | physical memory, and each byte in the device corresponds to the |
| 16 | matching physical address. The kmem device is the same as mem, but |
| 17 | the addresses correspond to the kernel's virtual address space rather |
| 18 | than physical memory. These devices are standard parts of a Linux |
| 19 | system and most users should say Y here. You might say N if very |
| 20 | security conscience or memory is tight. |
| 21 | |
Arjan van de Ven | b781ecb | 2008-04-29 00:58:34 -0700 | [diff] [blame] | 22 | config DEVKMEM |
| 23 | bool "/dev/kmem virtual device support" |
| 24 | default y |
| 25 | help |
| 26 | Say Y here if you want to support the /dev/kmem device. The |
| 27 | /dev/kmem device is rarely used, but can be used for certain |
| 28 | kind of kernel debugging operations. |
| 29 | When in doubt, say "N". |
| 30 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 31 | config STALDRV |
| 32 | bool "Stallion multiport serial support" |
| 33 | depends on SERIAL_NONSTANDARD |
| 34 | help |
| 35 | Stallion cards give you many serial ports. You would need something |
| 36 | like this to connect more than two modems to your Linux box, for |
| 37 | instance in order to become a dial-in server. If you say Y here, |
| 38 | you will be asked for your specific card model in the next |
Randy Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 39 | questions. Make sure to read <file:Documentation/serial/stallion.txt> |
| 40 | in this case. If you have never heard about all this, it's safe to |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 41 | say N. |
| 42 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 43 | config SGI_SNSC |
| 44 | bool "SGI Altix system controller communication support" |
| 45 | depends on (IA64_SGI_SN2 || IA64_GENERIC) |
| 46 | help |
| 47 | If you have an SGI Altix and you want to enable system |
| 48 | controller communication from user space (you want this!), |
| 49 | say Y. Otherwise, say N. |
| 50 | |
Bruce Losure | e1e1974 | 2005-04-25 13:09:41 -0700 | [diff] [blame] | 51 | config SGI_TIOCX |
| 52 | bool "SGI TIO CX driver support" |
| 53 | depends on (IA64_SGI_SN2 || IA64_GENERIC) |
| 54 | help |
| 55 | If you have an SGI Altix and you have fpga devices attached |
| 56 | to your TIO, say Y here, otherwise say N. |
| 57 | |
| 58 | config SGI_MBCS |
| 59 | tristate "SGI FPGA Core Services driver support" |
Bruce Losure | ae40aae | 2005-04-04 13:23:00 -0700 | [diff] [blame] | 60 | depends on SGI_TIOCX |
Bruce Losure | e1e1974 | 2005-04-25 13:09:41 -0700 | [diff] [blame] | 61 | help |
| 62 | If you have an SGI Altix with an attached SABrick |
| 63 | say Y or M here, otherwise say N. |
| 64 | |
Greg Kroah-Hartman | ab4382d | 2011-01-13 12:10:18 -0800 | [diff] [blame] | 65 | source "drivers/tty/serial/Kconfig" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 66 | |
Bryan Huntsman | 3f2bc4d | 2011-08-16 17:27:22 -0700 | [diff] [blame] | 67 | source "drivers/char/diag/Kconfig" |
| 68 | |
Samo Pogacnik | 24b4b67 | 2010-08-25 20:44:07 +0200 | [diff] [blame] | 69 | config TTY_PRINTK |
| 70 | bool "TTY driver to output user messages via printk" |
David Rientjes | 6a108a1 | 2011-01-20 14:44:16 -0800 | [diff] [blame] | 71 | depends on EXPERT |
Samo Pogacnik | 24b4b67 | 2010-08-25 20:44:07 +0200 | [diff] [blame] | 72 | default n |
| 73 | ---help--- |
| 74 | If you say Y here, the support for writing user messages (i.e. |
| 75 | console messages) via printk is available. |
| 76 | |
| 77 | The feature is useful to inline user messages with kernel |
| 78 | messages. |
| 79 | In order to use this feature, you should output user messages |
| 80 | to /dev/ttyprintk or redirect console to this TTY. |
| 81 | |
| 82 | If unsure, say N. |
| 83 | |
Mike Frysinger | 2dc63a8 | 2008-04-25 08:04:56 +0800 | [diff] [blame] | 84 | config BFIN_OTP |
| 85 | tristate "Blackfin On-Chip OTP Memory Support" |
Mike Frysinger | f69b2d7 | 2009-11-20 19:09:56 +0000 | [diff] [blame] | 86 | depends on BLACKFIN && (BF51x || BF52x || BF54x) |
Mike Frysinger | 2dc63a8 | 2008-04-25 08:04:56 +0800 | [diff] [blame] | 87 | default y |
| 88 | help |
| 89 | If you say Y here, you will get support for a character device |
| 90 | interface into the One Time Programmable memory pages that are |
| 91 | stored on the Blackfin processor. This will not get you access |
| 92 | to the secure memory pages however. You will need to write your |
| 93 | own secure code and reader for that. |
| 94 | |
| 95 | To compile this driver as a module, choose M here: the module |
| 96 | will be called bfin-otp. |
| 97 | |
| 98 | If unsure, it is safe to say Y. |
| 99 | |
| 100 | config BFIN_OTP_WRITE_ENABLE |
| 101 | bool "Enable writing support of OTP pages" |
| 102 | depends on BFIN_OTP |
| 103 | default n |
| 104 | help |
| 105 | If you say Y here, you will enable support for writing of the |
| 106 | OTP pages. This is dangerous by nature as you can only program |
| 107 | the pages once, so only enable this option when you actually |
| 108 | need it so as to not inadvertently clobber data. |
| 109 | |
| 110 | If unsure, say N. |
| 111 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 112 | config PRINTER |
| 113 | tristate "Parallel printer support" |
| 114 | depends on PARPORT |
| 115 | ---help--- |
| 116 | If you intend to attach a printer to the parallel port of your Linux |
| 117 | box (as opposed to using a serial printer; if the connector at the |
| 118 | printer has 9 or 25 holes ["female"], then it's serial), say Y. |
| 119 | Also read the Printing-HOWTO, available from |
| 120 | <http://www.tldp.org/docs.html#howto>. |
| 121 | |
| 122 | It is possible to share one parallel port among several devices |
| 123 | (e.g. printer and ZIP drive) and it is safe to compile the |
| 124 | corresponding drivers into the kernel. |
| 125 | |
| 126 | To compile this driver as a module, choose M here and read |
| 127 | <file:Documentation/parport.txt>. The module will be called lp. |
| 128 | |
| 129 | If you have several parallel ports, you can specify which ports to |
| 130 | use with the "lp" kernel command line option. (Try "man bootparam" |
| 131 | or see the documentation of your boot loader (lilo or loadlin) about |
| 132 | how to pass options to the kernel at boot time.) The syntax of the |
| 133 | "lp" command line option can be found in <file:drivers/char/lp.c>. |
| 134 | |
| 135 | If you have more than 8 printers, you need to increase the LP_NO |
| 136 | macro in lp.c and the PARPORT_MAX macro in parport.h. |
| 137 | |
| 138 | config LP_CONSOLE |
| 139 | bool "Support for console on line printer" |
| 140 | depends on PRINTER |
| 141 | ---help--- |
| 142 | If you want kernel messages to be printed out as they occur, you |
| 143 | can have a console on the printer. This option adds support for |
| 144 | doing that; to actually get it to happen you need to pass the |
| 145 | option "console=lp0" to the kernel at boot time. |
| 146 | |
| 147 | If the printer is out of paper (or off, or unplugged, or too |
| 148 | busy..) the kernel will stall until the printer is ready again. |
| 149 | By defining CONSOLE_LP_STRICT to 0 (at your own risk) you |
| 150 | can make the kernel continue when this happens, |
| 151 | but it'll lose the kernel messages. |
| 152 | |
| 153 | If unsure, say N. |
| 154 | |
| 155 | config PPDEV |
| 156 | tristate "Support for user-space parallel port device drivers" |
| 157 | depends on PARPORT |
| 158 | ---help--- |
| 159 | Saying Y to this adds support for /dev/parport device nodes. This |
| 160 | is needed for programs that want portable access to the parallel |
| 161 | port, for instance deviceid (which displays Plug-and-Play device |
| 162 | IDs). |
| 163 | |
| 164 | This is the parallel port equivalent of SCSI generic support (sg). |
| 165 | It is safe to say N to this -- it is not needed for normal printing |
| 166 | or parallel port CD-ROM/disk support. |
| 167 | |
| 168 | To compile this driver as a module, choose M here: the |
| 169 | module will be called ppdev. |
| 170 | |
| 171 | If unsure, say N. |
| 172 | |
Greg Kroah-Hartman | bdcffc5 | 2011-02-22 15:41:47 -0800 | [diff] [blame] | 173 | source "drivers/tty/hvc/Kconfig" |
Mike Frysinger | 5427bcf | 2011-02-04 20:45:49 -0500 | [diff] [blame] | 174 | |
Rusty Russell | 3161043 | 2007-10-22 11:03:39 +1000 | [diff] [blame] | 175 | config VIRTIO_CONSOLE |
Christian Borntraeger | 7721c49 | 2008-07-25 12:06:06 -0500 | [diff] [blame] | 176 | tristate "Virtio console" |
| 177 | depends on VIRTIO |
Rusty Russell | 3161043 | 2007-10-22 11:03:39 +1000 | [diff] [blame] | 178 | select HVC_DRIVER |
Christian Borntraeger | 7721c49 | 2008-07-25 12:06:06 -0500 | [diff] [blame] | 179 | help |
| 180 | Virtio console for use with lguest and other hypervisors. |
| 181 | |
Amit Shah | fb08bd2 | 2009-12-21 21:36:04 +0530 | [diff] [blame] | 182 | Also serves as a general-purpose serial device for data |
| 183 | transfer between the guest and host. Character devices at |
| 184 | /dev/vportNpn will be created when corresponding ports are |
| 185 | found, where N is the device number and n is the port number |
| 186 | within that device. If specified by the host, a sysfs |
| 187 | attribute called 'name' will be populated with a name for |
| 188 | the port which can be used by udev scripts to create a |
| 189 | symlink to the device. |
Rusty Russell | 3161043 | 2007-10-22 11:03:39 +1000 | [diff] [blame] | 190 | |
Sonny Rao | fe9e8d5 | 2008-07-08 15:45:11 +1000 | [diff] [blame] | 191 | config IBM_BSR |
| 192 | tristate "IBM POWER Barrier Synchronization Register support" |
| 193 | depends on PPC_PSERIES |
| 194 | help |
| 195 | This devices exposes a hardware mechanism for fast synchronization |
| 196 | of threads across a large system which avoids bouncing a cacheline |
| 197 | between several cores on a system |
| 198 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 199 | source "drivers/char/ipmi/Kconfig" |
| 200 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 201 | config DS1620 |
| 202 | tristate "NetWinder thermometer support" |
| 203 | depends on ARCH_NETWINDER |
| 204 | help |
| 205 | Say Y here to include support for the thermal management hardware |
| 206 | found in the NetWinder. This driver allows the user to control the |
| 207 | temperature set points and to read the current temperature. |
| 208 | |
| 209 | It is also possible to say M here to build it as a module (ds1620) |
| 210 | It is recommended to be used on a NetWinder, but it is not a |
| 211 | necessity. |
| 212 | |
| 213 | config NWBUTTON |
| 214 | tristate "NetWinder Button" |
| 215 | depends on ARCH_NETWINDER |
| 216 | ---help--- |
| 217 | If you say Y here and create a character device node /dev/nwbutton |
| 218 | with major and minor numbers 10 and 158 ("man mknod"), then every |
| 219 | time the orange button is pressed a number of times, the number of |
| 220 | times the button was pressed will be written to that device. |
| 221 | |
| 222 | This is most useful for applications, as yet unwritten, which |
| 223 | perform actions based on how many times the button is pressed in a |
| 224 | row. |
| 225 | |
| 226 | Do not hold the button down for too long, as the driver does not |
| 227 | alter the behaviour of the hardware reset circuitry attached to the |
| 228 | button; it will still execute a hard reset if the button is held |
| 229 | down for longer than approximately five seconds. |
| 230 | |
| 231 | To compile this driver as a module, choose M here: the |
| 232 | module will be called nwbutton. |
| 233 | |
| 234 | Most people will answer Y to this question and "Reboot Using Button" |
| 235 | below to be able to initiate a system shutdown from the button. |
| 236 | |
| 237 | config NWBUTTON_REBOOT |
| 238 | bool "Reboot Using Button" |
| 239 | depends on NWBUTTON |
| 240 | help |
| 241 | If you say Y here, then you will be able to initiate a system |
| 242 | shutdown and reboot by pressing the orange button a number of times. |
| 243 | The number of presses to initiate the shutdown is two by default, |
| 244 | but this can be altered by modifying the value of NUM_PRESSES_REBOOT |
| 245 | in nwbutton.h and recompiling the driver or, if you compile the |
| 246 | driver as a module, you can specify the number of presses at load |
| 247 | time with "insmod button reboot_count=<something>". |
| 248 | |
| 249 | config NWFLASH |
| 250 | tristate "NetWinder flash support" |
| 251 | depends on ARCH_NETWINDER |
| 252 | ---help--- |
| 253 | If you say Y here and create a character device /dev/flash with |
| 254 | major 10 and minor 160 you can manipulate the flash ROM containing |
| 255 | the NetWinder firmware. Be careful as accidentally overwriting the |
| 256 | flash contents can render your computer unbootable. On no account |
| 257 | allow random users access to this device. :-) |
| 258 | |
| 259 | To compile this driver as a module, choose M here: the |
| 260 | module will be called nwflash. |
| 261 | |
| 262 | If you're not sure, say N. |
| 263 | |
Michael Buesch | 844dd05 | 2006-06-26 00:24:59 -0700 | [diff] [blame] | 264 | source "drivers/char/hw_random/Kconfig" |
| 265 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 266 | config NVRAM |
| 267 | tristate "/dev/nvram support" |
Uwe Kleine-König | 807a96c | 2009-01-31 01:21:59 +0100 | [diff] [blame] | 268 | depends on ATARI || X86 || (ARM && RTC_DRV_CMOS) || GENERIC_NVRAM |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 269 | ---help--- |
| 270 | If you say Y here and create a character special file /dev/nvram |
| 271 | with major number 10 and minor number 144 using mknod ("man mknod"), |
| 272 | you get read and write access to the extra bytes of non-volatile |
| 273 | memory in the real time clock (RTC), which is contained in every PC |
| 274 | and most Ataris. The actual number of bytes varies, depending on the |
| 275 | nvram in the system, but is usually 114 (128-14 for the RTC). |
| 276 | |
| 277 | This memory is conventionally called "CMOS RAM" on PCs and "NVRAM" |
| 278 | on Ataris. /dev/nvram may be used to view settings there, or to |
| 279 | change them (with some utility). It could also be used to frequently |
| 280 | save a few bits of very important data that may not be lost over |
| 281 | power-off and for which writing to disk is too insecure. Note |
| 282 | however that most NVRAM space in a PC belongs to the BIOS and you |
| 283 | should NEVER idly tamper with it. See Ralf Brown's interrupt list |
| 284 | for a guide to the use of CMOS bytes by your BIOS. |
| 285 | |
| 286 | On Atari machines, /dev/nvram is always configured and does not need |
| 287 | to be selected. |
| 288 | |
| 289 | To compile this driver as a module, choose M here: the |
| 290 | module will be called nvram. |
| 291 | |
David Brownell | c750090 | 2008-04-28 02:11:52 -0700 | [diff] [blame] | 292 | # |
| 293 | # These legacy RTC drivers just cause too many conflicts with the generic |
| 294 | # RTC framework ... let's not even try to coexist any more. |
| 295 | # |
| 296 | if RTC_LIB=n |
| 297 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 298 | config RTC |
David Brownell | e6d2bb2 | 2008-06-12 15:21:55 -0700 | [diff] [blame] | 299 | tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)" |
David Brownell | c750090 | 2008-04-28 02:11:52 -0700 | [diff] [blame] | 300 | depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \ |
Al Viro | 3369465 | 2011-08-18 20:11:59 +0100 | [diff] [blame] | 301 | && !ARM && !SUPERH && !S390 && !AVR32 && !BLACKFIN && !UML |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 302 | ---help--- |
| 303 | If you say Y here and create a character special file /dev/rtc with |
| 304 | major number 10 and minor number 135 using mknod ("man mknod"), you |
| 305 | will get access to the real time clock (or hardware clock) built |
| 306 | into your computer. |
| 307 | |
| 308 | Every PC has such a clock built in. It can be used to generate |
| 309 | signals from as low as 1Hz up to 8192Hz, and can also be used |
| 310 | as a 24 hour alarm. It reports status information via the file |
| 311 | /proc/driver/rtc and its behaviour is set by various ioctls on |
| 312 | /dev/rtc. |
| 313 | |
| 314 | If you run Linux on a multiprocessor machine and said Y to |
| 315 | "Symmetric Multi Processing" above, you should say Y here to read |
| 316 | and set the RTC in an SMP compatible fashion. |
| 317 | |
| 318 | If you think you have a use for such a device (such as periodic data |
| 319 | sampling), then say Y here, and read <file:Documentation/rtc.txt> |
| 320 | for details. |
| 321 | |
| 322 | To compile this driver as a module, choose M here: the |
| 323 | module will be called rtc. |
| 324 | |
Al Viro | 2240598 | 2007-07-22 00:37:48 -0700 | [diff] [blame] | 325 | config JS_RTC |
| 326 | tristate "Enhanced Real Time Clock Support" |
| 327 | depends on SPARC32 && PCI |
| 328 | ---help--- |
| 329 | If you say Y here and create a character special file /dev/rtc with |
| 330 | major number 10 and minor number 135 using mknod ("man mknod"), you |
| 331 | will get access to the real time clock (or hardware clock) built |
| 332 | into your computer. |
| 333 | |
| 334 | Every PC has such a clock built in. It can be used to generate |
| 335 | signals from as low as 1Hz up to 8192Hz, and can also be used |
| 336 | as a 24 hour alarm. It reports status information via the file |
| 337 | /proc/driver/rtc and its behaviour is set by various ioctls on |
| 338 | /dev/rtc. |
| 339 | |
| 340 | If you think you have a use for such a device (such as periodic data |
| 341 | sampling), then say Y here, and read <file:Documentation/rtc.txt> |
| 342 | for details. |
| 343 | |
| 344 | To compile this driver as a module, choose M here: the |
| 345 | module will be called js-rtc. |
| 346 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 347 | config GEN_RTC |
| 348 | tristate "Generic /dev/rtc emulation" |
Al Viro | 3369465 | 2011-08-18 20:11:59 +0100 | [diff] [blame] | 349 | depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32 && !BLACKFIN && !UML |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 350 | ---help--- |
| 351 | If you say Y here and create a character special file /dev/rtc with |
| 352 | major number 10 and minor number 135 using mknod ("man mknod"), you |
| 353 | will get access to the real time clock (or hardware clock) built |
| 354 | into your computer. |
| 355 | |
| 356 | It reports status information via the file /proc/driver/rtc and its |
| 357 | behaviour is set by various ioctls on /dev/rtc. If you enable the |
| 358 | "extended RTC operation" below it will also provide an emulation |
| 359 | for RTC_UIE which is required by some programs and may improve |
| 360 | precision in some cases. |
| 361 | |
| 362 | To compile this driver as a module, choose M here: the |
| 363 | module will be called genrtc. |
| 364 | |
| 365 | config GEN_RTC_X |
| 366 | bool "Extended RTC operation" |
| 367 | depends on GEN_RTC |
| 368 | help |
| 369 | Provides an emulation for RTC_UIE which is required by some programs |
| 370 | and may improve precision of the generic RTC support in some cases. |
| 371 | |
| 372 | config EFI_RTC |
| 373 | bool "EFI Real Time Clock Services" |
| 374 | depends on IA64 |
| 375 | |
| 376 | config DS1302 |
| 377 | tristate "DS1302 RTC support" |
| 378 | depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT) |
| 379 | help |
| 380 | If you say Y here and create a character special file /dev/rtc with |
| 381 | major number 121 and minor number 0 using mknod ("man mknod"), you |
| 382 | will get access to the real time clock (or hardware clock) built |
| 383 | into your computer. |
| 384 | |
David Brownell | c750090 | 2008-04-28 02:11:52 -0700 | [diff] [blame] | 385 | endif # RTC_LIB |
| 386 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 387 | config DTLK |
| 388 | tristate "Double Talk PC internal speech card support" |
Martin Schwidefsky | eeca7a3 | 2007-05-10 15:45:56 +0200 | [diff] [blame] | 389 | depends on ISA |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 390 | help |
| 391 | This driver is for the DoubleTalk PC, a speech synthesizer |
| 392 | manufactured by RC Systems (<http://www.rcsys.com/>). It is also |
| 393 | called the `internal DoubleTalk'. |
| 394 | |
| 395 | To compile this driver as a module, choose M here: the |
| 396 | module will be called dtlk. |
| 397 | |
Stephen Neuendorffer | ef141a0 | 2008-02-06 04:24:09 +1100 | [diff] [blame] | 398 | config XILINX_HWICAP |
| 399 | tristate "Xilinx HWICAP Support" |
Michal Simek | 6fa612b | 2009-05-11 15:49:12 +0200 | [diff] [blame] | 400 | depends on XILINX_VIRTEX || MICROBLAZE |
Stephen Neuendorffer | ef141a0 | 2008-02-06 04:24:09 +1100 | [diff] [blame] | 401 | help |
| 402 | This option enables support for Xilinx Internal Configuration |
| 403 | Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex |
| 404 | FPGA platforms to partially reconfigure the FPGA at runtime. |
| 405 | |
| 406 | If unsure, say N. |
| 407 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 408 | config R3964 |
| 409 | tristate "Siemens R3964 line discipline" |
| 410 | ---help--- |
| 411 | This driver allows synchronous communication with devices using the |
| 412 | Siemens R3964 packet protocol. Unless you are dealing with special |
| 413 | hardware like PLCs, you are unlikely to need this. |
| 414 | |
| 415 | To compile this driver as a module, choose M here: the |
| 416 | module will be called n_r3964. |
| 417 | |
| 418 | If unsure, say N. |
| 419 | |
| 420 | config APPLICOM |
| 421 | tristate "Applicom intelligent fieldbus card support" |
| 422 | depends on PCI |
| 423 | ---help--- |
| 424 | This driver provides the kernel-side support for the intelligent |
| 425 | fieldbus cards made by Applicom International. More information |
| 426 | about these cards can be found on the WWW at the address |
| 427 | <http://www.applicom-int.com/>, or by email from David Woodhouse |
| 428 | <dwmw2@infradead.org>. |
| 429 | |
| 430 | To compile this driver as a module, choose M here: the |
| 431 | module will be called applicom. |
| 432 | |
| 433 | If unsure, say N. |
| 434 | |
| 435 | config SONYPI |
| 436 | tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)" |
| 437 | depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT |
| 438 | ---help--- |
| 439 | This driver enables access to the Sony Programmable I/O Control |
| 440 | Device which can be found in many (all ?) Sony Vaio laptops. |
| 441 | |
| 442 | If you have one of those laptops, read |
Carlos Corbacho | 018a651 | 2008-02-09 01:32:19 +0000 | [diff] [blame] | 443 | <file:Documentation/laptops/sonypi.txt>, and say Y or M here. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 444 | |
| 445 | To compile this driver as a module, choose M here: the |
| 446 | module will be called sonypi. |
| 447 | |
Yoichi Yuasa | 0976251 | 2007-05-06 14:51:58 -0700 | [diff] [blame] | 448 | config GPIO_TB0219 |
| 449 | tristate "TANBAC TB0219 GPIO support" |
Robert P. J. Day | bef1f40 | 2006-12-12 20:04:19 +0100 | [diff] [blame] | 450 | depends on TANBAC_TB022X |
Yoichi Yuasa | 584e123 | 2006-06-25 05:49:11 -0700 | [diff] [blame] | 451 | select GPIO_VR41XX |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 452 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 453 | source "drivers/char/pcmcia/Kconfig" |
| 454 | |
| 455 | config MWAVE |
| 456 | tristate "ACP Modem (Mwave) support" |
| 457 | depends on X86 |
| 458 | select SERIAL_8250 |
| 459 | ---help--- |
| 460 | The ACP modem (Mwave) for Linux is a WinModem. It is composed of a |
| 461 | kernel driver and a user level application. Together these components |
| 462 | support direct attachment to public switched telephone networks (PSTNs) |
| 463 | and support selected world wide countries. |
| 464 | |
| 465 | This version of the ACP Modem driver supports the IBM Thinkpad 600E, |
| 466 | 600, and 770 that include on board ACP modem hardware. |
| 467 | |
| 468 | The modem also supports the standard communications port interface |
| 469 | (ttySx) and is compatible with the Hayes AT Command Set. |
| 470 | |
| 471 | The user level application needed to use this driver can be found at |
| 472 | the IBM Linux Technology Center (LTC) web site: |
| 473 | <http://www.ibm.com/linux/ltc/>. |
| 474 | |
| 475 | If you own one of the above IBM Thinkpads which has the Mwave chipset |
| 476 | in it, say Y. |
| 477 | |
| 478 | To compile this driver as a module, choose M here: the |
| 479 | module will be called mwave. |
| 480 | |
| 481 | config SCx200_GPIO |
| 482 | tristate "NatSemi SCx200 GPIO Support" |
| 483 | depends on SCx200 |
Jim Cromie | 7a8e2a5 | 2006-06-27 02:54:27 -0700 | [diff] [blame] | 484 | select NSC_GPIO |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 485 | help |
| 486 | Give userspace access to the GPIO pins on the National |
| 487 | Semiconductor SCx200 processors. |
| 488 | |
| 489 | If compiled as a module, it will be called scx200_gpio. |
| 490 | |
Jim Cromie | 7a8e2a5 | 2006-06-27 02:54:27 -0700 | [diff] [blame] | 491 | config PC8736x_GPIO |
| 492 | tristate "NatSemi PC8736x GPIO Support" |
Al Viro | 3369465 | 2011-08-18 20:11:59 +0100 | [diff] [blame] | 493 | depends on X86_32 && !UML |
Jim Cromie | 7a8e2a5 | 2006-06-27 02:54:27 -0700 | [diff] [blame] | 494 | default SCx200_GPIO # mostly N |
| 495 | select NSC_GPIO # needed for support routines |
| 496 | help |
| 497 | Give userspace access to the GPIO pins on the National |
| 498 | Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip |
| 499 | has multiple functional units, inc several managed by |
| 500 | hwmon/pc87360 driver. Tested with PC-87366 |
| 501 | |
| 502 | If compiled as a module, it will be called pc8736x_gpio. |
| 503 | |
| 504 | config NSC_GPIO |
| 505 | tristate "NatSemi Base GPIO Support" |
Dave Jones | 699352c | 2006-06-29 02:24:32 -0700 | [diff] [blame] | 506 | depends on X86_32 |
Jim Cromie | 7a8e2a5 | 2006-06-27 02:54:27 -0700 | [diff] [blame] | 507 | # selected by SCx200_GPIO and PC8736x_GPIO |
| 508 | # what about 2 selectors differing: m != y |
| 509 | help |
| 510 | Common support used (and needed) by scx200_gpio and |
| 511 | pc8736x_gpio drivers. If those drivers are built as |
| 512 | modules, this one will be too, named nsc_gpio |
| 513 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 514 | config RAW_DRIVER |
Dave Jones | abd4aa5 | 2007-07-15 23:40:49 -0700 | [diff] [blame] | 515 | tristate "RAW driver (/dev/raw/rawN)" |
David Howells | 9361401 | 2006-09-30 20:45:40 +0200 | [diff] [blame] | 516 | depends on BLOCK |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 517 | help |
Dave Jones | abd4aa5 | 2007-07-15 23:40:49 -0700 | [diff] [blame] | 518 | The raw driver permits block devices to be bound to /dev/raw/rawN. |
| 519 | Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 520 | See the raw(8) manpage for more details. |
| 521 | |
Dave Jones | abd4aa5 | 2007-07-15 23:40:49 -0700 | [diff] [blame] | 522 | Applications should preferably open the device (eg /dev/hda1) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 523 | with the O_DIRECT flag. |
| 524 | |
Andrew Morton | 0de502a | 2005-12-12 00:37:41 -0800 | [diff] [blame] | 525 | config MAX_RAW_DEVS |
Jan Kara | 0078bff | 2011-04-29 00:24:29 +0200 | [diff] [blame] | 526 | int "Maximum number of RAW devices to support (1-65536)" |
Andrew Morton | 0de502a | 2005-12-12 00:37:41 -0800 | [diff] [blame] | 527 | depends on RAW_DRIVER |
| 528 | default "256" |
| 529 | help |
| 530 | The maximum number of RAW devices that are supported. |
| 531 | Default is 256. Increase this number in case you need lots of |
| 532 | raw devices. |
| 533 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 534 | config HPET |
| 535 | bool "HPET - High Precision Event Timer" if (X86 || IA64) |
| 536 | default n |
| 537 | depends on ACPI |
| 538 | help |
| 539 | If you say Y here, you will have a miscdevice named "/dev/hpet/". Each |
| 540 | open selects one of the timers supported by the HPET. The timers are |
Matt LaPlante | 3cb2fcc | 2006-11-30 05:22:59 +0100 | [diff] [blame] | 541 | non-periodic and/or periodic. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 542 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 543 | config HPET_MMAP |
| 544 | bool "Allow mmap of HPET" |
| 545 | default y |
| 546 | depends on HPET |
| 547 | help |
| 548 | If you say Y here, user applications will be able to mmap |
| 549 | the HPET registers. |
| 550 | |
| 551 | In some hardware implementations, the page containing HPET |
| 552 | registers may also contain other things that shouldn't be |
| 553 | exposed to the user. If this applies to your hardware, |
| 554 | say N here. |
| 555 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 556 | config HANGCHECK_TIMER |
| 557 | tristate "Hangcheck timer" |
Martin Schwidefsky | abf3ea1 | 2007-05-10 15:45:59 +0200 | [diff] [blame] | 558 | depends on X86 || IA64 || PPC64 || S390 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 559 | help |
| 560 | The hangcheck-timer module detects when the system has gone |
| 561 | out to lunch past a certain margin. It can reboot the system |
| 562 | or merely print a warning. |
| 563 | |
| 564 | config MMTIMER |
| 565 | tristate "MMTIMER Memory mapped RTC for SGI Altix" |
| 566 | depends on IA64_GENERIC || IA64_SGI_SN2 |
| 567 | default y |
| 568 | help |
| 569 | The mmtimer device allows direct userspace access to the |
| 570 | Altix system timer. |
| 571 | |
Dimitri Sivanich | fbd8ae1 | 2009-09-23 15:57:15 -0700 | [diff] [blame] | 572 | config UV_MMTIMER |
| 573 | tristate "UV_MMTIMER Memory mapped RTC for SGI UV" |
| 574 | depends on X86_UV |
| 575 | default m |
| 576 | help |
| 577 | The uv_mmtimer device allows direct userspace access to the |
| 578 | UV system timer. |
| 579 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 580 | source "drivers/char/tpm/Kconfig" |
| 581 | |
Mark Gross | 1a80ba8 | 2005-10-30 15:02:55 -0800 | [diff] [blame] | 582 | config TELCLOCK |
Mark Gross | 03154a2 | 2007-03-06 13:58:45 -0800 | [diff] [blame] | 583 | tristate "Telecom clock driver for ATCA SBC" |
Geert Uytterhoeven | 4d99bfa | 2006-10-16 19:59:43 +0200 | [diff] [blame] | 584 | depends on EXPERIMENTAL && X86 |
Mark Gross | 1a80ba8 | 2005-10-30 15:02:55 -0800 | [diff] [blame] | 585 | default n |
| 586 | help |
Mark Gross | 03154a2 | 2007-03-06 13:58:45 -0800 | [diff] [blame] | 587 | The telecom clock device is specific to the MPCBL0010 and MPCBL0050 |
| 588 | ATCA computers and allows direct userspace access to the |
| 589 | configuration of the telecom clock configuration settings. This |
| 590 | device is used for hardware synchronization across the ATCA backplane |
| 591 | fabric. Upon loading, the driver exports a sysfs directory, |
| 592 | /sys/devices/platform/telco_clock, with a number of files for |
| 593 | controlling the behavior of this hardware. |
Mark Gross | 1a80ba8 | 2005-10-30 15:02:55 -0800 | [diff] [blame] | 594 | |
Russell King | 4f911d6 | 2007-05-08 00:28:17 -0700 | [diff] [blame] | 595 | config DEVPORT |
| 596 | bool |
| 597 | depends on !M68K |
| 598 | depends on ISA || PCI |
| 599 | default y |
| 600 | |
Arve Hjønnevåg | 8b6990f | 2007-12-01 18:34:14 -0800 | [diff] [blame] | 601 | config DCC_TTY |
| 602 | tristate "DCC tty driver" |
| 603 | depends on ARM |
| 604 | |
Martin Schwidefsky | 61d48c2 | 2007-05-10 15:46:00 +0200 | [diff] [blame] | 605 | source "drivers/s390/char/Kconfig" |
| 606 | |
Marco Stornelli | 56d611a | 2010-05-26 14:43:54 -0700 | [diff] [blame] | 607 | config RAMOOPS |
| 608 | tristate "Log panic/oops to a RAM buffer" |
Heiko Carstens | b7e5d1f | 2010-06-04 14:14:48 -0700 | [diff] [blame] | 609 | depends on HAS_IOMEM |
Marco Stornelli | 56d611a | 2010-05-26 14:43:54 -0700 | [diff] [blame] | 610 | default n |
| 611 | help |
| 612 | This enables panic and oops messages to be logged to a circular |
| 613 | buffer in RAM where it can be read back at some later point. |
| 614 | |
Niranjana Vishwanathapura | 73210a1 | 2011-03-23 16:42:55 -0700 | [diff] [blame] | 615 | config MSM_SMD_PKT |
| 616 | bool "Enable device interface for some SMD packet ports" |
| 617 | default n |
| 618 | depends on MSM_SMD |
| 619 | help |
| 620 | Enables userspace clients to read and write to some packet SMD |
| 621 | ports via device interface for MSM chipset. |
| 622 | |
Chris Metcalf | dbcb4a1 | 2011-06-10 13:07:48 -0400 | [diff] [blame] | 623 | config TILE_SROM |
| 624 | bool "Character-device access via hypervisor to the Tilera SPI ROM" |
| 625 | depends on TILE |
| 626 | default y |
| 627 | ---help--- |
| 628 | This device provides character-level read-write access |
| 629 | to the SROM, typically via the "0", "1", and "2" devices |
| 630 | in /dev/srom/. The Tilera hypervisor makes the flash |
| 631 | device appear much like a simple EEPROM, and knows |
| 632 | how to partition a single ROM for multiple purposes. |
| 633 | |
Bryan Huntsman | 3f2bc4d | 2011-08-16 17:27:22 -0700 | [diff] [blame] | 634 | config MSM_ROTATOR |
| 635 | tristate "MSM Offline Image Rotator Driver" |
Laura Abbott | f2c6a1e | 2013-03-08 14:56:20 -0800 | [diff] [blame] | 636 | depends on (ARCH_MSM7X30 || ARCH_MSM8X60 || ARCH_MSM8960) |
Bryan Huntsman | 3f2bc4d | 2011-08-16 17:27:22 -0700 | [diff] [blame] | 637 | default y |
| 638 | help |
| 639 | This driver provides support for the image rotator HW block in the |
| 640 | MSM 7x30 SoC. |
| 641 | |
| 642 | config MSM_ROTATOR_USE_IMEM |
| 643 | bool "Enable rotator driver to use iMem" |
| 644 | depends on ARCH_MSM7X30 && MSM_ROTATOR |
| 645 | default y |
| 646 | help |
| 647 | This option enables the msm_rotator driver to use the move efficient |
| 648 | iMem. Some MSM platforms may not have iMem available for the rotator |
| 649 | block. Or some systems may want the iMem to be dedicated to a |
| 650 | different function. |
| 651 | |
Mitchel Humpherys | 5a2aad1 | 2012-09-30 22:55:35 -0700 | [diff] [blame] | 652 | config MSM_ADSPRPC |
| 653 | tristate "Qualcomm ADSP RPC driver" |
| 654 | depends on MSM_AUDIO_QDSP6 || MSM_AUDIO_QDSP6V2 |
| 655 | default m |
| 656 | help |
| 657 | Provides a communication mechanism that allows for clients to |
| 658 | make remote method invocations across processor boundary to |
| 659 | applications DSP processor. Say M if you want to enable this |
| 660 | module. |
| 661 | |
Bryan Huntsman | 3f2bc4d | 2011-08-16 17:27:22 -0700 | [diff] [blame] | 662 | config MMC_GENERIC_CSDIO |
| 663 | tristate "Generic sdio driver" |
| 664 | default n |
| 665 | help |
| 666 | SDIO function driver that extends SDIO card as character device |
| 667 | in user space. |
| 668 | |
| 669 | config CSDIO_VENDOR_ID |
| 670 | hex "Card VendorId" |
| 671 | depends on MMC_GENERIC_CSDIO |
| 672 | default "0" |
| 673 | help |
| 674 | Enter vendor id for targeted sdio device, this may be overwritten by |
| 675 | module parameters. |
| 676 | |
| 677 | config CSDIO_DEVICE_ID |
| 678 | hex "CardDeviceId" |
| 679 | depends on MMC_GENERIC_CSDIO |
| 680 | default "0" |
| 681 | help |
| 682 | Enter device id for targeted sdio device, this may be overwritten by |
| 683 | module parameters. |
Aparna Das | 29924c1 | 2013-06-07 17:31:51 -0700 | [diff] [blame^] | 684 | |
| 685 | config MSM_RDBG |
| 686 | tristate "Qualcomm Remote debug driver" |
| 687 | depends on MSM_AUDIO_QDSP6 || MSM_AUDIO_QDSP6V2 |
| 688 | help |
| 689 | Implements a shared memory based transport mechanism that allows |
| 690 | for a debugger running on a host PC to communicate with a remote |
| 691 | stub running on peripheral subsystems such as the ADSP, MODEM etc. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 692 | endmenu |
| 693 | |