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