1 #
2 # Character device configuration
3 #
5 menu "Character devices"
7 source "drivers/tty/Kconfig"
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.
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".
31 config SGI_SNSC
32 bool "SGI Altix system controller communication support"
33 depends on (IA64_SGI_SN2 || IA64_GENERIC)
34 help
35 If you have an SGI Altix and you want to enable system
36 controller communication from user space (you want this!),
37 say Y. Otherwise, say N.
39 config SGI_TIOCX
40 bool "SGI TIO CX driver support"
41 depends on (IA64_SGI_SN2 || IA64_GENERIC)
42 help
43 If you have an SGI Altix and you have fpga devices attached
44 to your TIO, say Y here, otherwise say N.
46 config SGI_MBCS
47 tristate "SGI FPGA Core Services driver support"
48 depends on SGI_TIOCX
49 help
50 If you have an SGI Altix with an attached SABrick
51 say Y or M here, otherwise say N.
53 source "drivers/tty/serial/Kconfig"
55 config TTY_PRINTK
56 bool "TTY driver to output user messages via printk"
57 depends on EXPERT && TTY
58 default n
59 ---help---
60 If you say Y here, the support for writing user messages (i.e.
61 console messages) via printk is available.
63 The feature is useful to inline user messages with kernel
64 messages.
65 In order to use this feature, you should output user messages
66 to /dev/ttyprintk or redirect console to this TTY.
68 If unsure, say N.
70 config BFIN_OTP
71 tristate "Blackfin On-Chip OTP Memory Support"
72 depends on BLACKFIN && (BF51x || BF52x || BF54x)
73 default y
74 help
75 If you say Y here, you will get support for a character device
76 interface into the One Time Programmable memory pages that are
77 stored on the Blackfin processor. This will not get you access
78 to the secure memory pages however. You will need to write your
79 own secure code and reader for that.
81 To compile this driver as a module, choose M here: the module
82 will be called bfin-otp.
84 If unsure, it is safe to say Y.
86 config BFIN_OTP_WRITE_ENABLE
87 bool "Enable writing support of OTP pages"
88 depends on BFIN_OTP
89 default n
90 help
91 If you say Y here, you will enable support for writing of the
92 OTP pages. This is dangerous by nature as you can only program
93 the pages once, so only enable this option when you actually
94 need it so as to not inadvertently clobber data.
96 If unsure, say N.
98 config PRINTER
99 tristate "Parallel printer support"
100 depends on PARPORT
101 ---help---
102 If you intend to attach a printer to the parallel port of your Linux
103 box (as opposed to using a serial printer; if the connector at the
104 printer has 9 or 25 holes ["female"], then it's serial), say Y.
105 Also read the Printing-HOWTO, available from
106 <http://www.tldp.org/docs.html#howto>.
108 It is possible to share one parallel port among several devices
109 (e.g. printer and ZIP drive) and it is safe to compile the
110 corresponding drivers into the kernel.
112 To compile this driver as a module, choose M here and read
113 <file:Documentation/parport.txt>. The module will be called lp.
115 If you have several parallel ports, you can specify which ports to
116 use with the "lp" kernel command line option. (Try "man bootparam"
117 or see the documentation of your boot loader (lilo or loadlin) about
118 how to pass options to the kernel at boot time.) The syntax of the
119 "lp" command line option can be found in <file:drivers/char/lp.c>.
121 If you have more than 8 printers, you need to increase the LP_NO
122 macro in lp.c and the PARPORT_MAX macro in parport.h.
124 config LP_CONSOLE
125 bool "Support for console on line printer"
126 depends on PRINTER
127 ---help---
128 If you want kernel messages to be printed out as they occur, you
129 can have a console on the printer. This option adds support for
130 doing that; to actually get it to happen you need to pass the
131 option "console=lp0" to the kernel at boot time.
133 If the printer is out of paper (or off, or unplugged, or too
134 busy..) the kernel will stall until the printer is ready again.
135 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
136 can make the kernel continue when this happens,
137 but it'll lose the kernel messages.
139 If unsure, say N.
141 config PPDEV
142 tristate "Support for user-space parallel port device drivers"
143 depends on PARPORT
144 ---help---
145 Saying Y to this adds support for /dev/parport device nodes. This
146 is needed for programs that want portable access to the parallel
147 port, for instance deviceid (which displays Plug-and-Play device
148 IDs).
150 This is the parallel port equivalent of SCSI generic support (sg).
151 It is safe to say N to this -- it is not needed for normal printing
152 or parallel port CD-ROM/disk support.
154 To compile this driver as a module, choose M here: the
155 module will be called ppdev.
157 If unsure, say N.
159 source "drivers/tty/hvc/Kconfig"
161 config VIRTIO_CONSOLE
162 tristate "Virtio console"
163 depends on VIRTIO && TTY
164 select HVC_DRIVER
165 help
166 Virtio console for use with lguest and other hypervisors.
168 Also serves as a general-purpose serial device for data
169 transfer between the guest and host. Character devices at
170 /dev/vportNpn will be created when corresponding ports are
171 found, where N is the device number and n is the port number
172 within that device. If specified by the host, a sysfs
173 attribute called 'name' will be populated with a name for
174 the port which can be used by udev scripts to create a
175 symlink to the device.
177 config IBM_BSR
178 tristate "IBM POWER Barrier Synchronization Register support"
179 depends on PPC_PSERIES
180 help
181 This devices exposes a hardware mechanism for fast synchronization
182 of threads across a large system which avoids bouncing a cacheline
183 between several cores on a system
185 source "drivers/char/ipmi/Kconfig"
187 config DS1620
188 tristate "NetWinder thermometer support"
189 depends on ARCH_NETWINDER
190 help
191 Say Y here to include support for the thermal management hardware
192 found in the NetWinder. This driver allows the user to control the
193 temperature set points and to read the current temperature.
195 It is also possible to say M here to build it as a module (ds1620)
196 It is recommended to be used on a NetWinder, but it is not a
197 necessity.
199 config NWBUTTON
200 tristate "NetWinder Button"
201 depends on ARCH_NETWINDER
202 ---help---
203 If you say Y here and create a character device node /dev/nwbutton
204 with major and minor numbers 10 and 158 ("man mknod"), then every
205 time the orange button is pressed a number of times, the number of
206 times the button was pressed will be written to that device.
208 This is most useful for applications, as yet unwritten, which
209 perform actions based on how many times the button is pressed in a
210 row.
212 Do not hold the button down for too long, as the driver does not
213 alter the behaviour of the hardware reset circuitry attached to the
214 button; it will still execute a hard reset if the button is held
215 down for longer than approximately five seconds.
217 To compile this driver as a module, choose M here: the
218 module will be called nwbutton.
220 Most people will answer Y to this question and "Reboot Using Button"
221 below to be able to initiate a system shutdown from the button.
223 config NWBUTTON_REBOOT
224 bool "Reboot Using Button"
225 depends on NWBUTTON
226 help
227 If you say Y here, then you will be able to initiate a system
228 shutdown and reboot by pressing the orange button a number of times.
229 The number of presses to initiate the shutdown is two by default,
230 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
231 in nwbutton.h and recompiling the driver or, if you compile the
232 driver as a module, you can specify the number of presses at load
233 time with "insmod button reboot_count=<something>".
235 config NWFLASH
236 tristate "NetWinder flash support"
237 depends on ARCH_NETWINDER
238 ---help---
239 If you say Y here and create a character device /dev/flash with
240 major 10 and minor 160 you can manipulate the flash ROM containing
241 the NetWinder firmware. Be careful as accidentally overwriting the
242 flash contents can render your computer unbootable. On no account
243 allow random users access to this device. :-)
245 To compile this driver as a module, choose M here: the
246 module will be called nwflash.
248 If you're not sure, say N.
250 source "drivers/char/hw_random/Kconfig"
252 config NVRAM
253 tristate "/dev/nvram support"
254 depends on ATARI || X86 || (ARM && RTC_DRV_CMOS) || GENERIC_NVRAM
255 ---help---
256 If you say Y here and create a character special file /dev/nvram
257 with major number 10 and minor number 144 using mknod ("man mknod"),
258 you get read and write access to the extra bytes of non-volatile
259 memory in the real time clock (RTC), which is contained in every PC
260 and most Ataris. The actual number of bytes varies, depending on the
261 nvram in the system, but is usually 114 (128-14 for the RTC).
263 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
264 on Ataris. /dev/nvram may be used to view settings there, or to
265 change them (with some utility). It could also be used to frequently
266 save a few bits of very important data that may not be lost over
267 power-off and for which writing to disk is too insecure. Note
268 however that most NVRAM space in a PC belongs to the BIOS and you
269 should NEVER idly tamper with it. See Ralf Brown's interrupt list
270 for a guide to the use of CMOS bytes by your BIOS.
272 On Atari machines, /dev/nvram is always configured and does not need
273 to be selected.
275 To compile this driver as a module, choose M here: the
276 module will be called nvram.
278 #
279 # These legacy RTC drivers just cause too many conflicts with the generic
280 # RTC framework ... let's not even try to coexist any more.
281 #
282 if RTC_LIB=n
284 config RTC
285 tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
286 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
287 && !ARM && !SUPERH && !S390 && !AVR32 && !BLACKFIN && !UML
288 ---help---
289 If you say Y here and create a character special file /dev/rtc with
290 major number 10 and minor number 135 using mknod ("man mknod"), you
291 will get access to the real time clock (or hardware clock) built
292 into your computer.
294 Every PC has such a clock built in. It can be used to generate
295 signals from as low as 1Hz up to 8192Hz, and can also be used
296 as a 24 hour alarm. It reports status information via the file
297 /proc/driver/rtc and its behaviour is set by various ioctls on
298 /dev/rtc.
300 If you run Linux on a multiprocessor machine and said Y to
301 "Symmetric Multi Processing" above, you should say Y here to read
302 and set the RTC in an SMP compatible fashion.
304 If you think you have a use for such a device (such as periodic data
305 sampling), then say Y here, and read <file:Documentation/rtc.txt>
306 for details.
308 To compile this driver as a module, choose M here: the
309 module will be called rtc.
311 config JS_RTC
312 tristate "Enhanced Real Time Clock Support"
313 depends on SPARC32 && PCI
314 ---help---
315 If you say Y here and create a character special file /dev/rtc with
316 major number 10 and minor number 135 using mknod ("man mknod"), you
317 will get access to the real time clock (or hardware clock) built
318 into your computer.
320 Every PC has such a clock built in. It can be used to generate
321 signals from as low as 1Hz up to 8192Hz, and can also be used
322 as a 24 hour alarm. It reports status information via the file
323 /proc/driver/rtc and its behaviour is set by various ioctls on
324 /dev/rtc.
326 If you think you have a use for such a device (such as periodic data
327 sampling), then say Y here, and read <file:Documentation/rtc.txt>
328 for details.
330 To compile this driver as a module, choose M here: the
331 module will be called js-rtc.
333 config GEN_RTC
334 tristate "Generic /dev/rtc emulation"
335 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32 && !BLACKFIN && !UML
336 ---help---
337 If you say Y here and create a character special file /dev/rtc with
338 major number 10 and minor number 135 using mknod ("man mknod"), you
339 will get access to the real time clock (or hardware clock) built
340 into your computer.
342 It reports status information via the file /proc/driver/rtc and its
343 behaviour is set by various ioctls on /dev/rtc. If you enable the
344 "extended RTC operation" below it will also provide an emulation
345 for RTC_UIE which is required by some programs and may improve
346 precision in some cases.
348 To compile this driver as a module, choose M here: the
349 module will be called genrtc.
351 config GEN_RTC_X
352 bool "Extended RTC operation"
353 depends on GEN_RTC
354 help
355 Provides an emulation for RTC_UIE which is required by some programs
356 and may improve precision of the generic RTC support in some cases.
358 config EFI_RTC
359 bool "EFI Real Time Clock Services"
360 depends on IA64
362 config DS1302
363 tristate "DS1302 RTC support"
364 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
365 help
366 If you say Y here and create a character special file /dev/rtc with
367 major number 121 and minor number 0 using mknod ("man mknod"), you
368 will get access to the real time clock (or hardware clock) built
369 into your computer.
371 endif # RTC_LIB
373 config DTLK
374 tristate "Double Talk PC internal speech card support"
375 depends on ISA
376 help
377 This driver is for the DoubleTalk PC, a speech synthesizer
378 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
379 called the `internal DoubleTalk'.
381 To compile this driver as a module, choose M here: the
382 module will be called dtlk.
384 config XILINX_HWICAP
385 tristate "Xilinx HWICAP Support"
386 depends on XILINX_VIRTEX || MICROBLAZE
387 help
388 This option enables support for Xilinx Internal Configuration
389 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
390 FPGA platforms to partially reconfigure the FPGA at runtime.
392 If unsure, say N.
394 config R3964
395 tristate "Siemens R3964 line discipline"
396 depends on TTY
397 ---help---
398 This driver allows synchronous communication with devices using the
399 Siemens R3964 packet protocol. Unless you are dealing with special
400 hardware like PLCs, you are unlikely to need this.
402 To compile this driver as a module, choose M here: the
403 module will be called n_r3964.
405 If unsure, say N.
407 config APPLICOM
408 tristate "Applicom intelligent fieldbus card support"
409 depends on PCI
410 ---help---
411 This driver provides the kernel-side support for the intelligent
412 fieldbus cards made by Applicom International. More information
413 about these cards can be found on the WWW at the address
414 <http://www.applicom-int.com/>, or by email from David Woodhouse
415 <dwmw2@infradead.org>.
417 To compile this driver as a module, choose M here: the
418 module will be called applicom.
420 If unsure, say N.
422 config SONYPI
423 tristate "Sony Vaio Programmable I/O Control Device support"
424 depends on X86 && PCI && INPUT && !64BIT
425 ---help---
426 This driver enables access to the Sony Programmable I/O Control
427 Device which can be found in many (all ?) Sony Vaio laptops.
429 If you have one of those laptops, read
430 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
432 To compile this driver as a module, choose M here: the
433 module will be called sonypi.
435 config GPIO_TB0219
436 tristate "TANBAC TB0219 GPIO support"
437 depends on TANBAC_TB022X
438 select GPIO_VR41XX
440 source "drivers/char/pcmcia/Kconfig"
442 config MWAVE
443 tristate "ACP Modem (Mwave) support"
444 depends on X86 && TTY
445 select SERIAL_8250
446 ---help---
447 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
448 kernel driver and a user level application. Together these components
449 support direct attachment to public switched telephone networks (PSTNs)
450 and support selected world wide countries.
452 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
453 600, and 770 that include on board ACP modem hardware.
455 The modem also supports the standard communications port interface
456 (ttySx) and is compatible with the Hayes AT Command Set.
458 The user level application needed to use this driver can be found at
459 the IBM Linux Technology Center (LTC) web site:
460 <http://www.ibm.com/linux/ltc/>.
462 If you own one of the above IBM Thinkpads which has the Mwave chipset
463 in it, say Y.
465 To compile this driver as a module, choose M here: the
466 module will be called mwave.
468 config SCx200_GPIO
469 tristate "NatSemi SCx200 GPIO Support"
470 depends on SCx200
471 select NSC_GPIO
472 help
473 Give userspace access to the GPIO pins on the National
474 Semiconductor SCx200 processors.
476 If compiled as a module, it will be called scx200_gpio.
478 config PC8736x_GPIO
479 tristate "NatSemi PC8736x GPIO Support"
480 depends on X86_32 && !UML
481 default SCx200_GPIO # mostly N
482 select NSC_GPIO # needed for support routines
483 help
484 Give userspace access to the GPIO pins on the National
485 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
486 has multiple functional units, inc several managed by
487 hwmon/pc87360 driver. Tested with PC-87366
489 If compiled as a module, it will be called pc8736x_gpio.
491 config NSC_GPIO
492 tristate "NatSemi Base GPIO Support"
493 depends on X86_32
494 # selected by SCx200_GPIO and PC8736x_GPIO
495 # what about 2 selectors differing: m != y
496 help
497 Common support used (and needed) by scx200_gpio and
498 pc8736x_gpio drivers. If those drivers are built as
499 modules, this one will be too, named nsc_gpio
501 config RAW_DRIVER
502 tristate "RAW driver (/dev/raw/rawN)"
503 depends on BLOCK
504 help
505 The raw driver permits block devices to be bound to /dev/raw/rawN.
506 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
507 See the raw(8) manpage for more details.
509 Applications should preferably open the device (eg /dev/hda1)
510 with the O_DIRECT flag.
512 config MAX_RAW_DEVS
513 int "Maximum number of RAW devices to support (1-65536)"
514 depends on RAW_DRIVER
515 range 1 65536
516 default "256"
517 help
518 The maximum number of RAW devices that are supported.
519 Default is 256. Increase this number in case you need lots of
520 raw devices.
522 config HPET
523 bool "HPET - High Precision Event Timer" if (X86 || IA64)
524 default n
525 depends on ACPI
526 help
527 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
528 open selects one of the timers supported by the HPET. The timers are
529 non-periodic and/or periodic.
531 config HPET_MMAP
532 bool "Allow mmap of HPET"
533 default y
534 depends on HPET
535 help
536 If you say Y here, user applications will be able to mmap
537 the HPET registers.
539 config HPET_MMAP_DEFAULT
540 bool "Enable HPET MMAP access by default"
541 default y
542 depends on HPET_MMAP
543 help
544 In some hardware implementations, the page containing HPET
545 registers may also contain other things that shouldn't be
546 exposed to the user. This option selects the default (if
547 kernel parameter hpet_mmap is not set) user access to the
548 registers for applications that require it.
550 config HANGCHECK_TIMER
551 tristate "Hangcheck timer"
552 depends on X86 || IA64 || PPC64 || S390
553 help
554 The hangcheck-timer module detects when the system has gone
555 out to lunch past a certain margin. It can reboot the system
556 or merely print a warning.
558 config MMTIMER
559 tristate "MMTIMER Memory mapped RTC for SGI Altix"
560 depends on IA64_GENERIC || IA64_SGI_SN2
561 default y
562 help
563 The mmtimer device allows direct userspace access to the
564 Altix system timer.
566 config UV_MMTIMER
567 tristate "UV_MMTIMER Memory mapped RTC for SGI UV"
568 depends on X86_UV
569 default m
570 help
571 The uv_mmtimer device allows direct userspace access to the
572 UV system timer.
574 source "drivers/char/tpm/Kconfig"
576 config TELCLOCK
577 tristate "Telecom clock driver for ATCA SBC"
578 depends on X86
579 default n
580 help
581 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
582 ATCA computers and allows direct userspace access to the
583 configuration of the telecom clock configuration settings. This
584 device is used for hardware synchronization across the ATCA backplane
585 fabric. Upon loading, the driver exports a sysfs directory,
586 /sys/devices/platform/telco_clock, with a number of files for
587 controlling the behavior of this hardware.
589 config DEVPORT
590 bool
591 depends on !M68K
592 depends on ISA || PCI
593 default y
595 config DCC_TTY
596 tristate "DCC tty driver"
597 depends on ARM
599 source "drivers/s390/char/Kconfig"
601 config MSM_SMD_PKT
602 bool "Enable device interface for some SMD packet ports"
603 default n
604 depends on MSM_SMD
605 help
606 Enables userspace clients to read and write to some packet SMD
607 ports via device interface for MSM chipset.
609 config TILE_SROM
610 bool "Character-device access via hypervisor to the Tilera SPI ROM"
611 depends on TILE
612 default y
613 ---help---
614 This device provides character-level read-write access
615 to the SROM, typically via the "0", "1", and "2" devices
616 in /dev/srom/. The Tilera hypervisor makes the flash
617 device appear much like a simple EEPROM, and knows
618 how to partition a single ROM for multiple purposes.
620 endmenu