Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479
  1. #
  2. # Misc strange devices
  3. #
  4. menuconfig MISC_DEVICES
  5. bool "Misc devices"
  6. default y
  7. ---help---
  8. Say Y here to get to see options for device drivers from various
  9. different categories. This option alone does not add any kernel code.
  10. If you say N, all options in this submenu will be skipped and disabled.
  11. if MISC_DEVICES
  12. config ATMEL_PWM
  13. tristate "Atmel AT32/AT91 PWM support"
  14. depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
  15. help
  16. This option enables device driver support for the PWM channels
  17. on certain Atmel prcoessors. Pulse Width Modulation is used for
  18. purposes including software controlled power-efficent backlights
  19. on LCD displays, motor control, and waveform generation.
  20. config ATMEL_TCLIB
  21. bool "Atmel AT32/AT91 Timer/Counter Library"
  22. depends on (AVR32 || ARCH_AT91)
  23. help
  24. Select this if you want a library to allocate the Timer/Counter
  25. blocks found on many Atmel processors. This facilitates using
  26. these blocks by different drivers despite processor differences.
  27. config ATMEL_TCB_CLKSRC
  28. bool "TC Block Clocksource"
  29. depends on ATMEL_TCLIB && GENERIC_TIME
  30. default y
  31. help
  32. Select this to get a high precision clocksource based on a
  33. TC block with a 5+ MHz base clock rate. Two timer channels
  34. are combined to make a single 32-bit timer.
  35. When GENERIC_CLOCKEVENTS is defined, the third timer channel
  36. may be used as a clock event device supporting oneshot mode
  37. (delays of up to two seconds) based on the 32 KiHz clock.
  38. config ATMEL_TCB_CLKSRC_BLOCK
  39. int
  40. depends on ATMEL_TCB_CLKSRC
  41. prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
  42. default 0
  43. range 0 1
  44. help
  45. Some chips provide more than one TC block, so you have the
  46. choice of which one to use for the clock framework. The other
  47. TC can be used for other purposes, such as PWM generation and
  48. interval timing.
  49. config IBM_ASM
  50. tristate "Device driver for IBM RSA service processor"
  51. depends on X86 && PCI && INPUT && EXPERIMENTAL
  52. ---help---
  53. This option enables device driver support for in-band access to the
  54. IBM RSA (Condor) service processor in eServer xSeries systems.
  55. The ibmasm device driver allows user space application to access
  56. ASM (Advanced Systems Management) functions on the service
  57. processor. The driver is meant to be used in conjunction with
  58. a user space API.
  59. The ibmasm driver also enables the OS to use the UART on the
  60. service processor board as a regular serial port. To make use of
  61. this feature serial driver support (CONFIG_SERIAL_8250) must be
  62. enabled.
  63. WARNING: This software may not be supported or function
  64. correctly on your IBM server. Please consult the IBM ServerProven
  65. website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
  66. information on the specific driver level and support statement
  67. for your IBM server.
  68. config PHANTOM
  69. tristate "Sensable PHANToM (PCI)"
  70. depends on PCI
  71. help
  72. Say Y here if you want to build a driver for Sensable PHANToM device.
  73. This driver is only for PCI PHANToMs.
  74. If you choose to build module, its name will be phantom. If unsure,
  75. say N here.
  76. config EEPROM_93CX6
  77. tristate "EEPROM 93CX6 support"
  78. ---help---
  79. This is a driver for the EEPROM chipsets 93c46 and 93c66.
  80. The driver supports both read as well as write commands.
  81. If unsure, say N.
  82. config SGI_IOC4
  83. tristate "SGI IOC4 Base IO support"
  84. depends on PCI
  85. ---help---
  86. This option enables basic support for the IOC4 chip on certain
  87. SGI IO controller cards (IO9, IO10, and PCI-RT). This option
  88. does not enable any specific functions on such a card, but provides
  89. necessary infrastructure for other drivers to utilize.
  90. If you have an SGI Altix with an IOC4-based card say Y.
  91. Otherwise say N.
  92. config TIFM_CORE
  93. tristate "TI Flash Media interface support (EXPERIMENTAL)"
  94. depends on EXPERIMENTAL && PCI
  95. help
  96. If you want support for Texas Instruments(R) Flash Media adapters
  97. you should select this option and then also choose an appropriate
  98. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  99. support', if you have a TI PCI74xx compatible card reader, for
  100. example.
  101. You will also have to select some flash card format drivers. MMC/SD
  102. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  103. Interface support (MMC_TIFM_SD)'.
  104. To compile this driver as a module, choose M here: the module will
  105. be called tifm_core.
  106. config TIFM_7XX1
  107. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
  108. depends on PCI && TIFM_CORE && EXPERIMENTAL
  109. default TIFM_CORE
  110. help
  111. This option enables support for Texas Instruments(R) PCI74xx and
  112. PCI76xx families of Flash Media adapters, found in many laptops.
  113. To make actual use of the device, you will have to select some
  114. flash card format drivers, as outlined in the TIFM_CORE Help.
  115. To compile this driver as a module, choose M here: the module will
  116. be called tifm_7xx1.
  117. config ACER_WMI
  118. tristate "Acer WMI Laptop Extras (EXPERIMENTAL)"
  119. depends on X86
  120. depends on EXPERIMENTAL
  121. depends on ACPI
  122. depends on LEDS_CLASS
  123. depends on NEW_LEDS
  124. depends on BACKLIGHT_CLASS_DEVICE
  125. depends on SERIO_I8042
  126. select ACPI_WMI
  127. ---help---
  128. This is a driver for newer Acer (and Wistron) laptops. It adds
  129. wireless radio and bluetooth control, and on some laptops,
  130. exposes the mail LED and LCD backlight.
  131. For more information about this driver see
  132. <file:Documentation/laptops/acer-wmi.txt>
  133. If you have an ACPI-WMI compatible Acer/ Wistron laptop, say Y or M
  134. here.
  135. config ASUS_LAPTOP
  136. tristate "Asus Laptop Extras (EXPERIMENTAL)"
  137. depends on X86
  138. depends on ACPI
  139. depends on EXPERIMENTAL && !ACPI_ASUS
  140. depends on LEDS_CLASS
  141. depends on NEW_LEDS
  142. depends on BACKLIGHT_CLASS_DEVICE
  143. ---help---
  144. This is the new Linux driver for Asus laptops. It may also support some
  145. MEDION, JVC or VICTOR laptops. It makes all the extra buttons generate
  146. standard ACPI events that go through /proc/acpi/events. It also adds
  147. support for video output switching, LCD backlight control, Bluetooth and
  148. Wlan control, and most importantly, allows you to blink those fancy LEDs.
  149. For more information and a userspace daemon for handling the extra
  150. buttons see <http://acpi4asus.sf.net/>.
  151. If you have an ACPI-compatible ASUS laptop, say Y or M here.
  152. config FUJITSU_LAPTOP
  153. tristate "Fujitsu Laptop Extras"
  154. depends on X86
  155. depends on ACPI
  156. depends on INPUT
  157. depends on BACKLIGHT_CLASS_DEVICE
  158. ---help---
  159. This is a driver for laptops built by Fujitsu:
  160. * P2xxx/P5xxx/S6xxx/S7xxx series Lifebooks
  161. * Possibly other Fujitsu laptop models
  162. * Tested with S6410 and S7020
  163. It adds support for LCD brightness control and some hotkeys.
  164. If you have a Fujitsu laptop, say Y or M here.
  165. config FUJITSU_LAPTOP_DEBUG
  166. bool "Verbose debug mode for Fujitsu Laptop Extras"
  167. depends on FUJITSU_LAPTOP
  168. default n
  169. ---help---
  170. Enables extra debug output from the fujitsu extras driver, at the
  171. expense of a slight increase in driver size.
  172. If you are not sure, say N here.
  173. config TC1100_WMI
  174. tristate "HP Compaq TC1100 Tablet WMI Extras (EXPERIMENTAL)"
  175. depends on X86 && !X86_64
  176. depends on EXPERIMENTAL
  177. depends on ACPI
  178. select ACPI_WMI
  179. ---help---
  180. This is a driver for the WMI extensions (wireless and bluetooth power
  181. control) of the HP Compaq TC1100 tablet.
  182. config HP_WMI
  183. tristate "HP WMI extras"
  184. depends on ACPI_WMI
  185. depends on INPUT
  186. depends on RFKILL
  187. help
  188. Say Y here if you want to support WMI-based hotkeys on HP laptops and
  189. to read data from WMI such as docking or ambient light sensor state.
  190. To compile this driver as a module, choose M here: the module will
  191. be called hp-wmi.
  192. config MSI_LAPTOP
  193. tristate "MSI Laptop Extras"
  194. depends on X86
  195. depends on ACPI_EC
  196. depends on BACKLIGHT_CLASS_DEVICE
  197. ---help---
  198. This is a driver for laptops built by MSI (MICRO-STAR
  199. INTERNATIONAL):
  200. MSI MegaBook S270 (MS-1013)
  201. Cytron/TCM/Medion/Tchibo MD96100/SAM2000
  202. It adds support for Bluetooth, WLAN and LCD brightness control.
  203. More information about this driver is available at
  204. <http://0pointer.de/lennart/tchibo.html>.
  205. If you have an MSI S270 laptop, say Y or M here.
  206. config COMPAL_LAPTOP
  207. tristate "Compal Laptop Extras"
  208. depends on X86
  209. depends on ACPI_EC
  210. depends on BACKLIGHT_CLASS_DEVICE
  211. ---help---
  212. This is a driver for laptops built by Compal:
  213. Compal FL90/IFL90
  214. Compal FL91/IFL91
  215. Compal FL92/JFL92
  216. Compal FT00/IFT00
  217. It adds support for Bluetooth, WLAN and LCD brightness control.
  218. If you have an Compal FL9x/IFL9x/FT00 laptop, say Y or M here.
  219. config SONY_LAPTOP
  220. tristate "Sony Laptop Extras"
  221. depends on X86 && ACPI
  222. select BACKLIGHT_CLASS_DEVICE
  223. depends on INPUT
  224. ---help---
  225. This mini-driver drives the SNC and SPIC devices present in the ACPI
  226. BIOS of the Sony Vaio laptops.
  227. It gives access to some extra laptop functionalities like Bluetooth,
  228. screen brightness control, Fn keys and allows powering on/off some
  229. devices.
  230. Read <file:Documentation/laptops/sony-laptop.txt> for more information.
  231. config SONYPI_COMPAT
  232. bool "Sonypi compatibility"
  233. depends on SONY_LAPTOP
  234. ---help---
  235. Build the sonypi driver compatibility code into the sony-laptop driver.
  236. config THINKPAD_ACPI
  237. tristate "ThinkPad ACPI Laptop Extras"
  238. depends on X86 && ACPI
  239. select BACKLIGHT_LCD_SUPPORT
  240. select BACKLIGHT_CLASS_DEVICE
  241. select HWMON
  242. select NVRAM
  243. select INPUT
  244. select NEW_LEDS
  245. select LEDS_CLASS
  246. select NET
  247. select RFKILL
  248. ---help---
  249. This is a driver for the IBM and Lenovo ThinkPad laptops. It adds
  250. support for Fn-Fx key combinations, Bluetooth control, video
  251. output switching, ThinkLight control, UltraBay eject and more.
  252. For more information about this driver see
  253. <file:Documentation/laptops/thinkpad-acpi.txt> and
  254. <http://ibm-acpi.sf.net/> .
  255. This driver was formerly known as ibm-acpi.
  256. If you have an IBM or Lenovo ThinkPad laptop, say Y or M here.
  257. config THINKPAD_ACPI_DEBUG
  258. bool "Verbose debug mode"
  259. depends on THINKPAD_ACPI
  260. default n
  261. ---help---
  262. Enables extra debugging information, at the expense of a slightly
  263. increase in driver size.
  264. If you are not sure, say N here.
  265. config THINKPAD_ACPI_DOCK
  266. bool "Legacy Docking Station Support"
  267. depends on THINKPAD_ACPI
  268. depends on ACPI_DOCK=n
  269. default n
  270. ---help---
  271. Allows the thinkpad_acpi driver to handle docking station events.
  272. This support was made obsolete by the generic ACPI docking station
  273. support (CONFIG_ACPI_DOCK). It will allow locking and removing the
  274. laptop from the docking station, but will not properly connect PCI
  275. devices.
  276. If you are not sure, say N here.
  277. config THINKPAD_ACPI_BAY
  278. bool "Legacy Removable Bay Support"
  279. depends on THINKPAD_ACPI
  280. default y
  281. ---help---
  282. Allows the thinkpad_acpi driver to handle removable bays. It will
  283. electrically disable the device in the bay, and also generate
  284. notifications when the bay lever is ejected or inserted.
  285. If you are not sure, say Y here.
  286. config THINKPAD_ACPI_VIDEO
  287. bool "Video output control support"
  288. depends on THINKPAD_ACPI
  289. default y
  290. ---help---
  291. Allows the thinkpad_acpi driver to provide an interface to control
  292. the various video output ports.
  293. This feature often won't work well, depending on ThinkPad model,
  294. display state, video output devices in use, whether there is a X
  295. server running, phase of the moon, and the current mood of
  296. Schroedinger's cat. If you can use X.org's RandR to control
  297. your ThinkPad's video output ports instead of this feature,
  298. don't think twice: do it and say N here to save some memory.
  299. If you are not sure, say Y here.
  300. config THINKPAD_ACPI_HOTKEY_POLL
  301. bool "Support NVRAM polling for hot keys"
  302. depends on THINKPAD_ACPI
  303. default y
  304. ---help---
  305. Some thinkpad models benefit from NVRAM polling to detect a few of
  306. the hot key press events. If you know your ThinkPad model does not
  307. need to do NVRAM polling to support any of the hot keys you use,
  308. unselecting this option will save about 1kB of memory.
  309. ThinkPads T40 and newer, R52 and newer, and X31 and newer are
  310. unlikely to need NVRAM polling in their latest BIOS versions.
  311. NVRAM polling can detect at most the following keys: ThinkPad/Access
  312. IBM, Zoom, Switch Display (fn+F7), ThinkLight, Volume up/down/mute,
  313. Brightness up/down, Display Expand (fn+F8), Hibernate (fn+F12).
  314. If you are not sure, say Y here. The driver enables polling only if
  315. it is strictly necessary to do so.
  316. config ATMEL_SSC
  317. tristate "Device driver for Atmel SSC peripheral"
  318. depends on AVR32 || ARCH_AT91
  319. ---help---
  320. This option enables device driver support for Atmel Syncronized
  321. Serial Communication peripheral (SSC).
  322. The SSC peripheral supports a wide variety of serial frame based
  323. communications, i.e. I2S, SPI, etc.
  324. If unsure, say N.
  325. config INTEL_MENLOW
  326. tristate "Thermal Management driver for Intel menlow platform"
  327. depends on ACPI_THERMAL
  328. select THERMAL
  329. depends on X86
  330. ---help---
  331. ACPI thermal management enhancement driver on
  332. Intel Menlow platform.
  333. If unsure, say N.
  334. config EEEPC_LAPTOP
  335. tristate "Eee PC Hotkey Driver (EXPERIMENTAL)"
  336. depends on X86
  337. depends on ACPI
  338. depends on BACKLIGHT_CLASS_DEVICE
  339. depends on HWMON
  340. depends on EXPERIMENTAL
  341. depends on RFKILL
  342. ---help---
  343. This driver supports the Fn-Fx keys on Eee PC laptops.
  344. It also adds the ability to switch camera/wlan on/off.
  345. If you have an Eee PC laptop, say Y or M here.
  346. config ENCLOSURE_SERVICES
  347. tristate "Enclosure Services"
  348. default n
  349. help
  350. Provides support for intelligent enclosures (bays which
  351. contain storage devices). You also need either a host
  352. driver (SCSI/ATA) which supports enclosures
  353. or a SCSI enclosure device (SES) to use these services.
  354. config SGI_XP
  355. tristate "Support communication between SGI SSIs"
  356. depends on NET
  357. depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_64) && SMP
  358. select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  359. select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  360. select SGI_GRU if (IA64_GENERIC || IA64_SGI_UV || X86_64) && SMP
  361. ---help---
  362. An SGI machine can be divided into multiple Single System
  363. Images which act independently of each other and have
  364. hardware based memory protection from the others. Enabling
  365. this feature will allow for direct communication between SSIs
  366. based on a network adapter and DMA messaging.
  367. config HP_ILO
  368. tristate "Channel interface driver for HP iLO/iLO2 processor"
  369. depends on PCI
  370. default n
  371. help
  372. The channel interface driver allows applications to communicate
  373. with iLO/iLO2 management processors present on HP ProLiant
  374. servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
  375. which can be used to gather data from the management processor,
  376. via read and write system calls.
  377. To compile this driver as a module, choose M here: the
  378. module will be called hpilo.
  379. config SGI_GRU
  380. tristate "SGI GRU driver"
  381. depends on (X86_64 || IA64_SGI_UV || IA64_GENERIC) && SMP
  382. default n
  383. select MMU_NOTIFIER
  384. ---help---
  385. The GRU is a hardware resource located in the system chipset. The GRU
  386. contains memory that can be mmapped into the user address space. This memory is
  387. used to communicate with the GRU to perform functions such as load/store,
  388. scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
  389. instructions using user virtual addresses. GRU instructions (ex., bcopy) use
  390. user virtual addresses for operands.
  391. If you are not running on a SGI UV system, say N.
  392. config SGI_GRU_DEBUG
  393. bool "SGI GRU driver debug"
  394. depends on SGI_GRU
  395. default n
  396. ---help---
  397. This option enables addition debugging code for the SGI GRU driver. If
  398. you are unsure, say N.
  399. endif # MISC_DEVICES