]>
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 | ||
e58d7468 LW |
13 | config BCM2835_SMI |
14 | tristate "Broadcom 283x Secondary Memory Interface driver" | |
15 | depends on ARCH_BCM2835 | |
16 | default m | |
17 | help | |
18 | Driver for enabling and using Broadcom's Secondary/Slow Memory Interface. | |
19 | Appears as /dev/bcm2835_smi. For ioctl interface see drivers/misc/bcm2835_smi.h | |
20 | ||
4eb174be | 21 | config AD525X_DPOT |
6c536e4c MH |
22 | tristate "Analog Devices Digital Potentiometers" |
23 | depends on (I2C || SPI) && SYSFS | |
4eb174be MH |
24 | help |
25 | If you say yes here, you get support for the Analog Devices | |
6c536e4c MH |
26 | AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255 |
27 | AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203, | |
28 | AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235, | |
29 | AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293, | |
e3ae6847 | 30 | AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242, |
c74cba61 | 31 | AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282, |
a4bd3949 MH |
32 | ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270, |
33 | AD5271, AD5272, AD5274 | |
4eb174be MH |
34 | digital potentiometer chips. |
35 | ||
36 | See Documentation/misc-devices/ad525x_dpot.txt for the | |
37 | userspace interface. | |
38 | ||
39 | This driver can also be built as a module. If so, the module | |
40 | will be called ad525x_dpot. | |
41 | ||
6c536e4c MH |
42 | config AD525X_DPOT_I2C |
43 | tristate "support I2C bus connection" | |
44 | depends on AD525X_DPOT && I2C | |
45 | help | |
46 | Say Y here if you have a digital potentiometers hooked to an I2C bus. | |
47 | ||
48 | To compile this driver as a module, choose M here: the | |
49 | module will be called ad525x_dpot-i2c. | |
50 | ||
51 | config AD525X_DPOT_SPI | |
52 | tristate "support SPI bus connection" | |
53 | depends on AD525X_DPOT && SPI_MASTER | |
54 | help | |
55 | Say Y here if you have a digital potentiometers hooked to an SPI bus. | |
56 | ||
57 | If unsure, say N (but it's safe to say "Y"). | |
58 | ||
59 | To compile this driver as a module, choose M here: the | |
60 | module will be called ad525x_dpot-spi. | |
61 | ||
2a341f5c DB |
62 | config ATMEL_TCLIB |
63 | bool "Atmel AT32/AT91 Timer/Counter Library" | |
64 | depends on (AVR32 || ARCH_AT91) | |
65 | help | |
66 | Select this if you want a library to allocate the Timer/Counter | |
67 | blocks found on many Atmel processors. This facilitates using | |
68 | these blocks by different drivers despite processor differences. | |
69 | ||
4d243f92 DB |
70 | config ATMEL_TCB_CLKSRC |
71 | bool "TC Block Clocksource" | |
592913ec | 72 | depends on ATMEL_TCLIB |
4d243f92 DB |
73 | default y |
74 | help | |
75 | Select this to get a high precision clocksource based on a | |
76 | TC block with a 5+ MHz base clock rate. Two timer channels | |
77 | are combined to make a single 32-bit timer. | |
78 | ||
79 | When GENERIC_CLOCKEVENTS is defined, the third timer channel | |
80 | may be used as a clock event device supporting oneshot mode | |
81 | (delays of up to two seconds) based on the 32 KiHz clock. | |
82 | ||
83 | config ATMEL_TCB_CLKSRC_BLOCK | |
84 | int | |
85 | depends on ATMEL_TCB_CLKSRC | |
9373090d | 86 | prompt "TC Block" if CPU_AT32AP700X |
4d243f92 DB |
87 | default 0 |
88 | range 0 1 | |
89 | help | |
90 | Some chips provide more than one TC block, so you have the | |
91 | choice of which one to use for the clock framework. The other | |
92 | TC can be used for other purposes, such as PWM generation and | |
93 | interval timing. | |
94 | ||
54f69b92 JK |
95 | config DUMMY_IRQ |
96 | tristate "Dummy IRQ handler" | |
97 | default n | |
98 | ---help--- | |
99 | This module accepts a single 'irq' parameter, which it should register for. | |
100 | The sole purpose of this module is to help with debugging of systems on | |
101 | which spurious IRQs would happen on disabled IRQ vector. | |
102 | ||
1da177e4 LT |
103 | config IBM_ASM |
104 | tristate "Device driver for IBM RSA service processor" | |
65929215 | 105 | depends on X86 && PCI && INPUT |
75339d82 | 106 | depends on SERIAL_8250 || SERIAL_8250=n |
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" | |
fc1a5dbe | 203 | depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST) |
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" | |
0f78a11e | 238 | depends on 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 | ||
1f26d1c1 TB |
283 | config QCOM_COINCELL |
284 | tristate "Qualcomm coincell charger support" | |
285 | depends on MFD_SPMI_PMIC || COMPILE_TEST | |
286 | help | |
287 | This driver supports the coincell block found inside of | |
288 | Qualcomm PMICs. The coincell charger provides a means to | |
289 | charge a coincell battery or backup capacitor which is used | |
290 | to maintain PMIC register and RTC state in the absence of | |
291 | external power. | |
292 | ||
3d919e5f JS |
293 | config SGI_GRU |
294 | tristate "SGI GRU driver" | |
1bc4faa5 | 295 | depends on X86_UV && SMP |
3d919e5f JS |
296 | default n |
297 | select MMU_NOTIFIER | |
298 | ---help--- | |
299 | The GRU is a hardware resource located in the system chipset. The GRU | |
300 | contains memory that can be mmapped into the user address space. This memory is | |
301 | used to communicate with the GRU to perform functions such as load/store, | |
302 | scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user | |
303 | instructions using user virtual addresses. GRU instructions (ex., bcopy) use | |
304 | user virtual addresses for operands. | |
305 | ||
306 | If you are not running on a SGI UV system, say N. | |
307 | ||
308 | config SGI_GRU_DEBUG | |
309 | bool "SGI GRU driver debug" | |
310 | depends on SGI_GRU | |
311 | default n | |
312 | ---help--- | |
a82cb8b9 GU |
313 | This option enables additional debugging code for the SGI GRU driver. |
314 | If you are unsure, say N. | |
3d919e5f | 315 | |
22d96aa5 | 316 | config APDS9802ALS |
317 | tristate "Medfield Avago APDS9802 ALS Sensor module" | |
318 | depends on I2C | |
319 | help | |
320 | If you say yes here you get support for the ALS APDS9802 ambient | |
321 | light sensor. | |
322 | ||
323 | This driver can also be built as a module. If so, the module | |
324 | will be called apds9802als. | |
325 | ||
3cdbbeeb DM |
326 | config ISL29003 |
327 | tristate "Intersil ISL29003 ambient light sensor" | |
328 | depends on I2C && SYSFS | |
329 | help | |
330 | If you say yes here you get support for the Intersil ISL29003 | |
331 | ambient light sensor. | |
332 | ||
333 | This driver can also be built as a module. If so, the module | |
334 | will be called isl29003. | |
335 | ||
2e85c4dd KT |
336 | config ISL29020 |
337 | tristate "Intersil ISL29020 ambient light sensor" | |
338 | depends on I2C | |
339 | help | |
340 | If you say yes here you get support for the Intersil ISL29020 | |
341 | ambient light sensor. | |
342 | ||
343 | This driver can also be built as a module. If so, the module | |
344 | will be called isl29020. | |
345 | ||
6a9bcced JD |
346 | config SENSORS_TSL2550 |
347 | tristate "Taos TSL2550 ambient light sensor" | |
348 | depends on I2C && SYSFS | |
349 | help | |
350 | If you say yes here you get support for the Taos TSL2550 | |
351 | ambient light sensor. | |
352 | ||
353 | This driver can also be built as a module. If so, the module | |
354 | will be called tsl2550. | |
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" | |
48e3d668 | 416 | depends on VMWARE_VMCI && 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 | ||
cf4ece53 | 440 | config PCH_PHUB |
584ad00c | 441 | tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB" |
4cd5773a | 442 | select GENERIC_NET_UTILS |
46fd8c34 | 443 | depends on PCI && (X86_32 || MIPS || COMPILE_TEST) |
cf4ece53 MO |
444 | help |
445 | This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of | |
446 | Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded | |
447 | processor. The Topcliff has MAC address and Option ROM data in SROM. | |
448 | This driver can access MAC address and Option ROM data in SROM. | |
449 | ||
584ad00c TM |
450 | This driver also can be used for LAPIS Semiconductor's IOH, |
451 | ML7213/ML7223/ML7831. | |
452 | ML7213 which is for IVI(In-Vehicle Infotainment) use. | |
453 | ML7223 IOH is for MP(Media Phone) use. | |
454 | ML7831 IOH is for general purpose use. | |
455 | ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. | |
456 | ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. | |
c47dda7d | 457 | |
cf4ece53 MO |
458 | To compile this driver as a module, choose M here: the module will |
459 | be called pch_phub. | |
460 | ||
a1bb73d7 DK |
461 | config USB_SWITCH_FSA9480 |
462 | tristate "FSA9480 USB Switch" | |
463 | depends on I2C | |
464 | help | |
465 | The FSA9480 is a USB port accessory detector and switch. | |
466 | The FSA9480 is fully controlled using I2C and enables USB data, | |
467 | stereo and mono audio, video, microphone and UART data to use | |
468 | a common connector port. | |
469 | ||
781551df SR |
470 | config LATTICE_ECP3_CONFIG |
471 | tristate "Lattice ECP3 FPGA bitstream configuration via SPI" | |
472 | depends on SPI && SYSFS | |
473 | select FW_LOADER | |
474 | default n | |
475 | help | |
476 | This option enables support for bitstream configuration (programming | |
477 | or loading) of the Lattice ECP3 FPGA family via SPI. | |
478 | ||
479 | If unsure, say N. | |
480 | ||
4984c6f5 PZ |
481 | config SRAM |
482 | bool "Generic on-chip SRAM driver" | |
483 | depends on HAS_IOMEM | |
484 | select GENERIC_ALLOCATOR | |
485 | help | |
486 | This driver allows you to declare a memory region to be managed by | |
487 | the genalloc API. It is supposed to be used for small on-chip SRAM | |
488 | areas found on many SoCs. | |
489 | ||
974cc7b9 PM |
490 | config VEXPRESS_SYSCFG |
491 | bool "Versatile Express System Configuration driver" | |
492 | depends on VEXPRESS_CONFIG | |
493 | default y | |
494 | help | |
495 | ARM Ltd. Versatile Express uses specialised platform configuration | |
496 | bus. System Configuration interface is one of the possible means | |
497 | of generating transactions on this bus. | |
305b37bd KS |
498 | config PANEL |
499 | tristate "Parallel port LCD/Keypad Panel support" | |
500 | depends on PARPORT | |
501 | ---help--- | |
502 | Say Y here if you have an HD44780 or KS-0074 LCD connected to your | |
503 | parallel port. This driver also features 4 and 6-key keypads. The LCD | |
504 | is accessible through the /dev/lcd char device (10, 156), and the | |
505 | keypad through /dev/keypad (10, 185). Both require misc device to be | |
506 | enabled. This code can either be compiled as a module, or linked into | |
507 | the kernel and started at boot. If you don't understand what all this | |
508 | is about, say N. | |
509 | ||
510 | config PANEL_PARPORT | |
511 | int "Default parallel port number (0=LPT1)" | |
512 | depends on PANEL | |
513 | range 0 255 | |
514 | default "0" | |
515 | ---help--- | |
516 | This is the index of the parallel port the panel is connected to. One | |
517 | driver instance only supports one parallel port, so if your keypad | |
518 | and LCD are connected to two separate ports, you have to start two | |
519 | modules with different arguments. Numbering starts with '0' for LPT1, | |
520 | and so on. | |
521 | ||
522 | config PANEL_PROFILE | |
523 | int "Default panel profile (0-5, 0=custom)" | |
524 | depends on PANEL | |
525 | range 0 5 | |
526 | default "5" | |
527 | ---help--- | |
528 | To ease configuration, the driver supports different configuration | |
529 | profiles for past and recent wirings. These profiles can also be | |
530 | used to define an approximative configuration, completed by a few | |
531 | other options. Here are the profiles : | |
532 | ||
533 | 0 = custom (see further) | |
534 | 1 = 2x16 parallel LCD, old keypad | |
535 | 2 = 2x16 serial LCD (KS-0074), new keypad | |
536 | 3 = 2x16 parallel LCD (Hantronix), no keypad | |
537 | 4 = 2x16 parallel LCD (Nexcom NSA1045) with Nexcom's keypad | |
538 | 5 = 2x40 parallel LCD (old one), with old keypad | |
539 | ||
540 | Custom configurations allow you to define how your display is | |
541 | wired to the parallel port, and how it works. This is only intended | |
542 | for experts. | |
543 | ||
544 | config PANEL_KEYPAD | |
545 | depends on PANEL && PANEL_PROFILE="0" | |
546 | int "Keypad type (0=none, 1=old 6 keys, 2=new 6 keys, 3=Nexcom 4 keys)" | |
547 | range 0 3 | |
548 | default 0 | |
549 | ---help--- | |
550 | This enables and configures a keypad connected to the parallel port. | |
551 | The keys will be read from character device 10,185. Valid values are : | |
552 | ||
553 | 0 : do not enable this driver | |
554 | 1 : old 6 keys keypad | |
555 | 2 : new 6 keys keypad, as used on the server at www.ant-computing.com | |
556 | 3 : Nexcom NSA1045's 4 keys keypad | |
557 | ||
558 | New profiles can be described in the driver source. The driver also | |
559 | supports simultaneous keys pressed when the keypad supports them. | |
560 | ||
561 | config PANEL_LCD | |
562 | depends on PANEL && PANEL_PROFILE="0" | |
563 | int "LCD type (0=none, 1=custom, 2=old //, 3=ks0074, 4=hantronix, 5=Nexcom)" | |
564 | range 0 5 | |
565 | default 0 | |
566 | ---help--- | |
567 | This enables and configures an LCD connected to the parallel port. | |
568 | The driver includes an interpreter for escape codes starting with | |
569 | '\e[L' which are specific to the LCD, and a few ANSI codes. The | |
570 | driver will be registered as character device 10,156, usually | |
571 | under the name '/dev/lcd'. There are a total of 6 supported types : | |
572 | ||
573 | 0 : do not enable the driver | |
574 | 1 : custom configuration and wiring (see further) | |
575 | 2 : 2x16 & 2x40 parallel LCD (old wiring) | |
576 | 3 : 2x16 serial LCD (KS-0074 based) | |
577 | 4 : 2x16 parallel LCD (Hantronix wiring) | |
578 | 5 : 2x16 parallel LCD (Nexcom wiring) | |
579 | ||
580 | When type '1' is specified, other options will appear to configure | |
581 | more precise aspects (wiring, dimensions, protocol, ...). Please note | |
582 | that those values changed from the 2.4 driver for better consistency. | |
583 | ||
584 | config PANEL_LCD_HEIGHT | |
585 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" | |
586 | int "Number of lines on the LCD (1-2)" | |
587 | range 1 2 | |
588 | default 2 | |
589 | ---help--- | |
590 | This is the number of visible character lines on the LCD in custom profile. | |
591 | It can either be 1 or 2. | |
592 | ||
593 | config PANEL_LCD_WIDTH | |
594 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" | |
595 | int "Number of characters per line on the LCD (1-40)" | |
596 | range 1 40 | |
597 | default 40 | |
598 | ---help--- | |
599 | This is the number of characters per line on the LCD in custom profile. | |
600 | Common values are 16,20,24,40. | |
601 | ||
602 | config PANEL_LCD_BWIDTH | |
603 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" | |
604 | int "Internal LCD line width (1-40, 40 by default)" | |
605 | range 1 40 | |
606 | default 40 | |
607 | ---help--- | |
608 | Most LCDs use a standard controller which supports hardware lines of 40 | |
609 | characters, although sometimes only 16, 20 or 24 of them are really wired | |
610 | to the terminal. This results in some non-visible but addressable characters, | |
611 | and is the case for most parallel LCDs. Other LCDs, and some serial ones, | |
612 | however, use the same line width internally as what is visible. The KS0074 | |
613 | for example, uses 16 characters per line for 16 visible characters per line. | |
614 | ||
615 | This option lets you configure the value used by your LCD in 'custom' profile. | |
616 | If you don't know, put '40' here. | |
617 | ||
618 | config PANEL_LCD_HWIDTH | |
619 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" | |
620 | int "Hardware LCD line width (1-64, 64 by default)" | |
621 | range 1 64 | |
622 | default 64 | |
623 | ---help--- | |
624 | Most LCDs use a single address bit to differentiate line 0 and line 1. Since | |
625 | some of them need to be able to address 40 chars with the lower bits, they | |
626 | often use the immediately superior power of 2, which is 64, to address the | |
627 | next line. | |
628 | ||
629 | If you don't know what your LCD uses, in doubt let 16 here for a 2x16, and | |
630 | 64 here for a 2x40. | |
631 | ||
632 | config PANEL_LCD_CHARSET | |
633 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" | |
634 | int "LCD character set (0=normal, 1=KS0074)" | |
635 | range 0 1 | |
636 | default 0 | |
637 | ---help--- | |
638 | Some controllers such as the KS0074 use a somewhat strange character set | |
639 | where many symbols are at unusual places. The driver knows how to map | |
640 | 'standard' ASCII characters to the character sets used by these controllers. | |
641 | Valid values are : | |
642 | ||
643 | 0 : normal (untranslated) character set | |
644 | 1 : KS0074 character set | |
645 | ||
646 | If you don't know, use the normal one (0). | |
647 | ||
648 | config PANEL_LCD_PROTO | |
649 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" | |
650 | int "LCD communication mode (0=parallel 8 bits, 1=serial)" | |
651 | range 0 1 | |
652 | default 0 | |
653 | ---help--- | |
654 | This driver now supports any serial or parallel LCD wired to a parallel | |
655 | port. But before assigning signals, the driver needs to know if it will | |
656 | be driving a serial LCD or a parallel one. Serial LCDs only use 2 wires | |
657 | (SDA/SCL), while parallel ones use 2 or 3 wires for the control signals | |
658 | (E, RS, sometimes RW), and 4 or 8 for the data. Use 0 here for a 8 bits | |
659 | parallel LCD, and 1 for a serial LCD. | |
660 | ||
661 | config PANEL_LCD_PIN_E | |
662 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0" | |
663 | int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) " | |
664 | range -17 17 | |
665 | default 14 | |
666 | ---help--- | |
667 | This describes the number of the parallel port pin to which the LCD 'E' | |
668 | signal has been connected. It can be : | |
669 | ||
670 | 0 : no connection (eg: connected to ground) | |
671 | 1..17 : directly connected to any of these pins on the DB25 plug | |
672 | -1..-17 : connected to the same pin through an inverter (eg: transistor). | |
673 | ||
674 | Default for the 'E' pin in custom profile is '14' (AUTOFEED). | |
675 | ||
676 | config PANEL_LCD_PIN_RS | |
677 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0" | |
678 | int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) " | |
679 | range -17 17 | |
680 | default 17 | |
681 | ---help--- | |
682 | This describes the number of the parallel port pin to which the LCD 'RS' | |
683 | signal has been connected. It can be : | |
684 | ||
685 | 0 : no connection (eg: connected to ground) | |
686 | 1..17 : directly connected to any of these pins on the DB25 plug | |
687 | -1..-17 : connected to the same pin through an inverter (eg: transistor). | |
688 | ||
689 | Default for the 'RS' pin in custom profile is '17' (SELECT IN). | |
690 | ||
691 | config PANEL_LCD_PIN_RW | |
692 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0" | |
693 | int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) " | |
694 | range -17 17 | |
695 | default 16 | |
696 | ---help--- | |
697 | This describes the number of the parallel port pin to which the LCD 'RW' | |
698 | signal has been connected. It can be : | |
699 | ||
700 | 0 : no connection (eg: connected to ground) | |
701 | 1..17 : directly connected to any of these pins on the DB25 plug | |
702 | -1..-17 : connected to the same pin through an inverter (eg: transistor). | |
703 | ||
704 | Default for the 'RW' pin in custom profile is '16' (INIT). | |
705 | ||
706 | config PANEL_LCD_PIN_SCL | |
707 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0" | |
708 | int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) " | |
709 | range -17 17 | |
710 | default 1 | |
711 | ---help--- | |
712 | This describes the number of the parallel port pin to which the serial | |
713 | LCD 'SCL' signal has been connected. It can be : | |
714 | ||
715 | 0 : no connection (eg: connected to ground) | |
716 | 1..17 : directly connected to any of these pins on the DB25 plug | |
717 | -1..-17 : connected to the same pin through an inverter (eg: transistor). | |
718 | ||
719 | Default for the 'SCL' pin in custom profile is '1' (STROBE). | |
720 | ||
721 | config PANEL_LCD_PIN_SDA | |
722 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0" | |
723 | int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) " | |
724 | range -17 17 | |
725 | default 2 | |
726 | ---help--- | |
727 | This describes the number of the parallel port pin to which the serial | |
728 | LCD 'SDA' signal has been connected. It can be : | |
729 | ||
730 | 0 : no connection (eg: connected to ground) | |
731 | 1..17 : directly connected to any of these pins on the DB25 plug | |
732 | -1..-17 : connected to the same pin through an inverter (eg: transistor). | |
733 | ||
734 | Default for the 'SDA' pin in custom profile is '2' (D0). | |
735 | ||
736 | config PANEL_LCD_PIN_BL | |
737 | depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" | |
738 | int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) " | |
739 | range -17 17 | |
740 | default 0 | |
741 | ---help--- | |
742 | This describes the number of the parallel port pin to which the LCD 'BL' signal | |
743 | has been connected. It can be : | |
744 | ||
745 | 0 : no connection (eg: connected to ground) | |
746 | 1..17 : directly connected to any of these pins on the DB25 plug | |
747 | -1..-17 : connected to the same pin through an inverter (eg: transistor). | |
748 | ||
749 | Default for the 'BL' pin in custom profile is '0' (uncontrolled). | |
750 | ||
751 | config PANEL_CHANGE_MESSAGE | |
752 | depends on PANEL | |
753 | bool "Change LCD initialization message ?" | |
754 | default "n" | |
755 | ---help--- | |
756 | This allows you to replace the boot message indicating the kernel version | |
757 | and the driver version with a custom message. This is useful on appliances | |
758 | where a simple 'Starting system' message can be enough to stop a customer | |
759 | from worrying. | |
760 | ||
761 | If you say 'Y' here, you'll be able to choose a message yourself. Otherwise, | |
762 | say 'N' and keep the default message with the version. | |
763 | ||
764 | config PANEL_BOOT_MESSAGE | |
765 | depends on PANEL && PANEL_CHANGE_MESSAGE="y" | |
766 | string "New initialization message" | |
767 | default "" | |
768 | ---help--- | |
769 | This allows you to replace the boot message indicating the kernel version | |
770 | and the driver version with a custom message. This is useful on appliances | |
771 | where a simple 'Starting system' message can be enough to stop a customer | |
772 | from worrying. | |
773 | ||
774 | An empty message will only clear the display at driver init time. Any other | |
775 | printf()-formatted message is valid with newline and escape codes. | |
974cc7b9 | 776 | |
4e17e1db | 777 | source "drivers/misc/c2port/Kconfig" |
5195e509 | 778 | source "drivers/misc/eeprom/Kconfig" |
5f5bac82 | 779 | source "drivers/misc/cb710/Kconfig" |
2bb32e84 | 780 | source "drivers/misc/ti-st/Kconfig" |
ff606677 | 781 | source "drivers/misc/lis3lv02d/Kconfig" |
cff4fa84 | 782 | source "drivers/misc/altera-stapl/Kconfig" |
ffc2825c | 783 | source "drivers/misc/mei/Kconfig" |
20259849 | 784 | source "drivers/misc/vmw_vmci/Kconfig" |
b170d8ce | 785 | source "drivers/misc/mic/Kconfig" |
76f5adbc | 786 | source "drivers/misc/genwqe/Kconfig" |
6e2055a9 | 787 | source "drivers/misc/echo/Kconfig" |
10542ca0 | 788 | source "drivers/misc/cxl/Kconfig" |
7c5763b8 | 789 | endmenu |