Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Misc strange devices | |
3 | # | |
4 | ||
7c5763b8 FE |
5 | menu "Misc devices" |
6 | ||
ff606677 JD |
7 | config SENSORS_LIS3LV02D |
8 | tristate | |
9 | depends on INPUT | |
10 | select INPUT_POLLDEV | |
11 | default n | |
12 | ||
4eb174be | 13 | config AD525X_DPOT |
6c536e4c MH |
14 | tristate "Analog Devices Digital Potentiometers" |
15 | depends on (I2C || SPI) && SYSFS | |
4eb174be MH |
16 | help |
17 | If you say yes here, you get support for the Analog Devices | |
6c536e4c MH |
18 | AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255 |
19 | AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203, | |
20 | AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235, | |
21 | AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293, | |
e3ae6847 | 22 | AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242, |
c74cba61 | 23 | AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282, |
a4bd3949 MH |
24 | ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270, |
25 | AD5271, AD5272, AD5274 | |
4eb174be MH |
26 | digital potentiometer chips. |
27 | ||
28 | See Documentation/misc-devices/ad525x_dpot.txt for the | |
29 | userspace interface. | |
30 | ||
31 | This driver can also be built as a module. If so, the module | |
32 | will be called ad525x_dpot. | |
33 | ||
6c536e4c MH |
34 | config AD525X_DPOT_I2C |
35 | tristate "support I2C bus connection" | |
36 | depends on AD525X_DPOT && I2C | |
37 | help | |
38 | Say Y here if you have a digital potentiometers hooked to an I2C bus. | |
39 | ||
40 | To compile this driver as a module, choose M here: the | |
41 | module will be called ad525x_dpot-i2c. | |
42 | ||
43 | config AD525X_DPOT_SPI | |
44 | tristate "support SPI bus connection" | |
45 | depends on AD525X_DPOT && SPI_MASTER | |
46 | help | |
47 | Say Y here if you have a digital potentiometers hooked to an SPI bus. | |
48 | ||
49 | If unsure, say N (but it's safe to say "Y"). | |
50 | ||
51 | To compile this driver as a module, choose M here: the | |
52 | module will be called ad525x_dpot-spi. | |
53 | ||
9a1e8eb1 DB |
54 | config ATMEL_PWM |
55 | tristate "Atmel AT32/AT91 PWM support" | |
2d60cd15 | 56 | depends on HAVE_CLK |
9a1e8eb1 DB |
57 | help |
58 | This option enables device driver support for the PWM channels | |
692105b8 ML |
59 | on certain Atmel processors. Pulse Width Modulation is used for |
60 | purposes including software controlled power-efficient backlights | |
9a1e8eb1 DB |
61 | on LCD displays, motor control, and waveform generation. |
62 | ||
f0f05b1c AM |
63 | config AB8500_PWM |
64 | bool "AB8500 PWM support" | |
b1437580 | 65 | depends on AB8500_CORE && ARCH_U8500 |
f0f05b1c AM |
66 | select HAVE_PWM |
67 | help | |
68 | This driver exports functions to enable/disble/config/free Pulse | |
69 | Width Modulation in the Analog Baseband Chip AB8500. | |
70 | It is used by led and backlight driver to control the intensity. | |
71 | ||
2a341f5c DB |
72 | config ATMEL_TCLIB |
73 | bool "Atmel AT32/AT91 Timer/Counter Library" | |
74 | depends on (AVR32 || ARCH_AT91) | |
75 | help | |
76 | Select this if you want a library to allocate the Timer/Counter | |
77 | blocks found on many Atmel processors. This facilitates using | |
78 | these blocks by different drivers despite processor differences. | |
79 | ||
4d243f92 DB |
80 | config ATMEL_TCB_CLKSRC |
81 | bool "TC Block Clocksource" | |
592913ec | 82 | depends on ATMEL_TCLIB |
4d243f92 DB |
83 | default y |
84 | help | |
85 | Select this to get a high precision clocksource based on a | |
86 | TC block with a 5+ MHz base clock rate. Two timer channels | |
87 | are combined to make a single 32-bit timer. | |
88 | ||
89 | When GENERIC_CLOCKEVENTS is defined, the third timer channel | |
90 | may be used as a clock event device supporting oneshot mode | |
91 | (delays of up to two seconds) based on the 32 KiHz clock. | |
92 | ||
93 | config ATMEL_TCB_CLKSRC_BLOCK | |
94 | int | |
95 | depends on ATMEL_TCB_CLKSRC | |
96 | prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X | |
97 | default 0 | |
98 | range 0 1 | |
99 | help | |
100 | Some chips provide more than one TC block, so you have the | |
101 | choice of which one to use for the clock framework. The other | |
102 | TC can be used for other purposes, such as PWM generation and | |
103 | interval timing. | |
104 | ||
1da177e4 LT |
105 | config IBM_ASM |
106 | tristate "Device driver for IBM RSA service processor" | |
ff294cba | 107 | depends on X86 && PCI && INPUT && EXPERIMENTAL |
1da177e4 LT |
108 | ---help--- |
109 | This option enables device driver support for in-band access to the | |
110 | IBM RSA (Condor) service processor in eServer xSeries systems. | |
111 | The ibmasm device driver allows user space application to access | |
112 | ASM (Advanced Systems Management) functions on the service | |
113 | processor. The driver is meant to be used in conjunction with | |
114 | a user space API. | |
115 | The ibmasm driver also enables the OS to use the UART on the | |
116 | service processor board as a regular serial port. To make use of | |
117 | this feature serial driver support (CONFIG_SERIAL_8250) must be | |
118 | enabled. | |
f9565129 | 119 | |
1da177e4 LT |
120 | WARNING: This software may not be supported or function |
121 | correctly on your IBM server. Please consult the IBM ServerProven | |
631dd1a8 JM |
122 | website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/> |
123 | for information on the specific driver level and support statement | |
1da177e4 LT |
124 | for your IBM server. |
125 | ||
cef2cf07 | 126 | config PHANTOM |
ec905a18 | 127 | tristate "Sensable PHANToM (PCI)" |
cef2cf07 JS |
128 | depends on PCI |
129 | help | |
130 | Say Y here if you want to build a driver for Sensable PHANToM device. | |
131 | ||
ec905a18 JS |
132 | This driver is only for PCI PHANToMs. |
133 | ||
cef2cf07 JS |
134 | If you choose to build module, its name will be phantom. If unsure, |
135 | say N here. | |
136 | ||
0b61d2ac F |
137 | config INTEL_MID_PTI |
138 | tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard" | |
8ea95e08 | 139 | depends on PCI |
0b61d2ac F |
140 | default n |
141 | help | |
142 | The PTI (Parallel Trace Interface) driver directs | |
143 | trace data routed from various parts in the system out | |
144 | through an Intel Penwell PTI port and out of the mobile | |
145 | device for analysis with a debugging tool (Lauterbach or Fido). | |
146 | ||
147 | You should select this driver if the target kernel is meant for | |
148 | an Intel Atom (non-netbook) mobile device containing a MIPI | |
149 | P1149.7 standard implementation. | |
150 | ||
59f14800 BC |
151 | config SGI_IOC4 |
152 | tristate "SGI IOC4 Base IO support" | |
aa6c2e62 | 153 | depends on PCI |
59f14800 BC |
154 | ---help--- |
155 | This option enables basic support for the IOC4 chip on certain | |
156 | SGI IO controller cards (IO9, IO10, and PCI-RT). This option | |
157 | does not enable any specific functions on such a card, but provides | |
158 | necessary infrastructure for other drivers to utilize. | |
159 | ||
160 | If you have an SGI Altix with an IOC4-based card say Y. | |
161 | Otherwise say N. | |
162 | ||
f9565129 AD |
163 | config TIFM_CORE |
164 | tristate "TI Flash Media interface support (EXPERIMENTAL)" | |
9f3bed5f | 165 | depends on EXPERIMENTAL && PCI |
f9565129 AD |
166 | help |
167 | If you want support for Texas Instruments(R) Flash Media adapters | |
168 | you should select this option and then also choose an appropriate | |
169 | host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter | |
170 | support', if you have a TI PCI74xx compatible card reader, for | |
171 | example. | |
172 | You will also have to select some flash card format drivers. MMC/SD | |
173 | cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD | |
174 | Interface support (MMC_TIFM_SD)'. | |
175 | ||
8c36790a | 176 | To compile this driver as a module, choose M here: the module will |
f9565129 | 177 | be called tifm_core. |
1da177e4 | 178 | |
f9565129 AD |
179 | config TIFM_7XX1 |
180 | tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)" | |
181 | depends on PCI && TIFM_CORE && EXPERIMENTAL | |
182 | default TIFM_CORE | |
183 | help | |
184 | This option enables support for Texas Instruments(R) PCI74xx and | |
185 | PCI76xx families of Flash Media adapters, found in many laptops. | |
186 | To make actual use of the device, you will have to select some | |
187 | flash card format drivers, as outlined in the TIFM_CORE Help. | |
188 | ||
8c36790a | 189 | To compile this driver as a module, choose M here: the module will |
f9565129 AD |
190 | be called tifm_7xx1. |
191 | ||
a412ae3f DW |
192 | config ICS932S401 |
193 | tristate "Integrated Circuits ICS932S401" | |
194 | depends on I2C && EXPERIMENTAL | |
195 | help | |
196 | If you say yes here you get support for the Integrated Circuits | |
197 | ICS932S401 clock control chips. | |
198 | ||
199 | This driver can also be built as a module. If so, the module | |
200 | will be called ics932s401. | |
201 | ||
eb1f2930 HCE |
202 | config ATMEL_SSC |
203 | tristate "Device driver for Atmel SSC peripheral" | |
204 | depends on AVR32 || ARCH_AT91 | |
205 | ---help--- | |
692105b8 | 206 | This option enables device driver support for Atmel Synchronized |
eb1f2930 HCE |
207 | Serial Communication peripheral (SSC). |
208 | ||
209 | The SSC peripheral supports a wide variety of serial frame based | |
210 | communications, i.e. I2S, SPI, etc. | |
211 | ||
212 | If unsure, say N. | |
213 | ||
d569d5bb JB |
214 | config ENCLOSURE_SERVICES |
215 | tristate "Enclosure Services" | |
216 | default n | |
217 | help | |
218 | Provides support for intelligent enclosures (bays which | |
219 | contain storage devices). You also need either a host | |
220 | driver (SCSI/ATA) which supports enclosures | |
221 | or a SCSI enclosure device (SES) to use these services. | |
222 | ||
45d9ca49 DN |
223 | config SGI_XP |
224 | tristate "Support communication between SGI SSIs" | |
3b0de7b3 | 225 | depends on NET |
03b48632 | 226 | depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP |
45d9ca49 DN |
227 | select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2 |
228 | select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2 | |
1bc4faa5 | 229 | select SGI_GRU if X86_64 && SMP |
45d9ca49 DN |
230 | ---help--- |
231 | An SGI machine can be divided into multiple Single System | |
232 | Images which act independently of each other and have | |
233 | hardware based memory protection from the others. Enabling | |
234 | this feature will allow for direct communication between SSIs | |
235 | based on a network adapter and DMA messaging. | |
236 | ||
82dca611 AS |
237 | config CS5535_MFGPT |
238 | tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support" | |
703f03c8 | 239 | depends on PCI && X86 && MFD_CS5535 |
82dca611 AS |
240 | default n |
241 | help | |
242 | This driver provides access to MFGPT functionality for other | |
243 | drivers that need timers. MFGPTs are available in the CS5535 and | |
244 | CS5536 companion chips that are found in AMD Geode and several | |
245 | other platforms. They have a better resolution and max interval | |
246 | than the generic PIT, and are suitable for use as high-res timers. | |
247 | You probably don't want to enable this manually; other drivers that | |
248 | make use of it should enable it. | |
249 | ||
250 | config CS5535_MFGPT_DEFAULT_IRQ | |
251 | int | |
2bf212b9 | 252 | depends on CS5535_MFGPT |
82dca611 AS |
253 | default 7 |
254 | help | |
255 | MFGPTs on the CS5535 require an interrupt. The selected IRQ | |
256 | can be overridden as a module option as well as by driver that | |
257 | use the cs5535_mfgpt_ API; however, different architectures might | |
258 | want to use a different IRQ by default. This is here for | |
259 | architectures to set as necessary. | |
260 | ||
9c8f05c2 RD |
261 | config CS5535_CLOCK_EVENT_SRC |
262 | tristate "CS5535/CS5536 high-res timer (MFGPT) events" | |
592913ec | 263 | depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT |
9c8f05c2 RD |
264 | help |
265 | This driver provides a clock event source based on the MFGPT | |
266 | timer(s) in the CS5535 and CS5536 companion chips. | |
267 | MFGPTs have a better resolution and max interval than the | |
268 | generic PIT, and are suitable for use as high-res timers. | |
269 | ||
89bcb05d | 270 | config HP_ILO |
1ce873ab | 271 | tristate "Channel interface driver for the HP iLO processor" |
f38954c9 | 272 | depends on PCI |
89bcb05d DA |
273 | default n |
274 | help | |
275 | The channel interface driver allows applications to communicate | |
1ce873ab | 276 | with iLO management processors present on HP ProLiant servers. |
277 | Upon loading, the driver creates /dev/hpilo/dXccbN files, which | |
278 | can be used to gather data from the management processor, via | |
279 | read and write system calls. | |
89bcb05d DA |
280 | |
281 | To compile this driver as a module, choose M here: the | |
282 | module will be called hpilo. | |
283 | ||
3d919e5f JS |
284 | config SGI_GRU |
285 | tristate "SGI GRU driver" | |
1bc4faa5 | 286 | depends on X86_UV && SMP |
3d919e5f JS |
287 | default n |
288 | select MMU_NOTIFIER | |
289 | ---help--- | |
290 | The GRU is a hardware resource located in the system chipset. The GRU | |
291 | contains memory that can be mmapped into the user address space. This memory is | |
292 | used to communicate with the GRU to perform functions such as load/store, | |
293 | scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user | |
294 | instructions using user virtual addresses. GRU instructions (ex., bcopy) use | |
295 | user virtual addresses for operands. | |
296 | ||
297 | If you are not running on a SGI UV system, say N. | |
298 | ||
299 | config SGI_GRU_DEBUG | |
300 | bool "SGI GRU driver debug" | |
301 | depends on SGI_GRU | |
302 | default n | |
303 | ---help--- | |
304 | This option enables addition debugging code for the SGI GRU driver. If | |
305 | you are unsure, say N. | |
306 | ||
22d96aa5 | 307 | config APDS9802ALS |
308 | tristate "Medfield Avago APDS9802 ALS Sensor module" | |
309 | depends on I2C | |
310 | help | |
311 | If you say yes here you get support for the ALS APDS9802 ambient | |
312 | light sensor. | |
313 | ||
314 | This driver can also be built as a module. If so, the module | |
315 | will be called apds9802als. | |
316 | ||
3cdbbeeb DM |
317 | config ISL29003 |
318 | tristate "Intersil ISL29003 ambient light sensor" | |
319 | depends on I2C && SYSFS | |
320 | help | |
321 | If you say yes here you get support for the Intersil ISL29003 | |
322 | ambient light sensor. | |
323 | ||
324 | This driver can also be built as a module. If so, the module | |
325 | will be called isl29003. | |
326 | ||
2e85c4dd KT |
327 | config ISL29020 |
328 | tristate "Intersil ISL29020 ambient light sensor" | |
329 | depends on I2C | |
330 | help | |
331 | If you say yes here you get support for the Intersil ISL29020 | |
332 | ambient light sensor. | |
333 | ||
334 | This driver can also be built as a module. If so, the module | |
335 | will be called isl29020. | |
336 | ||
6a9bcced JD |
337 | config SENSORS_TSL2550 |
338 | tristate "Taos TSL2550 ambient light sensor" | |
339 | depends on I2C && SYSFS | |
340 | help | |
341 | If you say yes here you get support for the Taos TSL2550 | |
342 | ambient light sensor. | |
343 | ||
344 | This driver can also be built as a module. If so, the module | |
345 | will be called tsl2550. | |
346 | ||
7efe15f2 H |
347 | config SENSORS_BH1780 |
348 | tristate "ROHM BH1780GLI ambient light sensor" | |
349 | depends on I2C && SYSFS | |
350 | help | |
351 | If you say yes here you get support for the ROHM BH1780GLI | |
352 | ambient light sensor. | |
353 | ||
354 | This driver can also be built as a module. If so, the module | |
355 | will be called bh1780gli. | |
356 | ||
190420ab SO |
357 | config SENSORS_BH1770 |
358 | tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" | |
359 | depends on I2C | |
360 | ---help--- | |
361 | Say Y here if you want to build a driver for BH1770GLC (ROHM) or | |
362 | SFH7770 (Osram) combined ambient light and proximity sensor chip. | |
363 | ||
364 | To compile this driver as a module, choose M here: the | |
365 | module will be called bh1770glc. If unsure, say N here. | |
366 | ||
92b1f84d SO |
367 | config SENSORS_APDS990X |
368 | tristate "APDS990X combined als and proximity sensors" | |
369 | depends on I2C | |
370 | default n | |
371 | ---help--- | |
372 | Say Y here if you want to build a driver for Avago APDS990x | |
373 | combined ambient light and proximity sensor chip. | |
374 | ||
375 | To compile this driver as a module, choose M here: the | |
376 | module will be called apds990x. If unsure, say N here. | |
377 | ||
cfa3b24c KT |
378 | config HMC6352 |
379 | tristate "Honeywell HMC6352 compass" | |
380 | depends on I2C | |
381 | help | |
382 | This driver provides support for the Honeywell HMC6352 compass, | |
383 | providing configuration and heading data via sysfs. | |
384 | ||
ef12379f HS |
385 | config EP93XX_PWM |
386 | tristate "EP93xx PWM support" | |
387 | depends on ARCH_EP93XX | |
388 | help | |
389 | This option enables device driver support for the PWM channels | |
390 | on the Cirrus EP93xx processors. The EP9307 chip only has one | |
391 | PWM channel all the others have two, the second channel is an | |
392 | alternate function of the EGPIO14 pin. A sysfs interface is | |
393 | provided to control the PWM channels. | |
394 | ||
395 | To compile this driver as a module, choose M here: the module will | |
396 | be called ep93xx_pwm. | |
397 | ||
dddc66ff WS |
398 | config DS1682 |
399 | tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm" | |
400 | depends on I2C && EXPERIMENTAL | |
401 | help | |
402 | If you say yes here you get support for Dallas Semiconductor | |
403 | DS1682 Total Elapsed Time Recorder. | |
404 | ||
405 | This driver can also be built as a module. If so, the module | |
406 | will be called ds1682. | |
407 | ||
b9500546 PA |
408 | config SPEAR13XX_PCIE_GADGET |
409 | bool "PCIe gadget support for SPEAr13XX platform" | |
410 | depends on ARCH_SPEAR13XX | |
411 | default n | |
412 | help | |
413 | This option enables gadget support for PCIe controller. If | |
414 | board file defines any controller as PCIe endpoint then a sysfs | |
415 | entry will be created for that controller. User can use these | |
416 | sysfs node to configure PCIe EP as per his requirements. | |
417 | ||
4d00928c DM |
418 | config TI_DAC7512 |
419 | tristate "Texas Instruments DAC7512" | |
420 | depends on SPI && SYSFS | |
421 | help | |
422 | If you say yes here you get support for the Texas Instruments | |
423 | DAC7512 16-bit digital-to-analog converter. | |
424 | ||
425 | This driver can also be built as a module. If so, the module | |
149d730f | 426 | will be called ti_dac7512. |
4d00928c | 427 | |
453dc659 DT |
428 | config VMWARE_BALLOON |
429 | tristate "VMware Balloon Driver" | |
430 | depends on X86 | |
431 | help | |
432 | This is VMware physical memory management driver which acts | |
433 | like a "balloon" that can be inflated to reclaim physical pages | |
434 | by reserving them in the guest and invalidating them in the | |
435 | monitor, freeing up the underlying machine pages so they can | |
436 | be allocated to other guests. The balloon can also be deflated | |
437 | to allow the guest to use more physical memory. | |
438 | ||
439 | If unsure, say N. | |
440 | ||
441 | To compile this driver as a module, choose M here: the | |
d544b7a4 | 442 | module will be called vmw_balloon. |
453dc659 | 443 | |
ce896245 LW |
444 | config ARM_CHARLCD |
445 | bool "ARM Ltd. Character LCD Driver" | |
446 | depends on PLAT_VERSATILE | |
447 | help | |
448 | This is a driver for the character LCD found on the ARM Ltd. | |
449 | Versatile and RealView Platform Baseboards. It doesn't do | |
450 | very much more than display the text "ARM Linux" on the first | |
451 | line and the Linux version on the second line, but that's | |
452 | still useful. | |
453 | ||
5bf1d290 CM |
454 | config BMP085 |
455 | tristate "BMP085 digital pressure sensor" | |
456 | depends on I2C && SYSFS | |
457 | help | |
458 | If you say yes here you get support for the Bosch Sensortec | |
d8b187c6 | 459 | BMP085 digital pressure sensor. |
5bf1d290 CM |
460 | |
461 | To compile this driver as a module, choose M here: the | |
462 | module will be called bmp085. | |
463 | ||
cf4ece53 | 464 | config PCH_PHUB |
584ad00c | 465 | tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB" |
cf4ece53 MO |
466 | depends on PCI |
467 | help | |
468 | This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of | |
469 | Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded | |
470 | processor. The Topcliff has MAC address and Option ROM data in SROM. | |
471 | This driver can access MAC address and Option ROM data in SROM. | |
472 | ||
584ad00c TM |
473 | This driver also can be used for LAPIS Semiconductor's IOH, |
474 | ML7213/ML7223/ML7831. | |
475 | ML7213 which is for IVI(In-Vehicle Infotainment) use. | |
476 | ML7223 IOH is for MP(Media Phone) use. | |
477 | ML7831 IOH is for general purpose use. | |
478 | ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. | |
479 | ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. | |
c47dda7d | 480 | |
cf4ece53 MO |
481 | To compile this driver as a module, choose M here: the module will |
482 | be called pch_phub. | |
483 | ||
a1bb73d7 DK |
484 | config USB_SWITCH_FSA9480 |
485 | tristate "FSA9480 USB Switch" | |
486 | depends on I2C | |
487 | help | |
488 | The FSA9480 is a USB port accessory detector and switch. | |
489 | The FSA9480 is fully controlled using I2C and enables USB data, | |
490 | stereo and mono audio, video, microphone and UART data to use | |
491 | a common connector port. | |
492 | ||
99f09beb DK |
493 | config MAX8997_MUIC |
494 | tristate "MAX8997 MUIC Support" | |
495 | depends on MFD_MAX8997 | |
496 | help | |
497 | If you say yes here you get support for the MUIC device of | |
498 | Maxim MAX8997 PMIC. | |
499 | The MAX8997 MUIC is a USB port accessory detector and switch. | |
500 | ||
4e17e1db | 501 | source "drivers/misc/c2port/Kconfig" |
5195e509 | 502 | source "drivers/misc/eeprom/Kconfig" |
5f5bac82 | 503 | source "drivers/misc/cb710/Kconfig" |
ab69a5ae | 504 | source "drivers/misc/iwmc3200top/Kconfig" |
2bb32e84 | 505 | source "drivers/misc/ti-st/Kconfig" |
ff606677 | 506 | source "drivers/misc/lis3lv02d/Kconfig" |
c186f0e1 | 507 | source "drivers/misc/carma/Kconfig" |
cff4fa84 | 508 | source "drivers/misc/altera-stapl/Kconfig" |
7c5763b8 | 509 | endmenu |