Loading...
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Misc strange devices
4#
5
6menu "Misc devices"
7
8config SENSORS_LIS3LV02D
9 tristate
10 depends on INPUT
11
12config AD525X_DPOT
13 tristate "Analog Devices Digital Potentiometers"
14 depends on (I2C || SPI) && SYSFS
15 help
16 If you say yes here, you get support for the Analog Devices
17 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
18 AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
19 AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
20 AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
21 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
22 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
23 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
24 AD5271, AD5272, AD5274
25 digital potentiometer chips.
26
27 See Documentation/misc-devices/ad525x_dpot.rst for the
28 userspace interface.
29
30 This driver can also be built as a module. If so, the module
31 will be called ad525x_dpot.
32
33config AD525X_DPOT_I2C
34 tristate "support I2C bus connection"
35 depends on AD525X_DPOT && I2C
36 help
37 Say Y here if you have a digital potentiometers hooked to an I2C bus.
38
39 To compile this driver as a module, choose M here: the
40 module will be called ad525x_dpot-i2c.
41
42config AD525X_DPOT_SPI
43 tristate "support SPI bus connection"
44 depends on AD525X_DPOT && SPI_MASTER
45 help
46 Say Y here if you have a digital potentiometers hooked to an SPI bus.
47
48 If unsure, say N (but it's safe to say "Y").
49
50 To compile this driver as a module, choose M here: the
51 module will be called ad525x_dpot-spi.
52
53config DUMMY_IRQ
54 tristate "Dummy IRQ handler"
55 help
56 This module accepts a single 'irq' parameter, which it should register for.
57 The sole purpose of this module is to help with debugging of systems on
58 which spurious IRQs would happen on disabled IRQ vector.
59
60config IBM_ASM
61 tristate "Device driver for IBM RSA service processor"
62 depends on X86 && PCI && INPUT
63 depends on SERIAL_8250 || SERIAL_8250=n
64 help
65 This option enables device driver support for in-band access to the
66 IBM RSA (Condor) service processor in eServer xSeries systems.
67 The ibmasm device driver allows user space application to access
68 ASM (Advanced Systems Management) functions on the service
69 processor. The driver is meant to be used in conjunction with
70 a user space API.
71 The ibmasm driver also enables the OS to use the UART on the
72 service processor board as a regular serial port. To make use of
73 this feature serial driver support (CONFIG_SERIAL_8250) must be
74 enabled.
75
76 WARNING: This software may not be supported or function
77 correctly on your IBM server. Please consult the IBM ServerProven
78 website <https://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
79 for information on the specific driver level and support statement
80 for your IBM server.
81
82config IBMVMC
83 tristate "IBM Virtual Management Channel support"
84 depends on PPC_PSERIES
85 help
86 This is the IBM POWER Virtual Management Channel
87
88 This driver is to be used for the POWER Virtual
89 Management Channel virtual adapter on the PowerVM
90 platform. It provides both request/response and
91 async message support through the /dev/ibmvmc node.
92
93 To compile this driver as a module, choose M here: the
94 module will be called ibmvmc.
95
96config PHANTOM
97 tristate "Sensable PHANToM (PCI)"
98 depends on PCI
99 help
100 Say Y here if you want to build a driver for Sensable PHANToM device.
101
102 This driver is only for PCI PHANToMs.
103
104 If you choose to build module, its name will be phantom. If unsure,
105 say N here.
106
107config RPMB
108 tristate "RPMB partition interface"
109 depends on MMC
110 help
111 Unified RPMB unit interface for RPMB capable devices such as eMMC and
112 UFS. Provides interface for in-kernel security controllers to access
113 RPMB unit.
114
115 If unsure, select N.
116
117config TIFM_CORE
118 tristate "TI Flash Media interface support"
119 depends on PCI
120 help
121 If you want support for Texas Instruments(R) Flash Media adapters
122 you should select this option and then also choose an appropriate
123 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
124 support', if you have a TI PCI74xx compatible card reader, for
125 example.
126 You will also have to select some flash card format drivers. MMC/SD
127 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
128 Interface support (MMC_TIFM_SD)'.
129
130 To compile this driver as a module, choose M here: the module will
131 be called tifm_core.
132
133config TIFM_7XX1
134 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
135 depends on PCI && TIFM_CORE
136 default TIFM_CORE
137 help
138 This option enables support for Texas Instruments(R) PCI74xx and
139 PCI76xx families of Flash Media adapters, found in many laptops.
140 To make actual use of the device, you will have to select some
141 flash card format drivers, as outlined in the TIFM_CORE Help.
142
143 To compile this driver as a module, choose M here: the module will
144 be called tifm_7xx1.
145
146config ICS932S401
147 tristate "Integrated Circuits ICS932S401"
148 depends on I2C
149 help
150 If you say yes here you get support for the Integrated Circuits
151 ICS932S401 clock control chips.
152
153 This driver can also be built as a module. If so, the module
154 will be called ics932s401.
155
156config ATMEL_SSC
157 tristate "Device driver for Atmel SSC peripheral"
158 depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
159 help
160 This option enables device driver support for Atmel Synchronized
161 Serial Communication peripheral (SSC).
162
163 The SSC peripheral supports a wide variety of serial frame based
164 communications, i.e. I2S, SPI, etc.
165
166 If unsure, say N.
167
168config ENCLOSURE_SERVICES
169 tristate "Enclosure Services"
170 help
171 Provides support for intelligent enclosures (bays which
172 contain storage devices). You also need either a host
173 driver (SCSI/ATA) which supports enclosures
174 or a SCSI enclosure device (SES) to use these services.
175
176config SGI_XP
177 tristate "Support communication between SGI SSIs"
178 depends on NET
179 depends on X86_UV && SMP
180 depends on X86_64 || BROKEN
181 select SGI_GRU if X86_64 && SMP
182 help
183 An SGI machine can be divided into multiple Single System
184 Images which act independently of each other and have
185 hardware based memory protection from the others. Enabling
186 this feature will allow for direct communication between SSIs
187 based on a network adapter and DMA messaging.
188
189config SMPRO_ERRMON
190 tristate "Ampere Computing SMPro error monitor driver"
191 depends on MFD_SMPRO || COMPILE_TEST
192 help
193 Say Y here to get support for the SMpro error monitor function
194 provided by Ampere Computing's Altra and Altra Max SoCs. Upon
195 loading, the driver creates sysfs files which can be use to gather
196 multiple HW error data reported via read and write system calls.
197
198 To compile this driver as a module, say M here. The driver will be
199 called smpro-errmon.
200
201config SMPRO_MISC
202 tristate "Ampere Computing SMPro miscellaneous driver"
203 depends on MFD_SMPRO || COMPILE_TEST
204 help
205 Say Y here to get support for the SMpro error miscellalenous function
206 provided by Ampere Computing's Altra and Altra Max SoCs.
207
208 To compile this driver as a module, say M here. The driver will be
209 called smpro-misc.
210
211config CS5535_MFGPT
212 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
213 depends on MFD_CS5535
214 help
215 This driver provides access to MFGPT functionality for other
216 drivers that need timers. MFGPTs are available in the CS5535 and
217 CS5536 companion chips that are found in AMD Geode and several
218 other platforms. They have a better resolution and max interval
219 than the generic PIT, and are suitable for use as high-res timers.
220 You probably don't want to enable this manually; other drivers that
221 make use of it should enable it.
222
223config CS5535_MFGPT_DEFAULT_IRQ
224 int
225 depends on CS5535_MFGPT
226 default 7
227 help
228 MFGPTs on the CS5535 require an interrupt. The selected IRQ
229 can be overridden as a module option as well as by driver that
230 use the cs5535_mfgpt_ API; however, different architectures might
231 want to use a different IRQ by default. This is here for
232 architectures to set as necessary.
233
234config CS5535_CLOCK_EVENT_SRC
235 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
236 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
237 help
238 This driver provides a clock event source based on the MFGPT
239 timer(s) in the CS5535 and CS5536 companion chips.
240 MFGPTs have a better resolution and max interval than the
241 generic PIT, and are suitable for use as high-res timers.
242
243config GEHC_ACHC
244 tristate "GEHC ACHC support"
245 depends on SPI && SYSFS
246 depends on SOC_IMX53 || COMPILE_TEST
247 select FW_LOADER
248 help
249 Support for GE ACHC microcontroller, that is part of the GE
250 PPD device.
251
252 To compile this driver as a module, choose M here: the
253 module will be called gehc-achc.
254
255config HI6421V600_IRQ
256 tristate "HiSilicon Hi6421v600 IRQ and powerkey"
257 depends on OF
258 depends on SPMI
259 depends on HAS_IOMEM
260 select MFD_CORE
261 select REGMAP_SPMI
262 help
263 This driver provides IRQ handling for Hi6421v600, used on
264 some Kirin chipsets, like the one at Hikey 970.
265
266config HP_ILO
267 tristate "Channel interface driver for the HP iLO processor"
268 depends on PCI
269 help
270 The channel interface driver allows applications to communicate
271 with iLO management processors present on HP ProLiant servers.
272 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
273 can be used to gather data from the management processor, via
274 read and write system calls.
275
276 To compile this driver as a module, choose M here: the
277 module will be called hpilo.
278
279config QCOM_COINCELL
280 tristate "Qualcomm coincell charger support"
281 depends on MFD_SPMI_PMIC || COMPILE_TEST
282 help
283 This driver supports the coincell block found inside of
284 Qualcomm PMICs. The coincell charger provides a means to
285 charge a coincell battery or backup capacitor which is used
286 to maintain PMIC register and RTC state in the absence of
287 external power.
288
289config QCOM_FASTRPC
290 tristate "Qualcomm FastRPC"
291 depends on ARCH_QCOM || COMPILE_TEST
292 depends on RPMSG
293 select DMA_SHARED_BUFFER
294 select QCOM_SCM
295 help
296 Provides a communication mechanism that allows for clients to
297 make remote method invocations across processor boundary to
298 applications DSP processor. Say M if you want to enable this
299 module.
300
301config SGI_GRU
302 tristate "SGI GRU driver"
303 depends on X86_UV && SMP
304 select MMU_NOTIFIER
305 help
306 The GRU is a hardware resource located in the system chipset. The GRU
307 contains memory that can be mmapped into the user address space.
308 This memory is used to communicate with the GRU to perform functions
309 such as load/store, scatter/gather, bcopy, AMOs, etc. The GRU is
310 directly accessed by user instructions using user virtual addresses.
311 GRU instructions (ex., bcopy) use user virtual addresses for operands.
312
313 If you are not running on a SGI UV system, say N.
314
315config SGI_GRU_DEBUG
316 bool "SGI GRU driver debug"
317 depends on SGI_GRU
318 help
319 This option enables additional debugging code for the SGI GRU driver.
320 If you are unsure, say N.
321
322config APDS9802ALS
323 tristate "Medfield Avago APDS9802 ALS Sensor module"
324 depends on I2C
325 help
326 If you say yes here you get support for the ALS APDS9802 ambient
327 light sensor.
328
329 This driver can also be built as a module. If so, the module
330 will be called apds9802als.
331
332config ISL29003
333 tristate "Intersil ISL29003 ambient light sensor"
334 depends on I2C && SYSFS
335 help
336 If you say yes here you get support for the Intersil ISL29003
337 ambient light sensor.
338
339 This driver can also be built as a module. If so, the module
340 will be called isl29003.
341
342config ISL29020
343 tristate "Intersil ISL29020 ambient light sensor"
344 depends on I2C
345 help
346 If you say yes here you get support for the Intersil ISL29020
347 ambient light sensor.
348
349 This driver can also be built as a module. If so, the module
350 will be called isl29020.
351
352config SENSORS_TSL2550
353 tristate "Taos TSL2550 ambient light sensor"
354 depends on I2C && SYSFS
355 help
356 If you say yes here you get support for the Taos TSL2550
357 ambient light sensor.
358
359 This driver can also be built as a module. If so, the module
360 will be called tsl2550.
361
362config SENSORS_BH1770
363 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
364 depends on I2C
365 help
366 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
367 SFH7770 (Osram) combined ambient light and proximity sensor chip.
368
369 To compile this driver as a module, choose M here: the
370 module will be called bh1770glc. If unsure, say N here.
371
372config SENSORS_APDS990X
373 tristate "APDS990X combined als and proximity sensors"
374 depends on I2C
375 help
376 Say Y here if you want to build a driver for Avago APDS990x
377 combined ambient light and proximity sensor chip.
378
379 To compile this driver as a module, choose M here: the
380 module will be called apds990x. If unsure, say N here.
381
382config HMC6352
383 tristate "Honeywell HMC6352 compass"
384 depends on I2C
385 help
386 This driver provides support for the Honeywell HMC6352 compass,
387 providing configuration and heading data via sysfs.
388
389config DS1682
390 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
391 depends on I2C
392 help
393 If you say yes here you get support for Dallas Semiconductor
394 DS1682 Total Elapsed Time Recorder.
395
396 This driver can also be built as a module. If so, the module
397 will be called ds1682.
398
399config VMWARE_BALLOON
400 tristate "VMware Balloon Driver"
401 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
402 select MEMORY_BALLOON
403 help
404 This is VMware physical memory management driver which acts
405 like a "balloon" that can be inflated to reclaim physical pages
406 by reserving them in the guest and invalidating them in the
407 monitor, freeing up the underlying machine pages so they can
408 be allocated to other guests. The balloon can also be deflated
409 to allow the guest to use more physical memory.
410
411 If unsure, say N.
412
413 To compile this driver as a module, choose M here: the
414 module will be called vmw_balloon.
415
416config PCH_PHUB
417 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
418 select GENERIC_NET_UTILS
419 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
420 help
421 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
422 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
423 processor. The Topcliff has MAC address and Option ROM data in SROM.
424 This driver can access MAC address and Option ROM data in SROM.
425
426 This driver also can be used for LAPIS Semiconductor's IOH,
427 ML7213/ML7223/ML7831.
428 ML7213 which is for IVI(In-Vehicle Infotainment) use.
429 ML7223 IOH is for MP(Media Phone) use.
430 ML7831 IOH is for general purpose use.
431 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
432 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
433
434 To compile this driver as a module, choose M here: the module will
435 be called pch_phub.
436
437config LATTICE_ECP3_CONFIG
438 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
439 depends on SPI && SYSFS
440 select FW_LOADER
441 help
442 This option enables support for bitstream configuration (programming
443 or loading) of the Lattice ECP3 FPGA family via SPI.
444
445 If unsure, say N.
446
447config SRAM
448 bool "Generic on-chip SRAM driver"
449 depends on HAS_IOMEM
450 select GENERIC_ALLOCATOR
451 select SRAM_EXEC if ARM
452 help
453 This driver allows you to declare a memory region to be managed by
454 the genalloc API. It is supposed to be used for small on-chip SRAM
455 areas found on many SoCs.
456
457config SRAM_EXEC
458 bool
459
460config DW_XDATA_PCIE
461 depends on PCI
462 tristate "Synopsys DesignWare xData PCIe driver"
463 help
464 This driver allows controlling Synopsys DesignWare PCIe traffic
465 generator IP also known as xData, present in Synopsys DesignWare
466 PCIe Endpoint prototype.
467
468 If unsure, say N.
469
470config PCI_ENDPOINT_TEST
471 depends on PCI
472 select CRC32
473 tristate "PCI Endpoint Test driver"
474 help
475 Enable this configuration option to enable the host side test driver
476 for PCI Endpoint.
477
478config XILINX_SDFEC
479 tristate "Xilinx SDFEC 16"
480 depends on HAS_IOMEM
481 help
482 This option enables support for the Xilinx SDFEC (Soft Decision
483 Forward Error Correction) driver. This enables a char driver
484 for the SDFEC.
485
486 You may select this driver if your design instantiates the
487 SDFEC(16nm) hardened block. To compile this as a module choose M.
488
489 If unsure, say N.
490
491config MISC_RTSX
492 tristate
493 default MISC_RTSX_PCI || MISC_RTSX_USB
494
495config HISI_HIKEY_USB
496 tristate "USB GPIO Hub on HiSilicon Hikey 960/970 Platform"
497 depends on (OF && GPIOLIB) || COMPILE_TEST
498 depends on USB_ROLE_SWITCH
499 help
500 If you say yes here this adds support for the on-board USB GPIO hub
501 found on HiKey 960/970 boards, which is necessary to support
502 switching between the dual-role USB-C port and the USB-A host ports
503 using only one USB controller.
504
505config OPEN_DICE
506 tristate "Open Profile for DICE driver"
507 depends on OF_RESERVED_MEM
508 depends on HAS_IOMEM
509 help
510 This driver exposes a DICE reserved memory region to userspace via
511 a character device. The memory region contains Compound Device
512 Identifiers (CDIs) generated by firmware as an output of DICE
513 measured boot flow. Userspace can use CDIs for remote attestation
514 and sealing.
515
516 If unsure, say N.
517
518config NTSYNC
519 tristate "NT synchronization primitive emulation"
520 depends on BROKEN
521 help
522 This module provides kernel support for emulation of Windows NT
523 synchronization primitives. It is not a hardware driver.
524
525 To compile this driver as a module, choose M here: the
526 module will be called ntsync.
527
528 If unsure, say N.
529
530config VCPU_STALL_DETECTOR
531 tristate "Guest vCPU stall detector"
532 depends on OF && HAS_IOMEM
533 help
534 When this driver is bound inside a KVM guest, it will
535 periodically "pet" an MMIO stall detector device from each vCPU
536 and allow the host to detect vCPU stalls.
537
538 To compile this driver as a module, choose M here: the module
539 will be called vcpu_stall_detector.
540
541 If you do not intend to run this kernel as a guest, say N.
542
543config TMR_MANAGER
544 tristate "Select TMR Manager"
545 depends on MICROBLAZE && MB_MANAGER
546 help
547 This option enables the driver developed for TMR Manager.
548 The Triple Modular Redundancy(TMR) manager provides support for
549 fault detection.
550
551 Say N here unless you know what you are doing.
552
553config TMR_INJECT
554 tristate "Select TMR Inject"
555 depends on TMR_MANAGER && FAULT_INJECTION_DEBUG_FS
556 help
557 This option enables the driver developed for TMR Inject.
558 The Triple Modular Redundancy(TMR) Inject provides
559 fault injection.
560
561 Say N here unless you know what you are doing.
562
563config TPS6594_ESM
564 tristate "TI TPS6594 Error Signal Monitor support"
565 depends on MFD_TPS6594
566 default MFD_TPS6594
567 help
568 Support ESM (Error Signal Monitor) on TPS6594 PMIC devices.
569 ESM is used typically to reboot the board in error condition.
570
571 This driver can also be built as a module. If so, the module
572 will be called tps6594-esm.
573
574config TPS6594_PFSM
575 tristate "TI TPS6594 Pre-configurable Finite State Machine support"
576 depends on MFD_TPS6594
577 default MFD_TPS6594
578 help
579 Support PFSM (Pre-configurable Finite State Machine) on TPS6594 PMIC devices.
580 These devices integrate a finite state machine engine, which manages the state
581 of the device during operating state transition.
582
583 This driver can also be built as a module. If so, the module
584 will be called tps6594-pfsm.
585
586config NSM
587 tristate "Nitro (Enclaves) Security Module support"
588 depends on VIRTIO
589 select HW_RANDOM
590 help
591 This driver provides support for the Nitro Security Module
592 in AWS EC2 Nitro based Enclaves. The driver exposes a /dev/nsm
593 device user space can use to communicate with the hypervisor.
594
595 To compile this driver as a module, choose M here.
596 The module will be called nsm.
597
598config MARVELL_CN10K_DPI
599 tristate "Octeon CN10K DPI driver"
600 depends on PCI && PCI_IOV
601 depends on ARCH_THUNDER || (COMPILE_TEST && 64BIT)
602 help
603 Enables Octeon CN10K DMA packet interface (DPI) driver which
604 intializes DPI hardware's physical function (PF) device's
605 global configuration and its virtual function (VFs) resource
606 configuration to enable DMA transfers. DPI PF device does not
607 have any data movement functionality, it only serves VF's
608 resource configuration requests.
609
610 To compile this driver as a module, choose M here: the module
611 will be called mrvl_cn10k_dpi.
612
613config MCHP_LAN966X_PCI
614 tristate "Microchip LAN966x PCIe Support"
615 depends on PCI
616 select OF
617 select OF_OVERLAY
618 select IRQ_DOMAIN
619 help
620 This enables the support for the LAN966x PCIe device.
621
622 This is used to drive the LAN966x PCIe device from the host system
623 to which it is connected. The driver uses a device tree overlay to
624 load other drivers to support for LAN966x internal components.
625
626 Even if this driver does not depend on those other drivers, in order
627 to have a fully functional board, the following drivers are needed:
628 - fixed-clock (COMMON_CLK)
629 - lan966x-oic (LAN966X_OIC)
630 - lan966x-cpu-syscon (MFD_SYSCON)
631 - lan966x-switch-reset (RESET_MCHP_SPARX5)
632 - lan966x-pinctrl (PINCTRL_OCELOT)
633 - lan966x-serdes (PHY_LAN966X_SERDES)
634 - lan966x-miim (MDIO_MSCC_MIIM)
635 - lan966x-switch (LAN966X_SWITCH)
636
637source "drivers/misc/c2port/Kconfig"
638source "drivers/misc/eeprom/Kconfig"
639source "drivers/misc/cb710/Kconfig"
640source "drivers/misc/lis3lv02d/Kconfig"
641source "drivers/misc/altera-stapl/Kconfig"
642source "drivers/misc/mei/Kconfig"
643source "drivers/misc/vmw_vmci/Kconfig"
644source "drivers/misc/genwqe/Kconfig"
645source "drivers/misc/echo/Kconfig"
646source "drivers/misc/cxl/Kconfig"
647source "drivers/misc/ocxl/Kconfig"
648source "drivers/misc/bcm-vk/Kconfig"
649source "drivers/misc/cardreader/Kconfig"
650source "drivers/misc/uacce/Kconfig"
651source "drivers/misc/pvpanic/Kconfig"
652source "drivers/misc/mchp_pci1xxxx/Kconfig"
653source "drivers/misc/keba/Kconfig"
654endmenu
1#
2# Misc strange devices
3#
4
5menu "Misc devices"
6
7config SENSORS_LIS3LV02D
8 tristate
9 depends on INPUT
10 select INPUT_POLLDEV
11 default n
12
13config AD525X_DPOT
14 tristate "Analog Devices Digital Potentiometers"
15 depends on (I2C || SPI) && SYSFS
16 help
17 If you say yes here, you get support for the Analog Devices
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,
22 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
23 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
24 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
25 AD5271, AD5272, AD5274
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
34config 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
43config 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
54config ATMEL_TCLIB
55 bool "Atmel AT32/AT91 Timer/Counter Library"
56 depends on (AVR32 || ARCH_AT91)
57 help
58 Select this if you want a library to allocate the Timer/Counter
59 blocks found on many Atmel processors. This facilitates using
60 these blocks by different drivers despite processor differences.
61
62config ATMEL_TCB_CLKSRC
63 bool "TC Block Clocksource"
64 depends on ATMEL_TCLIB
65 default y
66 help
67 Select this to get a high precision clocksource based on a
68 TC block with a 5+ MHz base clock rate. Two timer channels
69 are combined to make a single 32-bit timer.
70
71 When GENERIC_CLOCKEVENTS is defined, the third timer channel
72 may be used as a clock event device supporting oneshot mode
73 (delays of up to two seconds) based on the 32 KiHz clock.
74
75config ATMEL_TCB_CLKSRC_BLOCK
76 int
77 depends on ATMEL_TCB_CLKSRC
78 prompt "TC Block" if CPU_AT32AP700X
79 default 0
80 range 0 1
81 help
82 Some chips provide more than one TC block, so you have the
83 choice of which one to use for the clock framework. The other
84 TC can be used for other purposes, such as PWM generation and
85 interval timing.
86
87config DUMMY_IRQ
88 tristate "Dummy IRQ handler"
89 default n
90 ---help---
91 This module accepts a single 'irq' parameter, which it should register for.
92 The sole purpose of this module is to help with debugging of systems on
93 which spurious IRQs would happen on disabled IRQ vector.
94
95config IBM_ASM
96 tristate "Device driver for IBM RSA service processor"
97 depends on X86 && PCI && INPUT
98 depends on SERIAL_8250 || SERIAL_8250=n
99 ---help---
100 This option enables device driver support for in-band access to the
101 IBM RSA (Condor) service processor in eServer xSeries systems.
102 The ibmasm device driver allows user space application to access
103 ASM (Advanced Systems Management) functions on the service
104 processor. The driver is meant to be used in conjunction with
105 a user space API.
106 The ibmasm driver also enables the OS to use the UART on the
107 service processor board as a regular serial port. To make use of
108 this feature serial driver support (CONFIG_SERIAL_8250) must be
109 enabled.
110
111 WARNING: This software may not be supported or function
112 correctly on your IBM server. Please consult the IBM ServerProven
113 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
114 for information on the specific driver level and support statement
115 for your IBM server.
116
117config PHANTOM
118 tristate "Sensable PHANToM (PCI)"
119 depends on PCI
120 help
121 Say Y here if you want to build a driver for Sensable PHANToM device.
122
123 This driver is only for PCI PHANToMs.
124
125 If you choose to build module, its name will be phantom. If unsure,
126 say N here.
127
128config INTEL_MID_PTI
129 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
130 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
131 default n
132 help
133 The PTI (Parallel Trace Interface) driver directs
134 trace data routed from various parts in the system out
135 through an Intel Penwell PTI port and out of the mobile
136 device for analysis with a debugging tool (Lauterbach or Fido).
137
138 You should select this driver if the target kernel is meant for
139 an Intel Atom (non-netbook) mobile device containing a MIPI
140 P1149.7 standard implementation.
141
142config SGI_IOC4
143 tristate "SGI IOC4 Base IO support"
144 depends on PCI
145 ---help---
146 This option enables basic support for the IOC4 chip on certain
147 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
148 does not enable any specific functions on such a card, but provides
149 necessary infrastructure for other drivers to utilize.
150
151 If you have an SGI Altix with an IOC4-based card say Y.
152 Otherwise say N.
153
154config TIFM_CORE
155 tristate "TI Flash Media interface support"
156 depends on PCI
157 help
158 If you want support for Texas Instruments(R) Flash Media adapters
159 you should select this option and then also choose an appropriate
160 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
161 support', if you have a TI PCI74xx compatible card reader, for
162 example.
163 You will also have to select some flash card format drivers. MMC/SD
164 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
165 Interface support (MMC_TIFM_SD)'.
166
167 To compile this driver as a module, choose M here: the module will
168 be called tifm_core.
169
170config TIFM_7XX1
171 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
172 depends on PCI && TIFM_CORE
173 default TIFM_CORE
174 help
175 This option enables support for Texas Instruments(R) PCI74xx and
176 PCI76xx families of Flash Media adapters, found in many laptops.
177 To make actual use of the device, you will have to select some
178 flash card format drivers, as outlined in the TIFM_CORE Help.
179
180 To compile this driver as a module, choose M here: the module will
181 be called tifm_7xx1.
182
183config ICS932S401
184 tristate "Integrated Circuits ICS932S401"
185 depends on I2C
186 help
187 If you say yes here you get support for the Integrated Circuits
188 ICS932S401 clock control chips.
189
190 This driver can also be built as a module. If so, the module
191 will be called ics932s401.
192
193config ATMEL_SSC
194 tristate "Device driver for Atmel SSC peripheral"
195 depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
196 ---help---
197 This option enables device driver support for Atmel Synchronized
198 Serial Communication peripheral (SSC).
199
200 The SSC peripheral supports a wide variety of serial frame based
201 communications, i.e. I2S, SPI, etc.
202
203 If unsure, say N.
204
205config ENCLOSURE_SERVICES
206 tristate "Enclosure Services"
207 default n
208 help
209 Provides support for intelligent enclosures (bays which
210 contain storage devices). You also need either a host
211 driver (SCSI/ATA) which supports enclosures
212 or a SCSI enclosure device (SES) to use these services.
213
214config SGI_XP
215 tristate "Support communication between SGI SSIs"
216 depends on NET
217 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
218 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
219 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
220 select SGI_GRU if X86_64 && SMP
221 ---help---
222 An SGI machine can be divided into multiple Single System
223 Images which act independently of each other and have
224 hardware based memory protection from the others. Enabling
225 this feature will allow for direct communication between SSIs
226 based on a network adapter and DMA messaging.
227
228config CS5535_MFGPT
229 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
230 depends on MFD_CS5535
231 default n
232 help
233 This driver provides access to MFGPT functionality for other
234 drivers that need timers. MFGPTs are available in the CS5535 and
235 CS5536 companion chips that are found in AMD Geode and several
236 other platforms. They have a better resolution and max interval
237 than the generic PIT, and are suitable for use as high-res timers.
238 You probably don't want to enable this manually; other drivers that
239 make use of it should enable it.
240
241config CS5535_MFGPT_DEFAULT_IRQ
242 int
243 depends on CS5535_MFGPT
244 default 7
245 help
246 MFGPTs on the CS5535 require an interrupt. The selected IRQ
247 can be overridden as a module option as well as by driver that
248 use the cs5535_mfgpt_ API; however, different architectures might
249 want to use a different IRQ by default. This is here for
250 architectures to set as necessary.
251
252config CS5535_CLOCK_EVENT_SRC
253 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
254 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
255 help
256 This driver provides a clock event source based on the MFGPT
257 timer(s) in the CS5535 and CS5536 companion chips.
258 MFGPTs have a better resolution and max interval than the
259 generic PIT, and are suitable for use as high-res timers.
260
261config HP_ILO
262 tristate "Channel interface driver for the HP iLO processor"
263 depends on PCI
264 default n
265 help
266 The channel interface driver allows applications to communicate
267 with iLO management processors present on HP ProLiant servers.
268 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
269 can be used to gather data from the management processor, via
270 read and write system calls.
271
272 To compile this driver as a module, choose M here: the
273 module will be called hpilo.
274
275config QCOM_COINCELL
276 tristate "Qualcomm coincell charger support"
277 depends on MFD_SPMI_PMIC || COMPILE_TEST
278 help
279 This driver supports the coincell block found inside of
280 Qualcomm PMICs. The coincell charger provides a means to
281 charge a coincell battery or backup capacitor which is used
282 to maintain PMIC register and RTC state in the absence of
283 external power.
284
285config SGI_GRU
286 tristate "SGI GRU driver"
287 depends on X86_UV && SMP
288 default n
289 select MMU_NOTIFIER
290 ---help---
291 The GRU is a hardware resource located in the system chipset. The GRU
292 contains memory that can be mmapped into the user address space. This memory is
293 used to communicate with the GRU to perform functions such as load/store,
294 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
295 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
296 user virtual addresses for operands.
297
298 If you are not running on a SGI UV system, say N.
299
300config SGI_GRU_DEBUG
301 bool "SGI GRU driver debug"
302 depends on SGI_GRU
303 default n
304 ---help---
305 This option enables additional debugging code for the SGI GRU driver.
306 If you are unsure, say N.
307
308config APDS9802ALS
309 tristate "Medfield Avago APDS9802 ALS Sensor module"
310 depends on I2C
311 help
312 If you say yes here you get support for the ALS APDS9802 ambient
313 light sensor.
314
315 This driver can also be built as a module. If so, the module
316 will be called apds9802als.
317
318config ISL29003
319 tristate "Intersil ISL29003 ambient light sensor"
320 depends on I2C && SYSFS
321 help
322 If you say yes here you get support for the Intersil ISL29003
323 ambient light sensor.
324
325 This driver can also be built as a module. If so, the module
326 will be called isl29003.
327
328config ISL29020
329 tristate "Intersil ISL29020 ambient light sensor"
330 depends on I2C
331 help
332 If you say yes here you get support for the Intersil ISL29020
333 ambient light sensor.
334
335 This driver can also be built as a module. If so, the module
336 will be called isl29020.
337
338config SENSORS_TSL2550
339 tristate "Taos TSL2550 ambient light sensor"
340 depends on I2C && SYSFS
341 help
342 If you say yes here you get support for the Taos TSL2550
343 ambient light sensor.
344
345 This driver can also be built as a module. If so, the module
346 will be called tsl2550.
347
348config SENSORS_BH1770
349 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
350 depends on I2C
351 ---help---
352 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
353 SFH7770 (Osram) combined ambient light and proximity sensor chip.
354
355 To compile this driver as a module, choose M here: the
356 module will be called bh1770glc. If unsure, say N here.
357
358config SENSORS_APDS990X
359 tristate "APDS990X combined als and proximity sensors"
360 depends on I2C
361 default n
362 ---help---
363 Say Y here if you want to build a driver for Avago APDS990x
364 combined ambient light and proximity sensor chip.
365
366 To compile this driver as a module, choose M here: the
367 module will be called apds990x. If unsure, say N here.
368
369config HMC6352
370 tristate "Honeywell HMC6352 compass"
371 depends on I2C
372 help
373 This driver provides support for the Honeywell HMC6352 compass,
374 providing configuration and heading data via sysfs.
375
376config DS1682
377 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
378 depends on I2C
379 help
380 If you say yes here you get support for Dallas Semiconductor
381 DS1682 Total Elapsed Time Recorder.
382
383 This driver can also be built as a module. If so, the module
384 will be called ds1682.
385
386config SPEAR13XX_PCIE_GADGET
387 bool "PCIe gadget support for SPEAr13XX platform"
388 depends on ARCH_SPEAR13XX && BROKEN
389 default n
390 help
391 This option enables gadget support for PCIe controller. If
392 board file defines any controller as PCIe endpoint then a sysfs
393 entry will be created for that controller. User can use these
394 sysfs node to configure PCIe EP as per his requirements.
395
396config TI_DAC7512
397 tristate "Texas Instruments DAC7512"
398 depends on SPI && SYSFS
399 help
400 If you say yes here you get support for the Texas Instruments
401 DAC7512 16-bit digital-to-analog converter.
402
403 This driver can also be built as a module. If so, the module
404 will be called ti_dac7512.
405
406config VMWARE_BALLOON
407 tristate "VMware Balloon Driver"
408 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
409 help
410 This is VMware physical memory management driver which acts
411 like a "balloon" that can be inflated to reclaim physical pages
412 by reserving them in the guest and invalidating them in the
413 monitor, freeing up the underlying machine pages so they can
414 be allocated to other guests. The balloon can also be deflated
415 to allow the guest to use more physical memory.
416
417 If unsure, say N.
418
419 To compile this driver as a module, choose M here: the
420 module will be called vmw_balloon.
421
422config ARM_CHARLCD
423 bool "ARM Ltd. Character LCD Driver"
424 depends on PLAT_VERSATILE
425 help
426 This is a driver for the character LCD found on the ARM Ltd.
427 Versatile and RealView Platform Baseboards. It doesn't do
428 very much more than display the text "ARM Linux" on the first
429 line and the Linux version on the second line, but that's
430 still useful.
431
432config PCH_PHUB
433 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
434 select GENERIC_NET_UTILS
435 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
436 help
437 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
438 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
439 processor. The Topcliff has MAC address and Option ROM data in SROM.
440 This driver can access MAC address and Option ROM data in SROM.
441
442 This driver also can be used for LAPIS Semiconductor's IOH,
443 ML7213/ML7223/ML7831.
444 ML7213 which is for IVI(In-Vehicle Infotainment) use.
445 ML7223 IOH is for MP(Media Phone) use.
446 ML7831 IOH is for general purpose use.
447 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
448 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
449
450 To compile this driver as a module, choose M here: the module will
451 be called pch_phub.
452
453config USB_SWITCH_FSA9480
454 tristate "FSA9480 USB Switch"
455 depends on I2C
456 help
457 The FSA9480 is a USB port accessory detector and switch.
458 The FSA9480 is fully controlled using I2C and enables USB data,
459 stereo and mono audio, video, microphone and UART data to use
460 a common connector port.
461
462config LATTICE_ECP3_CONFIG
463 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
464 depends on SPI && SYSFS
465 select FW_LOADER
466 default n
467 help
468 This option enables support for bitstream configuration (programming
469 or loading) of the Lattice ECP3 FPGA family via SPI.
470
471 If unsure, say N.
472
473config SRAM
474 bool "Generic on-chip SRAM driver"
475 depends on HAS_IOMEM
476 select GENERIC_ALLOCATOR
477 help
478 This driver allows you to declare a memory region to be managed by
479 the genalloc API. It is supposed to be used for small on-chip SRAM
480 areas found on many SoCs.
481
482config VEXPRESS_SYSCFG
483 bool "Versatile Express System Configuration driver"
484 depends on VEXPRESS_CONFIG
485 default y
486 help
487 ARM Ltd. Versatile Express uses specialised platform configuration
488 bus. System Configuration interface is one of the possible means
489 of generating transactions on this bus.
490config PANEL
491 tristate "Parallel port LCD/Keypad Panel support"
492 depends on PARPORT
493 ---help---
494 Say Y here if you have an HD44780 or KS-0074 LCD connected to your
495 parallel port. This driver also features 4 and 6-key keypads. The LCD
496 is accessible through the /dev/lcd char device (10, 156), and the
497 keypad through /dev/keypad (10, 185). Both require misc device to be
498 enabled. This code can either be compiled as a module, or linked into
499 the kernel and started at boot. If you don't understand what all this
500 is about, say N.
501
502config PANEL_PARPORT
503 int "Default parallel port number (0=LPT1)"
504 depends on PANEL
505 range 0 255
506 default "0"
507 ---help---
508 This is the index of the parallel port the panel is connected to. One
509 driver instance only supports one parallel port, so if your keypad
510 and LCD are connected to two separate ports, you have to start two
511 modules with different arguments. Numbering starts with '0' for LPT1,
512 and so on.
513
514config PANEL_PROFILE
515 int "Default panel profile (0-5, 0=custom)"
516 depends on PANEL
517 range 0 5
518 default "5"
519 ---help---
520 To ease configuration, the driver supports different configuration
521 profiles for past and recent wirings. These profiles can also be
522 used to define an approximative configuration, completed by a few
523 other options. Here are the profiles :
524
525 0 = custom (see further)
526 1 = 2x16 parallel LCD, old keypad
527 2 = 2x16 serial LCD (KS-0074), new keypad
528 3 = 2x16 parallel LCD (Hantronix), no keypad
529 4 = 2x16 parallel LCD (Nexcom NSA1045) with Nexcom's keypad
530 5 = 2x40 parallel LCD (old one), with old keypad
531
532 Custom configurations allow you to define how your display is
533 wired to the parallel port, and how it works. This is only intended
534 for experts.
535
536config PANEL_KEYPAD
537 depends on PANEL && PANEL_PROFILE="0"
538 int "Keypad type (0=none, 1=old 6 keys, 2=new 6 keys, 3=Nexcom 4 keys)"
539 range 0 3
540 default 0
541 ---help---
542 This enables and configures a keypad connected to the parallel port.
543 The keys will be read from character device 10,185. Valid values are :
544
545 0 : do not enable this driver
546 1 : old 6 keys keypad
547 2 : new 6 keys keypad, as used on the server at www.ant-computing.com
548 3 : Nexcom NSA1045's 4 keys keypad
549
550 New profiles can be described in the driver source. The driver also
551 supports simultaneous keys pressed when the keypad supports them.
552
553config PANEL_LCD
554 depends on PANEL && PANEL_PROFILE="0"
555 int "LCD type (0=none, 1=custom, 2=old //, 3=ks0074, 4=hantronix, 5=Nexcom)"
556 range 0 5
557 default 0
558 ---help---
559 This enables and configures an LCD connected to the parallel port.
560 The driver includes an interpreter for escape codes starting with
561 '\e[L' which are specific to the LCD, and a few ANSI codes. The
562 driver will be registered as character device 10,156, usually
563 under the name '/dev/lcd'. There are a total of 6 supported types :
564
565 0 : do not enable the driver
566 1 : custom configuration and wiring (see further)
567 2 : 2x16 & 2x40 parallel LCD (old wiring)
568 3 : 2x16 serial LCD (KS-0074 based)
569 4 : 2x16 parallel LCD (Hantronix wiring)
570 5 : 2x16 parallel LCD (Nexcom wiring)
571
572 When type '1' is specified, other options will appear to configure
573 more precise aspects (wiring, dimensions, protocol, ...). Please note
574 that those values changed from the 2.4 driver for better consistency.
575
576config PANEL_LCD_HEIGHT
577 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
578 int "Number of lines on the LCD (1-2)"
579 range 1 2
580 default 2
581 ---help---
582 This is the number of visible character lines on the LCD in custom profile.
583 It can either be 1 or 2.
584
585config PANEL_LCD_WIDTH
586 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
587 int "Number of characters per line on the LCD (1-40)"
588 range 1 40
589 default 40
590 ---help---
591 This is the number of characters per line on the LCD in custom profile.
592 Common values are 16,20,24,40.
593
594config PANEL_LCD_BWIDTH
595 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
596 int "Internal LCD line width (1-40, 40 by default)"
597 range 1 40
598 default 40
599 ---help---
600 Most LCDs use a standard controller which supports hardware lines of 40
601 characters, although sometimes only 16, 20 or 24 of them are really wired
602 to the terminal. This results in some non-visible but addressable characters,
603 and is the case for most parallel LCDs. Other LCDs, and some serial ones,
604 however, use the same line width internally as what is visible. The KS0074
605 for example, uses 16 characters per line for 16 visible characters per line.
606
607 This option lets you configure the value used by your LCD in 'custom' profile.
608 If you don't know, put '40' here.
609
610config PANEL_LCD_HWIDTH
611 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
612 int "Hardware LCD line width (1-64, 64 by default)"
613 range 1 64
614 default 64
615 ---help---
616 Most LCDs use a single address bit to differentiate line 0 and line 1. Since
617 some of them need to be able to address 40 chars with the lower bits, they
618 often use the immediately superior power of 2, which is 64, to address the
619 next line.
620
621 If you don't know what your LCD uses, in doubt let 16 here for a 2x16, and
622 64 here for a 2x40.
623
624config PANEL_LCD_CHARSET
625 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
626 int "LCD character set (0=normal, 1=KS0074)"
627 range 0 1
628 default 0
629 ---help---
630 Some controllers such as the KS0074 use a somewhat strange character set
631 where many symbols are at unusual places. The driver knows how to map
632 'standard' ASCII characters to the character sets used by these controllers.
633 Valid values are :
634
635 0 : normal (untranslated) character set
636 1 : KS0074 character set
637
638 If you don't know, use the normal one (0).
639
640config PANEL_LCD_PROTO
641 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
642 int "LCD communication mode (0=parallel 8 bits, 1=serial)"
643 range 0 1
644 default 0
645 ---help---
646 This driver now supports any serial or parallel LCD wired to a parallel
647 port. But before assigning signals, the driver needs to know if it will
648 be driving a serial LCD or a parallel one. Serial LCDs only use 2 wires
649 (SDA/SCL), while parallel ones use 2 or 3 wires for the control signals
650 (E, RS, sometimes RW), and 4 or 8 for the data. Use 0 here for a 8 bits
651 parallel LCD, and 1 for a serial LCD.
652
653config PANEL_LCD_PIN_E
654 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
655 int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
656 range -17 17
657 default 14
658 ---help---
659 This describes the number of the parallel port pin to which the LCD 'E'
660 signal has been connected. It can be :
661
662 0 : no connection (eg: connected to ground)
663 1..17 : directly connected to any of these pins on the DB25 plug
664 -1..-17 : connected to the same pin through an inverter (eg: transistor).
665
666 Default for the 'E' pin in custom profile is '14' (AUTOFEED).
667
668config PANEL_LCD_PIN_RS
669 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
670 int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) "
671 range -17 17
672 default 17
673 ---help---
674 This describes the number of the parallel port pin to which the LCD 'RS'
675 signal has been connected. It can be :
676
677 0 : no connection (eg: connected to ground)
678 1..17 : directly connected to any of these pins on the DB25 plug
679 -1..-17 : connected to the same pin through an inverter (eg: transistor).
680
681 Default for the 'RS' pin in custom profile is '17' (SELECT IN).
682
683config PANEL_LCD_PIN_RW
684 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
685 int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) "
686 range -17 17
687 default 16
688 ---help---
689 This describes the number of the parallel port pin to which the LCD 'RW'
690 signal has been connected. It can be :
691
692 0 : no connection (eg: connected to ground)
693 1..17 : directly connected to any of these pins on the DB25 plug
694 -1..-17 : connected to the same pin through an inverter (eg: transistor).
695
696 Default for the 'RW' pin in custom profile is '16' (INIT).
697
698config PANEL_LCD_PIN_SCL
699 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
700 int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) "
701 range -17 17
702 default 1
703 ---help---
704 This describes the number of the parallel port pin to which the serial
705 LCD 'SCL' signal has been connected. It can be :
706
707 0 : no connection (eg: connected to ground)
708 1..17 : directly connected to any of these pins on the DB25 plug
709 -1..-17 : connected to the same pin through an inverter (eg: transistor).
710
711 Default for the 'SCL' pin in custom profile is '1' (STROBE).
712
713config PANEL_LCD_PIN_SDA
714 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
715 int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) "
716 range -17 17
717 default 2
718 ---help---
719 This describes the number of the parallel port pin to which the serial
720 LCD 'SDA' signal has been connected. It can be :
721
722 0 : no connection (eg: connected to ground)
723 1..17 : directly connected to any of these pins on the DB25 plug
724 -1..-17 : connected to the same pin through an inverter (eg: transistor).
725
726 Default for the 'SDA' pin in custom profile is '2' (D0).
727
728config PANEL_LCD_PIN_BL
729 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
730 int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) "
731 range -17 17
732 default 0
733 ---help---
734 This describes the number of the parallel port pin to which the LCD 'BL' signal
735 has been connected. It can be :
736
737 0 : no connection (eg: connected to ground)
738 1..17 : directly connected to any of these pins on the DB25 plug
739 -1..-17 : connected to the same pin through an inverter (eg: transistor).
740
741 Default for the 'BL' pin in custom profile is '0' (uncontrolled).
742
743config PANEL_CHANGE_MESSAGE
744 depends on PANEL
745 bool "Change LCD initialization message ?"
746 default "n"
747 ---help---
748 This allows you to replace the boot message indicating the kernel version
749 and the driver version with a custom message. This is useful on appliances
750 where a simple 'Starting system' message can be enough to stop a customer
751 from worrying.
752
753 If you say 'Y' here, you'll be able to choose a message yourself. Otherwise,
754 say 'N' and keep the default message with the version.
755
756config PANEL_BOOT_MESSAGE
757 depends on PANEL && PANEL_CHANGE_MESSAGE="y"
758 string "New initialization message"
759 default ""
760 ---help---
761 This allows you to replace the boot message indicating the kernel version
762 and the driver version with a custom message. This is useful on appliances
763 where a simple 'Starting system' message can be enough to stop a customer
764 from worrying.
765
766 An empty message will only clear the display at driver init time. Any other
767 printf()-formatted message is valid with newline and escape codes.
768
769source "drivers/misc/c2port/Kconfig"
770source "drivers/misc/eeprom/Kconfig"
771source "drivers/misc/cb710/Kconfig"
772source "drivers/misc/ti-st/Kconfig"
773source "drivers/misc/lis3lv02d/Kconfig"
774source "drivers/misc/altera-stapl/Kconfig"
775source "drivers/misc/mei/Kconfig"
776source "drivers/misc/vmw_vmci/Kconfig"
777source "drivers/misc/mic/Kconfig"
778source "drivers/misc/genwqe/Kconfig"
779source "drivers/misc/echo/Kconfig"
780source "drivers/misc/cxl/Kconfig"
781endmenu