Version:  2.0.40 2.2.26 2.4.37 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8

Linux/drivers/char/Kconfig

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

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us