source: src/linux/universal/linux-4.4/drivers/char/Kconfig @ 31885

Last change on this file since 31885 was 31885, checked in by brainslayer, 4 months ago

update

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