7 config SENSORS_LIS3LV02D
14 tristate "Analog Devices Digital Potentiometers"
15 depends on (I2C || SPI) && SYSFS
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.
28 See Documentation/misc-devices/ad525x_dpot.txt for the
31 This driver can also be built as a module. If so, the module
32 will be called ad525x_dpot.
34 config AD525X_DPOT_I2C
35 tristate "support I2C bus connection"
36 depends on AD525X_DPOT && I2C
38 Say Y here if you have a digital potentiometers hooked to an I2C bus.
40 To compile this driver as a module, choose M here: the
41 module will be called ad525x_dpot-i2c.
43 config AD525X_DPOT_SPI
44 tristate "support SPI bus connection"
45 depends on AD525X_DPOT && SPI_MASTER
47 Say Y here if you have a digital potentiometers hooked to an SPI bus.
49 If unsure, say N (but it's safe to say "Y").
51 To compile this driver as a module, choose M here: the
52 module will be called ad525x_dpot-spi.
55 bool "Atmel AT32/AT91 Timer/Counter Library"
56 depends on (AVR32 || ARCH_AT91)
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.
62 config ATMEL_TCB_CLKSRC
63 bool "TC Block Clocksource"
64 depends on ATMEL_TCLIB
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.
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.
75 config ATMEL_TCB_CLKSRC_BLOCK
77 depends on ATMEL_TCB_CLKSRC
78 prompt "TC Block" if CPU_AT32AP700X
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
88 tristate "Dummy IRQ handler"
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.
96 tristate "Device driver for IBM RSA service processor"
97 depends on X86 && PCI && INPUT
98 depends on SERIAL_8250 || SERIAL_8250=n
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
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
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
118 tristate "Sensable PHANToM (PCI)"
121 Say Y here if you want to build a driver for Sensable PHANToM device.
123 This driver is only for PCI PHANToMs.
125 If you choose to build module, its name will be phantom. If unsure,
129 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
130 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
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).
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.
143 tristate "SGI IOC4 Base IO support"
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.
151 If you have an SGI Altix with an IOC4-based card say Y.
155 tristate "TI Flash Media interface support"
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
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)'.
167 To compile this driver as a module, choose M here: the module will
171 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
172 depends on PCI && TIFM_CORE
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.
180 To compile this driver as a module, choose M here: the module will
184 tristate "Integrated Circuits ICS932S401"
187 If you say yes here you get support for the Integrated Circuits
188 ICS932S401 clock control chips.
190 This driver can also be built as a module. If so, the module
191 will be called ics932s401.
194 tristate "Device driver for Atmel SSC peripheral"
195 depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
197 This option enables device driver support for Atmel Synchronized
198 Serial Communication peripheral (SSC).
200 The SSC peripheral supports a wide variety of serial frame based
201 communications, i.e. I2S, SPI, etc.
205 config ENCLOSURE_SERVICES
206 tristate "Enclosure Services"
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.
215 tristate "Support communication between SGI SSIs"
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
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.
229 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
230 depends on MFD_CS5535
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.
241 config CS5535_MFGPT_DEFAULT_IRQ
243 depends on CS5535_MFGPT
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.
252 config CS5535_CLOCK_EVENT_SRC
253 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
254 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
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.
262 tristate "Channel interface driver for the HP iLO processor"
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.
272 To compile this driver as a module, choose M here: the
273 module will be called hpilo.
276 tristate "Qualcomm coincell charger support"
277 depends on MFD_SPMI_PMIC || COMPILE_TEST
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
286 tristate "SGI GRU driver"
287 depends on X86_UV && SMP
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.
298 If you are not running on a SGI UV system, say N.
301 bool "SGI GRU driver debug"
305 This option enables additional debugging code for the SGI GRU driver.
306 If you are unsure, say N.
309 tristate "Medfield Avago APDS9802 ALS Sensor module"
312 If you say yes here you get support for the ALS APDS9802 ambient
315 This driver can also be built as a module. If so, the module
316 will be called apds9802als.
319 tristate "Intersil ISL29003 ambient light sensor"
320 depends on I2C && SYSFS
322 If you say yes here you get support for the Intersil ISL29003
323 ambient light sensor.
325 This driver can also be built as a module. If so, the module
326 will be called isl29003.
329 tristate "Intersil ISL29020 ambient light sensor"
332 If you say yes here you get support for the Intersil ISL29020
333 ambient light sensor.
335 This driver can also be built as a module. If so, the module
336 will be called isl29020.
338 config SENSORS_TSL2550
339 tristate "Taos TSL2550 ambient light sensor"
340 depends on I2C && SYSFS
342 If you say yes here you get support for the Taos TSL2550
343 ambient light sensor.
345 This driver can also be built as a module. If so, the module
346 will be called tsl2550.
348 config SENSORS_BH1770
349 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
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.
355 To compile this driver as a module, choose M here: the
356 module will be called bh1770glc. If unsure, say N here.
358 config SENSORS_APDS990X
359 tristate "APDS990X combined als and proximity sensors"
363 Say Y here if you want to build a driver for Avago APDS990x
364 combined ambient light and proximity sensor chip.
366 To compile this driver as a module, choose M here: the
367 module will be called apds990x. If unsure, say N here.
370 tristate "Honeywell HMC6352 compass"
373 This driver provides support for the Honeywell HMC6352 compass,
374 providing configuration and heading data via sysfs.
377 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
380 If you say yes here you get support for Dallas Semiconductor
381 DS1682 Total Elapsed Time Recorder.
383 This driver can also be built as a module. If so, the module
384 will be called ds1682.
386 config SPEAR13XX_PCIE_GADGET
387 bool "PCIe gadget support for SPEAr13XX platform"
388 depends on ARCH_SPEAR13XX && BROKEN
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.
397 tristate "Texas Instruments DAC7512"
398 depends on SPI && SYSFS
400 If you say yes here you get support for the Texas Instruments
401 DAC7512 16-bit digital-to-analog converter.
403 This driver can also be built as a module. If so, the module
404 will be called ti_dac7512.
406 config VMWARE_BALLOON
407 tristate "VMware Balloon Driver"
408 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
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.
419 To compile this driver as a module, choose M here: the
420 module will be called vmw_balloon.
423 bool "ARM Ltd. Character LCD Driver"
424 depends on PLAT_VERSATILE
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
437 tristate "BMP085 digital pressure sensor on I2C"
440 depends on I2C && SYSFS
442 Say Y here if you want to support Bosch Sensortec's digital pressure
443 sensor hooked to an I2C bus.
445 To compile this driver as a module, choose M here: the
446 module will be called bmp085-i2c.
449 tristate "BMP085 digital pressure sensor on SPI"
452 depends on SPI_MASTER && SYSFS
454 Say Y here if you want to support Bosch Sensortec's digital pressure
455 sensor hooked to an SPI bus.
457 To compile this driver as a module, choose M here: the
458 module will be called bmp085-spi.
461 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
462 select GENERIC_NET_UTILS
463 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
465 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
466 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
467 processor. The Topcliff has MAC address and Option ROM data in SROM.
468 This driver can access MAC address and Option ROM data in SROM.
470 This driver also can be used for LAPIS Semiconductor's IOH,
471 ML7213/ML7223/ML7831.
472 ML7213 which is for IVI(In-Vehicle Infotainment) use.
473 ML7223 IOH is for MP(Media Phone) use.
474 ML7831 IOH is for general purpose use.
475 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
476 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
478 To compile this driver as a module, choose M here: the module will
481 config USB_SWITCH_FSA9480
482 tristate "FSA9480 USB Switch"
485 The FSA9480 is a USB port accessory detector and switch.
486 The FSA9480 is fully controlled using I2C and enables USB data,
487 stereo and mono audio, video, microphone and UART data to use
488 a common connector port.
490 config LATTICE_ECP3_CONFIG
491 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
492 depends on SPI && SYSFS
496 This option enables support for bitstream configuration (programming
497 or loading) of the Lattice ECP3 FPGA family via SPI.
502 bool "Generic on-chip SRAM driver"
504 select GENERIC_ALLOCATOR
506 This driver allows you to declare a memory region to be managed by
507 the genalloc API. It is supposed to be used for small on-chip SRAM
508 areas found on many SoCs.
510 config VEXPRESS_SYSCFG
511 bool "Versatile Express System Configuration driver"
512 depends on VEXPRESS_CONFIG
515 ARM Ltd. Versatile Express uses specialised platform configuration
516 bus. System Configuration interface is one of the possible means
517 of generating transactions on this bus.
519 tristate "Parallel port LCD/Keypad Panel support"
522 Say Y here if you have an HD44780 or KS-0074 LCD connected to your
523 parallel port. This driver also features 4 and 6-key keypads. The LCD
524 is accessible through the /dev/lcd char device (10, 156), and the
525 keypad through /dev/keypad (10, 185). Both require misc device to be
526 enabled. This code can either be compiled as a module, or linked into
527 the kernel and started at boot. If you don't understand what all this
531 int "Default parallel port number (0=LPT1)"
536 This is the index of the parallel port the panel is connected to. One
537 driver instance only supports one parallel port, so if your keypad
538 and LCD are connected to two separate ports, you have to start two
539 modules with different arguments. Numbering starts with '0' for LPT1,
543 int "Default panel profile (0-5, 0=custom)"
548 To ease configuration, the driver supports different configuration
549 profiles for past and recent wirings. These profiles can also be
550 used to define an approximative configuration, completed by a few
551 other options. Here are the profiles :
553 0 = custom (see further)
554 1 = 2x16 parallel LCD, old keypad
555 2 = 2x16 serial LCD (KS-0074), new keypad
556 3 = 2x16 parallel LCD (Hantronix), no keypad
557 4 = 2x16 parallel LCD (Nexcom NSA1045) with Nexcom's keypad
558 5 = 2x40 parallel LCD (old one), with old keypad
560 Custom configurations allow you to define how your display is
561 wired to the parallel port, and how it works. This is only intended
565 depends on PANEL && PANEL_PROFILE="0"
566 int "Keypad type (0=none, 1=old 6 keys, 2=new 6 keys, 3=Nexcom 4 keys)"
570 This enables and configures a keypad connected to the parallel port.
571 The keys will be read from character device 10,185. Valid values are :
573 0 : do not enable this driver
574 1 : old 6 keys keypad
575 2 : new 6 keys keypad, as used on the server at www.ant-computing.com
576 3 : Nexcom NSA1045's 4 keys keypad
578 New profiles can be described in the driver source. The driver also
579 supports simultaneous keys pressed when the keypad supports them.
582 depends on PANEL && PANEL_PROFILE="0"
583 int "LCD type (0=none, 1=custom, 2=old //, 3=ks0074, 4=hantronix, 5=Nexcom)"
587 This enables and configures an LCD connected to the parallel port.
588 The driver includes an interpreter for escape codes starting with
589 '\e[L' which are specific to the LCD, and a few ANSI codes. The
590 driver will be registered as character device 10,156, usually
591 under the name '/dev/lcd'. There are a total of 6 supported types :
593 0 : do not enable the driver
594 1 : custom configuration and wiring (see further)
595 2 : 2x16 & 2x40 parallel LCD (old wiring)
596 3 : 2x16 serial LCD (KS-0074 based)
597 4 : 2x16 parallel LCD (Hantronix wiring)
598 5 : 2x16 parallel LCD (Nexcom wiring)
600 When type '1' is specified, other options will appear to configure
601 more precise aspects (wiring, dimensions, protocol, ...). Please note
602 that those values changed from the 2.4 driver for better consistency.
604 config PANEL_LCD_HEIGHT
605 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
606 int "Number of lines on the LCD (1-2)"
610 This is the number of visible character lines on the LCD in custom profile.
611 It can either be 1 or 2.
613 config PANEL_LCD_WIDTH
614 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
615 int "Number of characters per line on the LCD (1-40)"
619 This is the number of characters per line on the LCD in custom profile.
620 Common values are 16,20,24,40.
622 config PANEL_LCD_BWIDTH
623 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
624 int "Internal LCD line width (1-40, 40 by default)"
628 Most LCDs use a standard controller which supports hardware lines of 40
629 characters, although sometimes only 16, 20 or 24 of them are really wired
630 to the terminal. This results in some non-visible but addressable characters,
631 and is the case for most parallel LCDs. Other LCDs, and some serial ones,
632 however, use the same line width internally as what is visible. The KS0074
633 for example, uses 16 characters per line for 16 visible characters per line.
635 This option lets you configure the value used by your LCD in 'custom' profile.
636 If you don't know, put '40' here.
638 config PANEL_LCD_HWIDTH
639 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
640 int "Hardware LCD line width (1-64, 64 by default)"
644 Most LCDs use a single address bit to differentiate line 0 and line 1. Since
645 some of them need to be able to address 40 chars with the lower bits, they
646 often use the immediately superior power of 2, which is 64, to address the
649 If you don't know what your LCD uses, in doubt let 16 here for a 2x16, and
652 config PANEL_LCD_CHARSET
653 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
654 int "LCD character set (0=normal, 1=KS0074)"
658 Some controllers such as the KS0074 use a somewhat strange character set
659 where many symbols are at unusual places. The driver knows how to map
660 'standard' ASCII characters to the character sets used by these controllers.
663 0 : normal (untranslated) character set
664 1 : KS0074 character set
666 If you don't know, use the normal one (0).
668 config PANEL_LCD_PROTO
669 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
670 int "LCD communication mode (0=parallel 8 bits, 1=serial)"
674 This driver now supports any serial or parallel LCD wired to a parallel
675 port. But before assigning signals, the driver needs to know if it will
676 be driving a serial LCD or a parallel one. Serial LCDs only use 2 wires
677 (SDA/SCL), while parallel ones use 2 or 3 wires for the control signals
678 (E, RS, sometimes RW), and 4 or 8 for the data. Use 0 here for a 8 bits
679 parallel LCD, and 1 for a serial LCD.
681 config PANEL_LCD_PIN_E
682 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
683 int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
687 This describes the number of the parallel port pin to which the LCD 'E'
688 signal has been connected. It can be :
690 0 : no connection (eg: connected to ground)
691 1..17 : directly connected to any of these pins on the DB25 plug
692 -1..-17 : connected to the same pin through an inverter (eg: transistor).
694 Default for the 'E' pin in custom profile is '14' (AUTOFEED).
696 config PANEL_LCD_PIN_RS
697 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
698 int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) "
702 This describes the number of the parallel port pin to which the LCD 'RS'
703 signal has been connected. It can be :
705 0 : no connection (eg: connected to ground)
706 1..17 : directly connected to any of these pins on the DB25 plug
707 -1..-17 : connected to the same pin through an inverter (eg: transistor).
709 Default for the 'RS' pin in custom profile is '17' (SELECT IN).
711 config PANEL_LCD_PIN_RW
712 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
713 int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) "
717 This describes the number of the parallel port pin to which the LCD 'RW'
718 signal has been connected. It can be :
720 0 : no connection (eg: connected to ground)
721 1..17 : directly connected to any of these pins on the DB25 plug
722 -1..-17 : connected to the same pin through an inverter (eg: transistor).
724 Default for the 'RW' pin in custom profile is '16' (INIT).
726 config PANEL_LCD_PIN_SCL
727 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
728 int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) "
732 This describes the number of the parallel port pin to which the serial
733 LCD 'SCL' signal has been connected. It can be :
735 0 : no connection (eg: connected to ground)
736 1..17 : directly connected to any of these pins on the DB25 plug
737 -1..-17 : connected to the same pin through an inverter (eg: transistor).
739 Default for the 'SCL' pin in custom profile is '1' (STROBE).
741 config PANEL_LCD_PIN_SDA
742 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
743 int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) "
747 This describes the number of the parallel port pin to which the serial
748 LCD 'SDA' signal has been connected. It can be :
750 0 : no connection (eg: connected to ground)
751 1..17 : directly connected to any of these pins on the DB25 plug
752 -1..-17 : connected to the same pin through an inverter (eg: transistor).
754 Default for the 'SDA' pin in custom profile is '2' (D0).
756 config PANEL_LCD_PIN_BL
757 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
758 int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) "
762 This describes the number of the parallel port pin to which the LCD 'BL' signal
763 has been connected. It can be :
765 0 : no connection (eg: connected to ground)
766 1..17 : directly connected to any of these pins on the DB25 plug
767 -1..-17 : connected to the same pin through an inverter (eg: transistor).
769 Default for the 'BL' pin in custom profile is '0' (uncontrolled).
771 config PANEL_CHANGE_MESSAGE
773 bool "Change LCD initialization message ?"
776 This allows you to replace the boot message indicating the kernel version
777 and the driver version with a custom message. This is useful on appliances
778 where a simple 'Starting system' message can be enough to stop a customer
781 If you say 'Y' here, you'll be able to choose a message yourself. Otherwise,
782 say 'N' and keep the default message with the version.
784 config PANEL_BOOT_MESSAGE
785 depends on PANEL && PANEL_CHANGE_MESSAGE="y"
786 string "New initialization message"
789 This allows you to replace the boot message indicating the kernel version
790 and the driver version with a custom message. This is useful on appliances
791 where a simple 'Starting system' message can be enough to stop a customer
794 An empty message will only clear the display at driver init time. Any other
795 printf()-formatted message is valid with newline and escape codes.
797 source "drivers/misc/c2port/Kconfig"
798 source "drivers/misc/eeprom/Kconfig"
799 source "drivers/misc/cb710/Kconfig"
800 source "drivers/misc/ti-st/Kconfig"
801 source "drivers/misc/lis3lv02d/Kconfig"
802 source "drivers/misc/altera-stapl/Kconfig"
803 source "drivers/misc/mei/Kconfig"
804 source "drivers/misc/vmw_vmci/Kconfig"
805 source "drivers/misc/mic/Kconfig"
806 source "drivers/misc/genwqe/Kconfig"
807 source "drivers/misc/echo/Kconfig"
808 source "drivers/misc/cxl/Kconfig"