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