]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blob - drivers/misc/Kconfig
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6
[mirror_ubuntu-bionic-kernel.git] / drivers / misc / Kconfig
1 #
2 # Misc strange devices
3 #
4
5 menuconfig MISC_DEVICES
6 bool "Misc devices"
7 default y
8 ---help---
9 Say Y here to get to see options for device drivers from various
10 different categories. This option alone does not add any kernel code.
11
12 If you say N, all options in this submenu will be skipped and disabled.
13
14 if MISC_DEVICES
15
16 config ATMEL_PWM
17 tristate "Atmel AT32/AT91 PWM support"
18 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
19 help
20 This option enables device driver support for the PWM channels
21 on certain Atmel prcoessors. Pulse Width Modulation is used for
22 purposes including software controlled power-efficent backlights
23 on LCD displays, motor control, and waveform generation.
24
25 config ATMEL_TCLIB
26 bool "Atmel AT32/AT91 Timer/Counter Library"
27 depends on (AVR32 || ARCH_AT91)
28 help
29 Select this if you want a library to allocate the Timer/Counter
30 blocks found on many Atmel processors. This facilitates using
31 these blocks by different drivers despite processor differences.
32
33 config ATMEL_TCB_CLKSRC
34 bool "TC Block Clocksource"
35 depends on ATMEL_TCLIB && GENERIC_TIME
36 default y
37 help
38 Select this to get a high precision clocksource based on a
39 TC block with a 5+ MHz base clock rate. Two timer channels
40 are combined to make a single 32-bit timer.
41
42 When GENERIC_CLOCKEVENTS is defined, the third timer channel
43 may be used as a clock event device supporting oneshot mode
44 (delays of up to two seconds) based on the 32 KiHz clock.
45
46 config ATMEL_TCB_CLKSRC_BLOCK
47 int
48 depends on ATMEL_TCB_CLKSRC
49 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
50 default 0
51 range 0 1
52 help
53 Some chips provide more than one TC block, so you have the
54 choice of which one to use for the clock framework. The other
55 TC can be used for other purposes, such as PWM generation and
56 interval timing.
57
58 config IBM_ASM
59 tristate "Device driver for IBM RSA service processor"
60 depends on X86 && PCI && INPUT && EXPERIMENTAL
61 ---help---
62 This option enables device driver support for in-band access to the
63 IBM RSA (Condor) service processor in eServer xSeries systems.
64 The ibmasm device driver allows user space application to access
65 ASM (Advanced Systems Management) functions on the service
66 processor. The driver is meant to be used in conjunction with
67 a user space API.
68 The ibmasm driver also enables the OS to use the UART on the
69 service processor board as a regular serial port. To make use of
70 this feature serial driver support (CONFIG_SERIAL_8250) must be
71 enabled.
72
73 WARNING: This software may not be supported or function
74 correctly on your IBM server. Please consult the IBM ServerProven
75 website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
76 information on the specific driver level and support statement
77 for your IBM server.
78
79 config PHANTOM
80 tristate "Sensable PHANToM (PCI)"
81 depends on PCI
82 help
83 Say Y here if you want to build a driver for Sensable PHANToM device.
84
85 This driver is only for PCI PHANToMs.
86
87 If you choose to build module, its name will be phantom. If unsure,
88 say N here.
89
90 config SGI_IOC4
91 tristate "SGI IOC4 Base IO support"
92 depends on PCI
93 ---help---
94 This option enables basic support for the IOC4 chip on certain
95 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
96 does not enable any specific functions on such a card, but provides
97 necessary infrastructure for other drivers to utilize.
98
99 If you have an SGI Altix with an IOC4-based card say Y.
100 Otherwise say N.
101
102 config TIFM_CORE
103 tristate "TI Flash Media interface support (EXPERIMENTAL)"
104 depends on EXPERIMENTAL && PCI
105 help
106 If you want support for Texas Instruments(R) Flash Media adapters
107 you should select this option and then also choose an appropriate
108 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
109 support', if you have a TI PCI74xx compatible card reader, for
110 example.
111 You will also have to select some flash card format drivers. MMC/SD
112 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
113 Interface support (MMC_TIFM_SD)'.
114
115 To compile this driver as a module, choose M here: the module will
116 be called tifm_core.
117
118 config TIFM_7XX1
119 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
120 depends on PCI && TIFM_CORE && EXPERIMENTAL
121 default TIFM_CORE
122 help
123 This option enables support for Texas Instruments(R) PCI74xx and
124 PCI76xx families of Flash Media adapters, found in many laptops.
125 To make actual use of the device, you will have to select some
126 flash card format drivers, as outlined in the TIFM_CORE Help.
127
128 To compile this driver as a module, choose M here: the module will
129 be called tifm_7xx1.
130
131 config ICS932S401
132 tristate "Integrated Circuits ICS932S401"
133 depends on I2C && EXPERIMENTAL
134 help
135 If you say yes here you get support for the Integrated Circuits
136 ICS932S401 clock control chips.
137
138 This driver can also be built as a module. If so, the module
139 will be called ics932s401.
140
141 config ATMEL_SSC
142 tristate "Device driver for Atmel SSC peripheral"
143 depends on AVR32 || ARCH_AT91
144 ---help---
145 This option enables device driver support for Atmel Syncronized
146 Serial Communication peripheral (SSC).
147
148 The SSC peripheral supports a wide variety of serial frame based
149 communications, i.e. I2S, SPI, etc.
150
151 If unsure, say N.
152
153 config ENCLOSURE_SERVICES
154 tristate "Enclosure Services"
155 default n
156 help
157 Provides support for intelligent enclosures (bays which
158 contain storage devices). You also need either a host
159 driver (SCSI/ATA) which supports enclosures
160 or a SCSI enclosure device (SES) to use these services.
161
162 config SGI_XP
163 tristate "Support communication between SGI SSIs"
164 depends on NET
165 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
166 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
167 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
168 select SGI_GRU if X86_64 && SMP
169 ---help---
170 An SGI machine can be divided into multiple Single System
171 Images which act independently of each other and have
172 hardware based memory protection from the others. Enabling
173 this feature will allow for direct communication between SSIs
174 based on a network adapter and DMA messaging.
175
176 config HP_ILO
177 tristate "Channel interface driver for HP iLO/iLO2 processor"
178 depends on PCI
179 default n
180 help
181 The channel interface driver allows applications to communicate
182 with iLO/iLO2 management processors present on HP ProLiant
183 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
184 which can be used to gather data from the management processor,
185 via read and write system calls.
186
187 To compile this driver as a module, choose M here: the
188 module will be called hpilo.
189
190 config SGI_GRU
191 tristate "SGI GRU driver"
192 depends on X86_UV && SMP
193 default n
194 select MMU_NOTIFIER
195 ---help---
196 The GRU is a hardware resource located in the system chipset. The GRU
197 contains memory that can be mmapped into the user address space. This memory is
198 used to communicate with the GRU to perform functions such as load/store,
199 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
200 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
201 user virtual addresses for operands.
202
203 If you are not running on a SGI UV system, say N.
204
205 config SGI_GRU_DEBUG
206 bool "SGI GRU driver debug"
207 depends on SGI_GRU
208 default n
209 ---help---
210 This option enables addition debugging code for the SGI GRU driver. If
211 you are unsure, say N.
212
213 config DELL_LAPTOP
214 tristate "Dell Laptop Extras (EXPERIMENTAL)"
215 depends on X86
216 depends on DCDBAS
217 depends on EXPERIMENTAL
218 depends on BACKLIGHT_CLASS_DEVICE
219 depends on RFKILL
220 depends on POWER_SUPPLY
221 default n
222 ---help---
223 This driver adds support for rfkill and backlight control to Dell
224 laptops.
225
226 config ISL29003
227 tristate "Intersil ISL29003 ambient light sensor"
228 depends on I2C && SYSFS
229 help
230 If you say yes here you get support for the Intersil ISL29003
231 ambient light sensor.
232
233 This driver can also be built as a module. If so, the module
234 will be called isl29003.
235
236 source "drivers/misc/c2port/Kconfig"
237 source "drivers/misc/eeprom/Kconfig"
238
239 endif # MISC_DEVICES