Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Character device configuration | |
3 | # | |
4 | ||
5 | menu "Character devices" | |
6 | ||
bdcffc5a | 7 | source "drivers/tty/Kconfig" |
13ae6645 | 8 | |
73f0718e RW |
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 | ||
b781ecb6 AV |
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 | ||
1da177e4 LT |
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 | ||
e1e19747 BL |
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" | |
ae40aae9 | 44 | depends on SGI_TIOCX |
e1e19747 BL |
45 | help |
46 | If you have an SGI Altix with an attached SABrick | |
47 | say Y or M here, otherwise say N. | |
48 | ||
ab4382d2 | 49 | source "drivers/tty/serial/Kconfig" |
1da177e4 | 50 | |
24b4b67d | 51 | config TTY_PRINTK |
b24313a8 | 52 | tristate "TTY driver to output user messages via printk" |
4f73bc4d | 53 | depends on EXPERT && TTY |
24b4b67d SP |
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 | ||
2dc63a84 MF |
66 | config BFIN_OTP |
67 | tristate "Blackfin On-Chip OTP Memory Support" | |
f69b2d7e | 68 | depends on BLACKFIN && (BF51x || BF52x || BF54x) |
2dc63a84 MF |
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 | ||
1da177e4 LT |
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 | ||
bdcffc5a | 155 | source "drivers/tty/hvc/Kconfig" |
5427bcf5 | 156 | |
31610434 | 157 | config VIRTIO_CONSOLE |
7721c494 | 158 | tristate "Virtio console" |
4f73bc4d | 159 | depends on VIRTIO && TTY |
31610434 | 160 | select HVC_DRIVER |
7721c494 CB |
161 | help |
162 | Virtio console for use with lguest and other hypervisors. | |
163 | ||
fb08bd27 AS |
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. | |
31610434 | 172 | |
fe9e8d53 SR |
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 | ||
1da177e4 LT |
181 | source "drivers/char/ipmi/Kconfig" |
182 | ||
1da177e4 LT |
183 | config DS1620 |
184 | tristate "NetWinder thermometer support" | |
185 | depends on ARCH_NETWINDER | |
186 | help | |
187 | Say Y here to include support for the thermal management hardware | |
188 | found in the NetWinder. This driver allows the user to control the | |
189 | temperature set points and to read the current temperature. | |
190 | ||
191 | It is also possible to say M here to build it as a module (ds1620) | |
192 | It is recommended to be used on a NetWinder, but it is not a | |
193 | necessity. | |
194 | ||
195 | config NWBUTTON | |
196 | tristate "NetWinder Button" | |
197 | depends on ARCH_NETWINDER | |
198 | ---help--- | |
199 | If you say Y here and create a character device node /dev/nwbutton | |
200 | with major and minor numbers 10 and 158 ("man mknod"), then every | |
201 | time the orange button is pressed a number of times, the number of | |
202 | times the button was pressed will be written to that device. | |
203 | ||
204 | This is most useful for applications, as yet unwritten, which | |
205 | perform actions based on how many times the button is pressed in a | |
206 | row. | |
207 | ||
208 | Do not hold the button down for too long, as the driver does not | |
209 | alter the behaviour of the hardware reset circuitry attached to the | |
210 | button; it will still execute a hard reset if the button is held | |
211 | down for longer than approximately five seconds. | |
212 | ||
213 | To compile this driver as a module, choose M here: the | |
214 | module will be called nwbutton. | |
215 | ||
216 | Most people will answer Y to this question and "Reboot Using Button" | |
217 | below to be able to initiate a system shutdown from the button. | |
218 | ||
219 | config NWBUTTON_REBOOT | |
220 | bool "Reboot Using Button" | |
221 | depends on NWBUTTON | |
222 | help | |
223 | If you say Y here, then you will be able to initiate a system | |
224 | shutdown and reboot by pressing the orange button a number of times. | |
225 | The number of presses to initiate the shutdown is two by default, | |
226 | but this can be altered by modifying the value of NUM_PRESSES_REBOOT | |
227 | in nwbutton.h and recompiling the driver or, if you compile the | |
228 | driver as a module, you can specify the number of presses at load | |
229 | time with "insmod button reboot_count=<something>". | |
230 | ||
231 | config NWFLASH | |
232 | tristate "NetWinder flash support" | |
233 | depends on ARCH_NETWINDER | |
234 | ---help--- | |
235 | If you say Y here and create a character device /dev/flash with | |
236 | major 10 and minor 160 you can manipulate the flash ROM containing | |
237 | the NetWinder firmware. Be careful as accidentally overwriting the | |
238 | flash contents can render your computer unbootable. On no account | |
239 | allow random users access to this device. :-) | |
240 | ||
241 | To compile this driver as a module, choose M here: the | |
242 | module will be called nwflash. | |
243 | ||
244 | If you're not sure, say N. | |
245 | ||
844dd05f MB |
246 | source "drivers/char/hw_random/Kconfig" |
247 | ||
1da177e4 LT |
248 | config NVRAM |
249 | tristate "/dev/nvram support" | |
807a96cd | 250 | depends on ATARI || X86 || (ARM && RTC_DRV_CMOS) || GENERIC_NVRAM |
1da177e4 LT |
251 | ---help--- |
252 | If you say Y here and create a character special file /dev/nvram | |
253 | with major number 10 and minor number 144 using mknod ("man mknod"), | |
254 | you get read and write access to the extra bytes of non-volatile | |
255 | memory in the real time clock (RTC), which is contained in every PC | |
256 | and most Ataris. The actual number of bytes varies, depending on the | |
257 | nvram in the system, but is usually 114 (128-14 for the RTC). | |
258 | ||
259 | This memory is conventionally called "CMOS RAM" on PCs and "NVRAM" | |
260 | on Ataris. /dev/nvram may be used to view settings there, or to | |
261 | change them (with some utility). It could also be used to frequently | |
262 | save a few bits of very important data that may not be lost over | |
263 | power-off and for which writing to disk is too insecure. Note | |
264 | however that most NVRAM space in a PC belongs to the BIOS and you | |
265 | should NEVER idly tamper with it. See Ralf Brown's interrupt list | |
266 | for a guide to the use of CMOS bytes by your BIOS. | |
267 | ||
268 | On Atari machines, /dev/nvram is always configured and does not need | |
269 | to be selected. | |
270 | ||
271 | To compile this driver as a module, choose M here: the | |
272 | module will be called nvram. | |
273 | ||
c7500900 DB |
274 | # |
275 | # These legacy RTC drivers just cause too many conflicts with the generic | |
276 | # RTC framework ... let's not even try to coexist any more. | |
277 | # | |
278 | if RTC_LIB=n | |
279 | ||
1da177e4 | 280 | config RTC |
e6d2bb2b | 281 | tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)" |
c7500900 | 282 | depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \ |
3369465e | 283 | && !ARM && !SUPERH && !S390 && !AVR32 && !BLACKFIN && !UML |
1da177e4 LT |
284 | ---help--- |
285 | If you say Y here and create a character special file /dev/rtc with | |
286 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
287 | will get access to the real time clock (or hardware clock) built | |
288 | into your computer. | |
289 | ||
290 | Every PC has such a clock built in. It can be used to generate | |
291 | signals from as low as 1Hz up to 8192Hz, and can also be used | |
292 | as a 24 hour alarm. It reports status information via the file | |
293 | /proc/driver/rtc and its behaviour is set by various ioctls on | |
294 | /dev/rtc. | |
295 | ||
296 | If you run Linux on a multiprocessor machine and said Y to | |
297 | "Symmetric Multi Processing" above, you should say Y here to read | |
298 | and set the RTC in an SMP compatible fashion. | |
299 | ||
300 | If you think you have a use for such a device (such as periodic data | |
301 | sampling), then say Y here, and read <file:Documentation/rtc.txt> | |
302 | for details. | |
303 | ||
304 | To compile this driver as a module, choose M here: the | |
305 | module will be called rtc. | |
306 | ||
2240598c AV |
307 | config JS_RTC |
308 | tristate "Enhanced Real Time Clock Support" | |
309 | depends on SPARC32 && PCI | |
310 | ---help--- | |
311 | If you say Y here and create a character special file /dev/rtc with | |
312 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
313 | will get access to the real time clock (or hardware clock) built | |
314 | into your computer. | |
315 | ||
316 | Every PC has such a clock built in. It can be used to generate | |
317 | signals from as low as 1Hz up to 8192Hz, and can also be used | |
318 | as a 24 hour alarm. It reports status information via the file | |
319 | /proc/driver/rtc and its behaviour is set by various ioctls on | |
320 | /dev/rtc. | |
321 | ||
322 | If you think you have a use for such a device (such as periodic data | |
323 | sampling), then say Y here, and read <file:Documentation/rtc.txt> | |
324 | for details. | |
325 | ||
326 | To compile this driver as a module, choose M here: the | |
327 | module will be called js-rtc. | |
328 | ||
1da177e4 LT |
329 | config GEN_RTC |
330 | tristate "Generic /dev/rtc emulation" | |
ba6ed7e1 AB |
331 | depends on RTC!=y |
332 | depends on ALPHA || M68K || MN10300 || PARISC || PPC || X86 | |
1da177e4 LT |
333 | ---help--- |
334 | If you say Y here and create a character special file /dev/rtc with | |
335 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
336 | will get access to the real time clock (or hardware clock) built | |
337 | into your computer. | |
338 | ||
339 | It reports status information via the file /proc/driver/rtc and its | |
340 | behaviour is set by various ioctls on /dev/rtc. If you enable the | |
341 | "extended RTC operation" below it will also provide an emulation | |
342 | for RTC_UIE which is required by some programs and may improve | |
343 | precision in some cases. | |
344 | ||
345 | To compile this driver as a module, choose M here: the | |
346 | module will be called genrtc. | |
347 | ||
348 | config GEN_RTC_X | |
349 | bool "Extended RTC operation" | |
350 | depends on GEN_RTC | |
351 | help | |
352 | Provides an emulation for RTC_UIE which is required by some programs | |
353 | and may improve precision of the generic RTC support in some cases. | |
354 | ||
355 | config EFI_RTC | |
356 | bool "EFI Real Time Clock Services" | |
357 | depends on IA64 | |
358 | ||
359 | config DS1302 | |
360 | tristate "DS1302 RTC support" | |
361 | depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT) | |
362 | help | |
363 | If you say Y here and create a character special file /dev/rtc with | |
364 | major number 121 and minor number 0 using mknod ("man mknod"), you | |
365 | will get access to the real time clock (or hardware clock) built | |
366 | into your computer. | |
367 | ||
c7500900 DB |
368 | endif # RTC_LIB |
369 | ||
1da177e4 LT |
370 | config DTLK |
371 | tristate "Double Talk PC internal speech card support" | |
eeca7a36 | 372 | depends on ISA |
1da177e4 LT |
373 | help |
374 | This driver is for the DoubleTalk PC, a speech synthesizer | |
375 | manufactured by RC Systems (<http://www.rcsys.com/>). It is also | |
376 | called the `internal DoubleTalk'. | |
377 | ||
378 | To compile this driver as a module, choose M here: the | |
379 | module will be called dtlk. | |
380 | ||
ef141a0b SN |
381 | config XILINX_HWICAP |
382 | tristate "Xilinx HWICAP Support" | |
6fa612b5 | 383 | depends on XILINX_VIRTEX || MICROBLAZE |
ef141a0b SN |
384 | help |
385 | This option enables support for Xilinx Internal Configuration | |
386 | Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex | |
387 | FPGA platforms to partially reconfigure the FPGA at runtime. | |
388 | ||
389 | If unsure, say N. | |
390 | ||
1da177e4 LT |
391 | config R3964 |
392 | tristate "Siemens R3964 line discipline" | |
4f73bc4d | 393 | depends on TTY |
1da177e4 LT |
394 | ---help--- |
395 | This driver allows synchronous communication with devices using the | |
396 | Siemens R3964 packet protocol. Unless you are dealing with special | |
397 | hardware like PLCs, you are unlikely to need this. | |
398 | ||
399 | To compile this driver as a module, choose M here: the | |
400 | module will be called n_r3964. | |
401 | ||
402 | If unsure, say N. | |
403 | ||
404 | config APPLICOM | |
405 | tristate "Applicom intelligent fieldbus card support" | |
406 | depends on PCI | |
407 | ---help--- | |
408 | This driver provides the kernel-side support for the intelligent | |
409 | fieldbus cards made by Applicom International. More information | |
410 | about these cards can be found on the WWW at the address | |
411 | <http://www.applicom-int.com/>, or by email from David Woodhouse | |
412 | <dwmw2@infradead.org>. | |
413 | ||
414 | To compile this driver as a module, choose M here: the | |
415 | module will be called applicom. | |
416 | ||
417 | If unsure, say N. | |
418 | ||
419 | config SONYPI | |
65929215 | 420 | tristate "Sony Vaio Programmable I/O Control Device support" |
57dcf020 | 421 | depends on X86_32 && PCI && INPUT |
1da177e4 LT |
422 | ---help--- |
423 | This driver enables access to the Sony Programmable I/O Control | |
424 | Device which can be found in many (all ?) Sony Vaio laptops. | |
425 | ||
426 | If you have one of those laptops, read | |
018a651a | 427 | <file:Documentation/laptops/sonypi.txt>, and say Y or M here. |
1da177e4 LT |
428 | |
429 | To compile this driver as a module, choose M here: the | |
430 | module will be called sonypi. | |
431 | ||
09762516 YY |
432 | config GPIO_TB0219 |
433 | tristate "TANBAC TB0219 GPIO support" | |
bef1f402 | 434 | depends on TANBAC_TB022X |
584e1236 | 435 | select GPIO_VR41XX |
1da177e4 | 436 | |
1da177e4 LT |
437 | source "drivers/char/pcmcia/Kconfig" |
438 | ||
439 | config MWAVE | |
440 | tristate "ACP Modem (Mwave) support" | |
4f73bc4d | 441 | depends on X86 && TTY |
1da177e4 LT |
442 | select SERIAL_8250 |
443 | ---help--- | |
444 | The ACP modem (Mwave) for Linux is a WinModem. It is composed of a | |
445 | kernel driver and a user level application. Together these components | |
446 | support direct attachment to public switched telephone networks (PSTNs) | |
447 | and support selected world wide countries. | |
448 | ||
449 | This version of the ACP Modem driver supports the IBM Thinkpad 600E, | |
450 | 600, and 770 that include on board ACP modem hardware. | |
451 | ||
452 | The modem also supports the standard communications port interface | |
453 | (ttySx) and is compatible with the Hayes AT Command Set. | |
454 | ||
455 | The user level application needed to use this driver can be found at | |
456 | the IBM Linux Technology Center (LTC) web site: | |
457 | <http://www.ibm.com/linux/ltc/>. | |
458 | ||
459 | If you own one of the above IBM Thinkpads which has the Mwave chipset | |
460 | in it, say Y. | |
461 | ||
462 | To compile this driver as a module, choose M here: the | |
463 | module will be called mwave. | |
464 | ||
465 | config SCx200_GPIO | |
466 | tristate "NatSemi SCx200 GPIO Support" | |
467 | depends on SCx200 | |
7a8e2a5e | 468 | select NSC_GPIO |
1da177e4 LT |
469 | help |
470 | Give userspace access to the GPIO pins on the National | |
471 | Semiconductor SCx200 processors. | |
472 | ||
473 | If compiled as a module, it will be called scx200_gpio. | |
474 | ||
7a8e2a5e JC |
475 | config PC8736x_GPIO |
476 | tristate "NatSemi PC8736x GPIO Support" | |
3369465e | 477 | depends on X86_32 && !UML |
7a8e2a5e JC |
478 | default SCx200_GPIO # mostly N |
479 | select NSC_GPIO # needed for support routines | |
480 | help | |
481 | Give userspace access to the GPIO pins on the National | |
482 | Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip | |
483 | has multiple functional units, inc several managed by | |
484 | hwmon/pc87360 driver. Tested with PC-87366 | |
485 | ||
486 | If compiled as a module, it will be called pc8736x_gpio. | |
487 | ||
488 | config NSC_GPIO | |
489 | tristate "NatSemi Base GPIO Support" | |
699352c3 | 490 | depends on X86_32 |
7a8e2a5e JC |
491 | # selected by SCx200_GPIO and PC8736x_GPIO |
492 | # what about 2 selectors differing: m != y | |
493 | help | |
494 | Common support used (and needed) by scx200_gpio and | |
495 | pc8736x_gpio drivers. If those drivers are built as | |
496 | modules, this one will be too, named nsc_gpio | |
497 | ||
1da177e4 | 498 | config RAW_DRIVER |
abd4aa5a | 499 | tristate "RAW driver (/dev/raw/rawN)" |
9361401e | 500 | depends on BLOCK |
1da177e4 | 501 | help |
abd4aa5a DJ |
502 | The raw driver permits block devices to be bound to /dev/raw/rawN. |
503 | Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. | |
1da177e4 LT |
504 | See the raw(8) manpage for more details. |
505 | ||
abd4aa5a | 506 | Applications should preferably open the device (eg /dev/hda1) |
1da177e4 LT |
507 | with the O_DIRECT flag. |
508 | ||
0de502aa | 509 | config MAX_RAW_DEVS |
0078bff5 | 510 | int "Maximum number of RAW devices to support (1-65536)" |
0de502aa | 511 | depends on RAW_DRIVER |
7143479a | 512 | range 1 65536 |
0de502aa AM |
513 | default "256" |
514 | help | |
515 | The maximum number of RAW devices that are supported. | |
516 | Default is 256. Increase this number in case you need lots of | |
517 | raw devices. | |
518 | ||
1da177e4 LT |
519 | config HPET |
520 | bool "HPET - High Precision Event Timer" if (X86 || IA64) | |
521 | default n | |
522 | depends on ACPI | |
523 | help | |
524 | If you say Y here, you will have a miscdevice named "/dev/hpet/". Each | |
525 | open selects one of the timers supported by the HPET. The timers are | |
3cb2fccc | 526 | non-periodic and/or periodic. |
1da177e4 | 527 | |
1da177e4 LT |
528 | config HPET_MMAP |
529 | bool "Allow mmap of HPET" | |
530 | default y | |
531 | depends on HPET | |
532 | help | |
533 | If you say Y here, user applications will be able to mmap | |
534 | the HPET registers. | |
535 | ||
3d035f58 PB |
536 | config HPET_MMAP_DEFAULT |
537 | bool "Enable HPET MMAP access by default" | |
538 | default y | |
539 | depends on HPET_MMAP | |
540 | help | |
1da177e4 LT |
541 | In some hardware implementations, the page containing HPET |
542 | registers may also contain other things that shouldn't be | |
3d035f58 PB |
543 | exposed to the user. This option selects the default (if |
544 | kernel parameter hpet_mmap is not set) user access to the | |
545 | registers for applications that require it. | |
1da177e4 | 546 | |
1da177e4 LT |
547 | config HANGCHECK_TIMER |
548 | tristate "Hangcheck timer" | |
abf3ea1b | 549 | depends on X86 || IA64 || PPC64 || S390 |
1da177e4 LT |
550 | help |
551 | The hangcheck-timer module detects when the system has gone | |
552 | out to lunch past a certain margin. It can reboot the system | |
553 | or merely print a warning. | |
554 | ||
555 | config MMTIMER | |
556 | tristate "MMTIMER Memory mapped RTC for SGI Altix" | |
557 | depends on IA64_GENERIC || IA64_SGI_SN2 | |
558 | default y | |
559 | help | |
560 | The mmtimer device allows direct userspace access to the | |
561 | Altix system timer. | |
562 | ||
fbd8ae10 DS |
563 | config UV_MMTIMER |
564 | tristate "UV_MMTIMER Memory mapped RTC for SGI UV" | |
565 | depends on X86_UV | |
566 | default m | |
567 | help | |
568 | The uv_mmtimer device allows direct userspace access to the | |
569 | UV system timer. | |
570 | ||
1da177e4 LT |
571 | source "drivers/char/tpm/Kconfig" |
572 | ||
1a80ba88 | 573 | config TELCLOCK |
03154a27 | 574 | tristate "Telecom clock driver for ATCA SBC" |
65929215 | 575 | depends on X86 |
1a80ba88 MG |
576 | default n |
577 | help | |
03154a27 MG |
578 | The telecom clock device is specific to the MPCBL0010 and MPCBL0050 |
579 | ATCA computers and allows direct userspace access to the | |
580 | configuration of the telecom clock configuration settings. This | |
581 | device is used for hardware synchronization across the ATCA backplane | |
582 | fabric. Upon loading, the driver exports a sysfs directory, | |
583 | /sys/devices/platform/telco_clock, with a number of files for | |
584 | controlling the behavior of this hardware. | |
1a80ba88 | 585 | |
4f911d64 RK |
586 | config DEVPORT |
587 | bool | |
588 | depends on !M68K | |
589 | depends on ISA || PCI | |
590 | default y | |
591 | ||
61d48c2c MS |
592 | source "drivers/s390/char/Kconfig" |
593 | ||
dbcb4a1a CM |
594 | config TILE_SROM |
595 | bool "Character-device access via hypervisor to the Tilera SPI ROM" | |
596 | depends on TILE | |
597 | default y | |
598 | ---help--- | |
599 | This device provides character-level read-write access | |
600 | to the SROM, typically via the "0", "1", and "2" devices | |
601 | in /dev/srom/. The Tilera hypervisor makes the flash | |
602 | device appear much like a simple EEPROM, and knows | |
603 | how to partition a single ROM for multiple purposes. | |
604 | ||
7051924f EB |
605 | source "drivers/char/xillybus/Kconfig" |
606 | ||
1da177e4 LT |
607 | endmenu |
608 |