2 # Character device configuration
5 menu "Character devices"
7 source "drivers/tty/Kconfig"
10 bool "Memory device driver"
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.
23 bool "/dev/kmem virtual device support"
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".
32 bool "Stallion multiport serial support"
33 depends on SERIAL_NONSTANDARD
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
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
44 bool "SGI Altix system controller communication support"
45 depends on (IA64_SGI_SN2 || IA64_GENERIC)
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.
52 bool "SGI TIO CX driver support"
53 depends on (IA64_SGI_SN2 || IA64_GENERIC)
55 If you have an SGI Altix and you have fpga devices attached
56 to your TIO, say Y here, otherwise say N.
59 tristate "SGI FPGA Core Services driver support"
62 If you have an SGI Altix with an attached SABrick
63 say Y or M here, otherwise say N.
65 source "drivers/tty/serial/Kconfig"
67 config TS0710_MUX_ENABLE
68 bool "Enable Spreadtrum ts0710 mux driver"
71 This driver is used to support spreadtrum ts0710 mux.
74 bool "MODEM interface"
77 This module supports to connect AP with CP by SPI or SDIO bus.
79 config MUX_SDIO_OPT1_HAL
80 bool "MUX SDIO OPT1 HAL"
83 This module supports to connect AP with CP use SDIO bus.And
84 will support the SDIO transfer option "DMA_OPT_1".
87 bool "TTY driver to output user messages via printk"
88 depends on EXPERT && TTY
91 If you say Y here, the support for writing user messages (i.e.
92 console messages) via printk is available.
94 The feature is useful to inline user messages with kernel
96 In order to use this feature, you should output user messages
97 to /dev/ttyprintk or redirect console to this TTY.
102 tristate "Blackfin On-Chip OTP Memory Support"
103 depends on BLACKFIN && (BF51x || BF52x || BF54x)
106 If you say Y here, you will get support for a character device
107 interface into the One Time Programmable memory pages that are
108 stored on the Blackfin processor. This will not get you access
109 to the secure memory pages however. You will need to write your
110 own secure code and reader for that.
112 To compile this driver as a module, choose M here: the module
113 will be called bfin-otp.
115 If unsure, it is safe to say Y.
117 config BFIN_OTP_WRITE_ENABLE
118 bool "Enable writing support of OTP pages"
122 If you say Y here, you will enable support for writing of the
123 OTP pages. This is dangerous by nature as you can only program
124 the pages once, so only enable this option when you actually
125 need it so as to not inadvertently clobber data.
130 tristate "Parallel printer support"
133 If you intend to attach a printer to the parallel port of your Linux
134 box (as opposed to using a serial printer; if the connector at the
135 printer has 9 or 25 holes ["female"], then it's serial), say Y.
136 Also read the Printing-HOWTO, available from
137 <http://www.tldp.org/docs.html#howto>.
139 It is possible to share one parallel port among several devices
140 (e.g. printer and ZIP drive) and it is safe to compile the
141 corresponding drivers into the kernel.
143 To compile this driver as a module, choose M here and read
144 <file:Documentation/parport.txt>. The module will be called lp.
146 If you have several parallel ports, you can specify which ports to
147 use with the "lp" kernel command line option. (Try "man bootparam"
148 or see the documentation of your boot loader (lilo or loadlin) about
149 how to pass options to the kernel at boot time.) The syntax of the
150 "lp" command line option can be found in <file:drivers/char/lp.c>.
152 If you have more than 8 printers, you need to increase the LP_NO
153 macro in lp.c and the PARPORT_MAX macro in parport.h.
156 bool "Support for console on line printer"
159 If you want kernel messages to be printed out as they occur, you
160 can have a console on the printer. This option adds support for
161 doing that; to actually get it to happen you need to pass the
162 option "console=lp0" to the kernel at boot time.
164 If the printer is out of paper (or off, or unplugged, or too
165 busy..) the kernel will stall until the printer is ready again.
166 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
167 can make the kernel continue when this happens,
168 but it'll lose the kernel messages.
173 tristate "Support for user-space parallel port device drivers"
176 Saying Y to this adds support for /dev/parport device nodes. This
177 is needed for programs that want portable access to the parallel
178 port, for instance deviceid (which displays Plug-and-Play device
181 This is the parallel port equivalent of SCSI generic support (sg).
182 It is safe to say N to this -- it is not needed for normal printing
183 or parallel port CD-ROM/disk support.
185 To compile this driver as a module, choose M here: the
186 module will be called ppdev.
190 source "drivers/tty/hvc/Kconfig"
192 config VIRTIO_CONSOLE
193 tristate "Virtio console"
194 depends on VIRTIO && TTY
197 Virtio console for use with lguest and other hypervisors.
199 Also serves as a general-purpose serial device for data
200 transfer between the guest and host. Character devices at
201 /dev/vportNpn will be created when corresponding ports are
202 found, where N is the device number and n is the port number
203 within that device. If specified by the host, a sysfs
204 attribute called 'name' will be populated with a name for
205 the port which can be used by udev scripts to create a
206 symlink to the device.
209 tristate "IBM POWER Barrier Synchronization Register support"
210 depends on PPC_PSERIES
212 This devices exposes a hardware mechanism for fast synchronization
213 of threads across a large system which avoids bouncing a cacheline
214 between several cores on a system
216 source "drivers/char/ipmi/Kconfig"
219 tristate "NetWinder thermometer support"
220 depends on ARCH_NETWINDER
222 Say Y here to include support for the thermal management hardware
223 found in the NetWinder. This driver allows the user to control the
224 temperature set points and to read the current temperature.
226 It is also possible to say M here to build it as a module (ds1620)
227 It is recommended to be used on a NetWinder, but it is not a
231 tristate "NetWinder Button"
232 depends on ARCH_NETWINDER
234 If you say Y here and create a character device node /dev/nwbutton
235 with major and minor numbers 10 and 158 ("man mknod"), then every
236 time the orange button is pressed a number of times, the number of
237 times the button was pressed will be written to that device.
239 This is most useful for applications, as yet unwritten, which
240 perform actions based on how many times the button is pressed in a
243 Do not hold the button down for too long, as the driver does not
244 alter the behaviour of the hardware reset circuitry attached to the
245 button; it will still execute a hard reset if the button is held
246 down for longer than approximately five seconds.
248 To compile this driver as a module, choose M here: the
249 module will be called nwbutton.
251 Most people will answer Y to this question and "Reboot Using Button"
252 below to be able to initiate a system shutdown from the button.
254 config NWBUTTON_REBOOT
255 bool "Reboot Using Button"
258 If you say Y here, then you will be able to initiate a system
259 shutdown and reboot by pressing the orange button a number of times.
260 The number of presses to initiate the shutdown is two by default,
261 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
262 in nwbutton.h and recompiling the driver or, if you compile the
263 driver as a module, you can specify the number of presses at load
264 time with "insmod button reboot_count=<something>".
267 tristate "NetWinder flash support"
268 depends on ARCH_NETWINDER
270 If you say Y here and create a character device /dev/flash with
271 major 10 and minor 160 you can manipulate the flash ROM containing
272 the NetWinder firmware. Be careful as accidentally overwriting the
273 flash contents can render your computer unbootable. On no account
274 allow random users access to this device. :-)
276 To compile this driver as a module, choose M here: the
277 module will be called nwflash.
279 If you're not sure, say N.
281 source "drivers/char/hw_random/Kconfig"
284 tristate "/dev/nvram support"
285 depends on ATARI || X86 || (ARM && RTC_DRV_CMOS) || GENERIC_NVRAM
287 If you say Y here and create a character special file /dev/nvram
288 with major number 10 and minor number 144 using mknod ("man mknod"),
289 you get read and write access to the extra bytes of non-volatile
290 memory in the real time clock (RTC), which is contained in every PC
291 and most Ataris. The actual number of bytes varies, depending on the
292 nvram in the system, but is usually 114 (128-14 for the RTC).
294 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
295 on Ataris. /dev/nvram may be used to view settings there, or to
296 change them (with some utility). It could also be used to frequently
297 save a few bits of very important data that may not be lost over
298 power-off and for which writing to disk is too insecure. Note
299 however that most NVRAM space in a PC belongs to the BIOS and you
300 should NEVER idly tamper with it. See Ralf Brown's interrupt list
301 for a guide to the use of CMOS bytes by your BIOS.
303 On Atari machines, /dev/nvram is always configured and does not need
306 To compile this driver as a module, choose M here: the
307 module will be called nvram.
310 # These legacy RTC drivers just cause too many conflicts with the generic
311 # RTC framework ... let's not even try to coexist any more.
316 tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
317 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
318 && !ARM && !SUPERH && !S390 && !AVR32 && !BLACKFIN && !UML
320 If you say Y here and create a character special file /dev/rtc with
321 major number 10 and minor number 135 using mknod ("man mknod"), you
322 will get access to the real time clock (or hardware clock) built
325 Every PC has such a clock built in. It can be used to generate
326 signals from as low as 1Hz up to 8192Hz, and can also be used
327 as a 24 hour alarm. It reports status information via the file
328 /proc/driver/rtc and its behaviour is set by various ioctls on
331 If you run Linux on a multiprocessor machine and said Y to
332 "Symmetric Multi Processing" above, you should say Y here to read
333 and set the RTC in an SMP compatible fashion.
335 If you think you have a use for such a device (such as periodic data
336 sampling), then say Y here, and read <file:Documentation/rtc.txt>
339 To compile this driver as a module, choose M here: the
340 module will be called rtc.
343 tristate "Enhanced Real Time Clock Support"
344 depends on SPARC32 && PCI
346 If you say Y here and create a character special file /dev/rtc with
347 major number 10 and minor number 135 using mknod ("man mknod"), you
348 will get access to the real time clock (or hardware clock) built
351 Every PC has such a clock built in. It can be used to generate
352 signals from as low as 1Hz up to 8192Hz, and can also be used
353 as a 24 hour alarm. It reports status information via the file
354 /proc/driver/rtc and its behaviour is set by various ioctls on
357 If you think you have a use for such a device (such as periodic data
358 sampling), then say Y here, and read <file:Documentation/rtc.txt>
361 To compile this driver as a module, choose M here: the
362 module will be called js-rtc.
365 tristate "Generic /dev/rtc emulation"
366 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32 && !BLACKFIN && !UML
368 If you say Y here and create a character special file /dev/rtc with
369 major number 10 and minor number 135 using mknod ("man mknod"), you
370 will get access to the real time clock (or hardware clock) built
373 It reports status information via the file /proc/driver/rtc and its
374 behaviour is set by various ioctls on /dev/rtc. If you enable the
375 "extended RTC operation" below it will also provide an emulation
376 for RTC_UIE which is required by some programs and may improve
377 precision in some cases.
379 To compile this driver as a module, choose M here: the
380 module will be called genrtc.
383 bool "Extended RTC operation"
386 Provides an emulation for RTC_UIE which is required by some programs
387 and may improve precision of the generic RTC support in some cases.
390 bool "EFI Real Time Clock Services"
394 tristate "DS1302 RTC support"
395 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
397 If you say Y here and create a character special file /dev/rtc with
398 major number 121 and minor number 0 using mknod ("man mknod"), you
399 will get access to the real time clock (or hardware clock) built
405 tristate "Double Talk PC internal speech card support"
408 This driver is for the DoubleTalk PC, a speech synthesizer
409 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
410 called the `internal DoubleTalk'.
412 To compile this driver as a module, choose M here: the
413 module will be called dtlk.
416 tristate "Xilinx HWICAP Support"
417 depends on XILINX_VIRTEX || MICROBLAZE
419 This option enables support for Xilinx Internal Configuration
420 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
421 FPGA platforms to partially reconfigure the FPGA at runtime.
426 tristate "Siemens R3964 line discipline"
429 This driver allows synchronous communication with devices using the
430 Siemens R3964 packet protocol. Unless you are dealing with special
431 hardware like PLCs, you are unlikely to need this.
433 To compile this driver as a module, choose M here: the
434 module will be called n_r3964.
439 tristate "Applicom intelligent fieldbus card support"
442 This driver provides the kernel-side support for the intelligent
443 fieldbus cards made by Applicom International. More information
444 about these cards can be found on the WWW at the address
445 <http://www.applicom-int.com/>, or by email from David Woodhouse
446 <dwmw2@infradead.org>.
448 To compile this driver as a module, choose M here: the
449 module will be called applicom.
454 tristate "Sony Vaio Programmable I/O Control Device support"
455 depends on X86 && PCI && INPUT && !64BIT
457 This driver enables access to the Sony Programmable I/O Control
458 Device which can be found in many (all ?) Sony Vaio laptops.
460 If you have one of those laptops, read
461 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
463 To compile this driver as a module, choose M here: the
464 module will be called sonypi.
467 tristate "TANBAC TB0219 GPIO support"
468 depends on TANBAC_TB022X
471 source "drivers/char/pcmcia/Kconfig"
474 tristate "ACP Modem (Mwave) support"
475 depends on X86 && TTY
478 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
479 kernel driver and a user level application. Together these components
480 support direct attachment to public switched telephone networks (PSTNs)
481 and support selected world wide countries.
483 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
484 600, and 770 that include on board ACP modem hardware.
486 The modem also supports the standard communications port interface
487 (ttySx) and is compatible with the Hayes AT Command Set.
489 The user level application needed to use this driver can be found at
490 the IBM Linux Technology Center (LTC) web site:
491 <http://www.ibm.com/linux/ltc/>.
493 If you own one of the above IBM Thinkpads which has the Mwave chipset
496 To compile this driver as a module, choose M here: the
497 module will be called mwave.
500 tristate "NatSemi SCx200 GPIO Support"
504 Give userspace access to the GPIO pins on the National
505 Semiconductor SCx200 processors.
507 If compiled as a module, it will be called scx200_gpio.
510 tristate "NatSemi PC8736x GPIO Support"
511 depends on X86_32 && !UML
512 default SCx200_GPIO # mostly N
513 select NSC_GPIO # needed for support routines
515 Give userspace access to the GPIO pins on the National
516 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
517 has multiple functional units, inc several managed by
518 hwmon/pc87360 driver. Tested with PC-87366
520 If compiled as a module, it will be called pc8736x_gpio.
523 tristate "NatSemi Base GPIO Support"
525 # selected by SCx200_GPIO and PC8736x_GPIO
526 # what about 2 selectors differing: m != y
528 Common support used (and needed) by scx200_gpio and
529 pc8736x_gpio drivers. If those drivers are built as
530 modules, this one will be too, named nsc_gpio
533 tristate "RAW driver (/dev/raw/rawN)"
536 The raw driver permits block devices to be bound to /dev/raw/rawN.
537 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
538 See the raw(8) manpage for more details.
540 Applications should preferably open the device (eg /dev/hda1)
541 with the O_DIRECT flag.
544 int "Maximum number of RAW devices to support (1-65536)"
545 depends on RAW_DRIVER
548 The maximum number of RAW devices that are supported.
549 Default is 256. Increase this number in case you need lots of
553 bool "HPET - High Precision Event Timer" if (X86 || IA64)
557 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
558 open selects one of the timers supported by the HPET. The timers are
559 non-periodic and/or periodic.
562 bool "Allow mmap of HPET"
566 If you say Y here, user applications will be able to mmap
569 In some hardware implementations, the page containing HPET
570 registers may also contain other things that shouldn't be
571 exposed to the user. If this applies to your hardware,
574 config HANGCHECK_TIMER
575 tristate "Hangcheck timer"
576 depends on X86 || IA64 || PPC64 || S390
578 The hangcheck-timer module detects when the system has gone
579 out to lunch past a certain margin. It can reboot the system
580 or merely print a warning.
583 tristate "MMTIMER Memory mapped RTC for SGI Altix"
584 depends on IA64_GENERIC || IA64_SGI_SN2
587 The mmtimer device allows direct userspace access to the
591 tristate "UV_MMTIMER Memory mapped RTC for SGI UV"
595 The uv_mmtimer device allows direct userspace access to the
598 source "drivers/char/tpm/Kconfig"
601 tristate "Telecom clock driver for ATCA SBC"
605 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
606 ATCA computers and allows direct userspace access to the
607 configuration of the telecom clock configuration settings. This
608 device is used for hardware synchronization across the ATCA backplane
609 fabric. Upon loading, the driver exports a sysfs directory,
610 /sys/devices/platform/telco_clock, with a number of files for
611 controlling the behavior of this hardware.
616 depends on ISA || PCI
620 tristate "DCC tty driver"
623 source "drivers/s390/char/Kconfig"
626 bool "Enable device interface for some SMD packet ports"
630 Enables userspace clients to read and write to some packet SMD
631 ports via device interface for MSM chipset.
634 bool "Character-device access via hypervisor to the Tilera SPI ROM"
638 This device provides character-level read-write access
639 to the SROM, typically via the "0", "1", and "2" devices
640 in /dev/srom/. The Tilera hypervisor makes the flash
641 device appear much like a simple EEPROM, and knows
642 how to partition a single ROM for multiple purposes.
648 This module supports to connect AP with CP use SPI bus.