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)
57 default y if PREEMPT_RT_FULL
59 Select this if you want a library to allocate the Timer/Counter
60 blocks found on many Atmel processors. This facilitates using
61 these blocks by different drivers despite processor differences.
63 config ATMEL_TCB_CLKSRC
64 bool "TC Block Clocksource"
65 depends on ATMEL_TCLIB
68 Select this to get a high precision clocksource based on a
69 TC block with a 5+ MHz base clock rate. Two timer channels
70 are combined to make a single 32-bit timer.
72 When GENERIC_CLOCKEVENTS is defined, the third timer channel
73 may be used as a clock event device supporting oneshot mode.
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
87 config ATMEL_TCB_CLKSRC_USE_SLOW_CLOCK
88 bool "TC Block use 32 KiHz clock"
89 depends on ATMEL_TCB_CLKSRC
90 default y if !PREEMPT_RT_FULL
92 Select this to use 32 KiHz base clock rate as TC block clock
93 source for clock events.
97 tristate "Dummy IRQ handler"
100 This module accepts a single 'irq' parameter, which it should register for.
101 The sole purpose of this module is to help with debugging of systems on
102 which spurious IRQs would happen on disabled IRQ vector.
105 tristate "Device driver for IBM RSA service processor"
106 depends on X86 && PCI && INPUT
107 depends on SERIAL_8250 || SERIAL_8250=n
109 This option enables device driver support for in-band access to the
110 IBM RSA (Condor) service processor in eServer xSeries systems.
111 The ibmasm device driver allows user space application to access
112 ASM (Advanced Systems Management) functions on the service
113 processor. The driver is meant to be used in conjunction with
115 The ibmasm driver also enables the OS to use the UART on the
116 service processor board as a regular serial port. To make use of
117 this feature serial driver support (CONFIG_SERIAL_8250) must be
120 WARNING: This software may not be supported or function
121 correctly on your IBM server. Please consult the IBM ServerProven
122 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
123 for information on the specific driver level and support statement
127 tristate "Sensable PHANToM (PCI)"
130 Say Y here if you want to build a driver for Sensable PHANToM device.
132 This driver is only for PCI PHANToMs.
134 If you choose to build module, its name will be phantom. If unsure,
138 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
139 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
142 The PTI (Parallel Trace Interface) driver directs
143 trace data routed from various parts in the system out
144 through an Intel Penwell PTI port and out of the mobile
145 device for analysis with a debugging tool (Lauterbach or Fido).
147 You should select this driver if the target kernel is meant for
148 an Intel Atom (non-netbook) mobile device containing a MIPI
149 P1149.7 standard implementation.
152 tristate "SGI IOC4 Base IO support"
155 This option enables basic support for the IOC4 chip on certain
156 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
157 does not enable any specific functions on such a card, but provides
158 necessary infrastructure for other drivers to utilize.
160 If you have an SGI Altix with an IOC4-based card say Y.
164 tristate "TI Flash Media interface support"
167 If you want support for Texas Instruments(R) Flash Media adapters
168 you should select this option and then also choose an appropriate
169 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
170 support', if you have a TI PCI74xx compatible card reader, for
172 You will also have to select some flash card format drivers. MMC/SD
173 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
174 Interface support (MMC_TIFM_SD)'.
176 To compile this driver as a module, choose M here: the module will
180 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
181 depends on PCI && TIFM_CORE
184 This option enables support for Texas Instruments(R) PCI74xx and
185 PCI76xx families of Flash Media adapters, found in many laptops.
186 To make actual use of the device, you will have to select some
187 flash card format drivers, as outlined in the TIFM_CORE Help.
189 To compile this driver as a module, choose M here: the module will
193 tristate "Integrated Circuits ICS932S401"
196 If you say yes here you get support for the Integrated Circuits
197 ICS932S401 clock control chips.
199 This driver can also be built as a module. If so, the module
200 will be called ics932s401.
203 tristate "Device driver for Atmel SSC peripheral"
204 depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
206 This option enables device driver support for Atmel Synchronized
207 Serial Communication peripheral (SSC).
209 The SSC peripheral supports a wide variety of serial frame based
210 communications, i.e. I2S, SPI, etc.
214 config ENCLOSURE_SERVICES
215 tristate "Enclosure Services"
218 Provides support for intelligent enclosures (bays which
219 contain storage devices). You also need either a host
220 driver (SCSI/ATA) which supports enclosures
221 or a SCSI enclosure device (SES) to use these services.
224 tristate "Support communication between SGI SSIs"
226 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
227 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
228 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
229 select SGI_GRU if X86_64 && SMP
231 An SGI machine can be divided into multiple Single System
232 Images which act independently of each other and have
233 hardware based memory protection from the others. Enabling
234 this feature will allow for direct communication between SSIs
235 based on a network adapter and DMA messaging.
238 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
239 depends on MFD_CS5535
242 This driver provides access to MFGPT functionality for other
243 drivers that need timers. MFGPTs are available in the CS5535 and
244 CS5536 companion chips that are found in AMD Geode and several
245 other platforms. They have a better resolution and max interval
246 than the generic PIT, and are suitable for use as high-res timers.
247 You probably don't want to enable this manually; other drivers that
248 make use of it should enable it.
250 config CS5535_MFGPT_DEFAULT_IRQ
252 depends on CS5535_MFGPT
255 MFGPTs on the CS5535 require an interrupt. The selected IRQ
256 can be overridden as a module option as well as by driver that
257 use the cs5535_mfgpt_ API; however, different architectures might
258 want to use a different IRQ by default. This is here for
259 architectures to set as necessary.
261 config CS5535_CLOCK_EVENT_SRC
262 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
263 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
265 This driver provides a clock event source based on the MFGPT
266 timer(s) in the CS5535 and CS5536 companion chips.
267 MFGPTs have a better resolution and max interval than the
268 generic PIT, and are suitable for use as high-res timers.
271 tristate "Channel interface driver for the HP iLO processor"
275 The channel interface driver allows applications to communicate
276 with iLO management processors present on HP ProLiant servers.
277 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
278 can be used to gather data from the management processor, via
279 read and write system calls.
281 To compile this driver as a module, choose M here: the
282 module will be called hpilo.
285 tristate "Qualcomm coincell charger support"
286 depends on MFD_SPMI_PMIC || COMPILE_TEST
288 This driver supports the coincell block found inside of
289 Qualcomm PMICs. The coincell charger provides a means to
290 charge a coincell battery or backup capacitor which is used
291 to maintain PMIC register and RTC state in the absence of
295 tristate "SGI GRU driver"
296 depends on X86_UV && SMP
300 The GRU is a hardware resource located in the system chipset. The GRU
301 contains memory that can be mmapped into the user address space. This memory is
302 used to communicate with the GRU to perform functions such as load/store,
303 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
304 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
305 user virtual addresses for operands.
307 If you are not running on a SGI UV system, say N.
310 bool "SGI GRU driver debug"
314 This option enables additional debugging code for the SGI GRU driver.
315 If you are unsure, say N.
318 tristate "Medfield Avago APDS9802 ALS Sensor module"
321 If you say yes here you get support for the ALS APDS9802 ambient
324 This driver can also be built as a module. If so, the module
325 will be called apds9802als.
328 tristate "Intersil ISL29003 ambient light sensor"
329 depends on I2C && SYSFS
331 If you say yes here you get support for the Intersil ISL29003
332 ambient light sensor.
334 This driver can also be built as a module. If so, the module
335 will be called isl29003.
338 tristate "Intersil ISL29020 ambient light sensor"
341 If you say yes here you get support for the Intersil ISL29020
342 ambient light sensor.
344 This driver can also be built as a module. If so, the module
345 will be called isl29020.
347 config SENSORS_TSL2550
348 tristate "Taos TSL2550 ambient light sensor"
349 depends on I2C && SYSFS
351 If you say yes here you get support for the Taos TSL2550
352 ambient light sensor.
354 This driver can also be built as a module. If so, the module
355 will be called tsl2550.
357 config SENSORS_BH1770
358 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
361 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
362 SFH7770 (Osram) combined ambient light and proximity sensor chip.
364 To compile this driver as a module, choose M here: the
365 module will be called bh1770glc. If unsure, say N here.
367 config SENSORS_APDS990X
368 tristate "APDS990X combined als and proximity sensors"
372 Say Y here if you want to build a driver for Avago APDS990x
373 combined ambient light and proximity sensor chip.
375 To compile this driver as a module, choose M here: the
376 module will be called apds990x. If unsure, say N here.
379 tristate "Honeywell HMC6352 compass"
382 This driver provides support for the Honeywell HMC6352 compass,
383 providing configuration and heading data via sysfs.
386 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
389 If you say yes here you get support for Dallas Semiconductor
390 DS1682 Total Elapsed Time Recorder.
392 This driver can also be built as a module. If so, the module
393 will be called ds1682.
395 config SPEAR13XX_PCIE_GADGET
396 bool "PCIe gadget support for SPEAr13XX platform"
397 depends on ARCH_SPEAR13XX && BROKEN
400 This option enables gadget support for PCIe controller. If
401 board file defines any controller as PCIe endpoint then a sysfs
402 entry will be created for that controller. User can use these
403 sysfs node to configure PCIe EP as per his requirements.
406 tristate "Texas Instruments DAC7512"
407 depends on SPI && SYSFS
409 If you say yes here you get support for the Texas Instruments
410 DAC7512 16-bit digital-to-analog converter.
412 This driver can also be built as a module. If so, the module
413 will be called ti_dac7512.
415 config VMWARE_BALLOON
416 tristate "VMware Balloon Driver"
417 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
419 This is VMware physical memory management driver which acts
420 like a "balloon" that can be inflated to reclaim physical pages
421 by reserving them in the guest and invalidating them in the
422 monitor, freeing up the underlying machine pages so they can
423 be allocated to other guests. The balloon can also be deflated
424 to allow the guest to use more physical memory.
428 To compile this driver as a module, choose M here: the
429 module will be called vmw_balloon.
432 bool "ARM Ltd. Character LCD Driver"
433 depends on PLAT_VERSATILE
435 This is a driver for the character LCD found on the ARM Ltd.
436 Versatile and RealView Platform Baseboards. It doesn't do
437 very much more than display the text "ARM Linux" on the first
438 line and the Linux version on the second line, but that's
442 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
443 select GENERIC_NET_UTILS
444 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
446 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
447 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
448 processor. The Topcliff has MAC address and Option ROM data in SROM.
449 This driver can access MAC address and Option ROM data in SROM.
451 This driver also can be used for LAPIS Semiconductor's IOH,
452 ML7213/ML7223/ML7831.
453 ML7213 which is for IVI(In-Vehicle Infotainment) use.
454 ML7223 IOH is for MP(Media Phone) use.
455 ML7831 IOH is for general purpose use.
456 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
457 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
459 To compile this driver as a module, choose M here: the module will
462 config USB_SWITCH_FSA9480
463 tristate "FSA9480 USB Switch"
466 The FSA9480 is a USB port accessory detector and switch.
467 The FSA9480 is fully controlled using I2C and enables USB data,
468 stereo and mono audio, video, microphone and UART data to use
469 a common connector port.
471 config LATTICE_ECP3_CONFIG
472 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
473 depends on SPI && SYSFS
477 This option enables support for bitstream configuration (programming
478 or loading) of the Lattice ECP3 FPGA family via SPI.
483 bool "Generic on-chip SRAM driver"
485 select GENERIC_ALLOCATOR
487 This driver allows you to declare a memory region to be managed by
488 the genalloc API. It is supposed to be used for small on-chip SRAM
489 areas found on many SoCs.
491 config VEXPRESS_SYSCFG
492 bool "Versatile Express System Configuration driver"
493 depends on VEXPRESS_CONFIG
496 ARM Ltd. Versatile Express uses specialised platform configuration
497 bus. System Configuration interface is one of the possible means
498 of generating transactions on this bus.
500 tristate "Parallel port LCD/Keypad Panel support"
503 Say Y here if you have an HD44780 or KS-0074 LCD connected to your
504 parallel port. This driver also features 4 and 6-key keypads. The LCD
505 is accessible through the /dev/lcd char device (10, 156), and the
506 keypad through /dev/keypad (10, 185). Both require misc device to be
507 enabled. This code can either be compiled as a module, or linked into
508 the kernel and started at boot. If you don't understand what all this
512 int "Default parallel port number (0=LPT1)"
517 This is the index of the parallel port the panel is connected to. One
518 driver instance only supports one parallel port, so if your keypad
519 and LCD are connected to two separate ports, you have to start two
520 modules with different arguments. Numbering starts with '0' for LPT1,
524 int "Default panel profile (0-5, 0=custom)"
529 To ease configuration, the driver supports different configuration
530 profiles for past and recent wirings. These profiles can also be
531 used to define an approximative configuration, completed by a few
532 other options. Here are the profiles :
534 0 = custom (see further)
535 1 = 2x16 parallel LCD, old keypad
536 2 = 2x16 serial LCD (KS-0074), new keypad
537 3 = 2x16 parallel LCD (Hantronix), no keypad
538 4 = 2x16 parallel LCD (Nexcom NSA1045) with Nexcom's keypad
539 5 = 2x40 parallel LCD (old one), with old keypad
541 Custom configurations allow you to define how your display is
542 wired to the parallel port, and how it works. This is only intended
546 depends on PANEL && PANEL_PROFILE="0"
547 int "Keypad type (0=none, 1=old 6 keys, 2=new 6 keys, 3=Nexcom 4 keys)"
551 This enables and configures a keypad connected to the parallel port.
552 The keys will be read from character device 10,185. Valid values are :
554 0 : do not enable this driver
555 1 : old 6 keys keypad
556 2 : new 6 keys keypad, as used on the server at www.ant-computing.com
557 3 : Nexcom NSA1045's 4 keys keypad
559 New profiles can be described in the driver source. The driver also
560 supports simultaneous keys pressed when the keypad supports them.
563 depends on PANEL && PANEL_PROFILE="0"
564 int "LCD type (0=none, 1=custom, 2=old //, 3=ks0074, 4=hantronix, 5=Nexcom)"
568 This enables and configures an LCD connected to the parallel port.
569 The driver includes an interpreter for escape codes starting with
570 '\e[L' which are specific to the LCD, and a few ANSI codes. The
571 driver will be registered as character device 10,156, usually
572 under the name '/dev/lcd'. There are a total of 6 supported types :
574 0 : do not enable the driver
575 1 : custom configuration and wiring (see further)
576 2 : 2x16 & 2x40 parallel LCD (old wiring)
577 3 : 2x16 serial LCD (KS-0074 based)
578 4 : 2x16 parallel LCD (Hantronix wiring)
579 5 : 2x16 parallel LCD (Nexcom wiring)
581 When type '1' is specified, other options will appear to configure
582 more precise aspects (wiring, dimensions, protocol, ...). Please note
583 that those values changed from the 2.4 driver for better consistency.
585 config PANEL_LCD_HEIGHT
586 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
587 int "Number of lines on the LCD (1-2)"
591 This is the number of visible character lines on the LCD in custom profile.
592 It can either be 1 or 2.
594 config PANEL_LCD_WIDTH
595 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
596 int "Number of characters per line on the LCD (1-40)"
600 This is the number of characters per line on the LCD in custom profile.
601 Common values are 16,20,24,40.
603 config PANEL_LCD_BWIDTH
604 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
605 int "Internal LCD line width (1-40, 40 by default)"
609 Most LCDs use a standard controller which supports hardware lines of 40
610 characters, although sometimes only 16, 20 or 24 of them are really wired
611 to the terminal. This results in some non-visible but addressable characters,
612 and is the case for most parallel LCDs. Other LCDs, and some serial ones,
613 however, use the same line width internally as what is visible. The KS0074
614 for example, uses 16 characters per line for 16 visible characters per line.
616 This option lets you configure the value used by your LCD in 'custom' profile.
617 If you don't know, put '40' here.
619 config PANEL_LCD_HWIDTH
620 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
621 int "Hardware LCD line width (1-64, 64 by default)"
625 Most LCDs use a single address bit to differentiate line 0 and line 1. Since
626 some of them need to be able to address 40 chars with the lower bits, they
627 often use the immediately superior power of 2, which is 64, to address the
630 If you don't know what your LCD uses, in doubt let 16 here for a 2x16, and
633 config PANEL_LCD_CHARSET
634 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
635 int "LCD character set (0=normal, 1=KS0074)"
639 Some controllers such as the KS0074 use a somewhat strange character set
640 where many symbols are at unusual places. The driver knows how to map
641 'standard' ASCII characters to the character sets used by these controllers.
644 0 : normal (untranslated) character set
645 1 : KS0074 character set
647 If you don't know, use the normal one (0).
649 config PANEL_LCD_PROTO
650 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
651 int "LCD communication mode (0=parallel 8 bits, 1=serial)"
655 This driver now supports any serial or parallel LCD wired to a parallel
656 port. But before assigning signals, the driver needs to know if it will
657 be driving a serial LCD or a parallel one. Serial LCDs only use 2 wires
658 (SDA/SCL), while parallel ones use 2 or 3 wires for the control signals
659 (E, RS, sometimes RW), and 4 or 8 for the data. Use 0 here for a 8 bits
660 parallel LCD, and 1 for a serial LCD.
662 config PANEL_LCD_PIN_E
663 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
664 int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
668 This describes the number of the parallel port pin to which the LCD 'E'
669 signal has been connected. It can be :
671 0 : no connection (eg: connected to ground)
672 1..17 : directly connected to any of these pins on the DB25 plug
673 -1..-17 : connected to the same pin through an inverter (eg: transistor).
675 Default for the 'E' pin in custom profile is '14' (AUTOFEED).
677 config PANEL_LCD_PIN_RS
678 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
679 int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) "
683 This describes the number of the parallel port pin to which the LCD 'RS'
684 signal has been connected. It can be :
686 0 : no connection (eg: connected to ground)
687 1..17 : directly connected to any of these pins on the DB25 plug
688 -1..-17 : connected to the same pin through an inverter (eg: transistor).
690 Default for the 'RS' pin in custom profile is '17' (SELECT IN).
692 config PANEL_LCD_PIN_RW
693 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0"
694 int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) "
698 This describes the number of the parallel port pin to which the LCD 'RW'
699 signal has been connected. It can be :
701 0 : no connection (eg: connected to ground)
702 1..17 : directly connected to any of these pins on the DB25 plug
703 -1..-17 : connected to the same pin through an inverter (eg: transistor).
705 Default for the 'RW' pin in custom profile is '16' (INIT).
707 config PANEL_LCD_PIN_SCL
708 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
709 int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) "
713 This describes the number of the parallel port pin to which the serial
714 LCD 'SCL' signal has been connected. It can be :
716 0 : no connection (eg: connected to ground)
717 1..17 : directly connected to any of these pins on the DB25 plug
718 -1..-17 : connected to the same pin through an inverter (eg: transistor).
720 Default for the 'SCL' pin in custom profile is '1' (STROBE).
722 config PANEL_LCD_PIN_SDA
723 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0"
724 int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) "
728 This describes the number of the parallel port pin to which the serial
729 LCD 'SDA' signal has been connected. It can be :
731 0 : no connection (eg: connected to ground)
732 1..17 : directly connected to any of these pins on the DB25 plug
733 -1..-17 : connected to the same pin through an inverter (eg: transistor).
735 Default for the 'SDA' pin in custom profile is '2' (D0).
737 config PANEL_LCD_PIN_BL
738 depends on PANEL && PANEL_PROFILE="0" && PANEL_LCD="1"
739 int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) "
743 This describes the number of the parallel port pin to which the LCD 'BL' signal
744 has been connected. It can be :
746 0 : no connection (eg: connected to ground)
747 1..17 : directly connected to any of these pins on the DB25 plug
748 -1..-17 : connected to the same pin through an inverter (eg: transistor).
750 Default for the 'BL' pin in custom profile is '0' (uncontrolled).
752 config PANEL_CHANGE_MESSAGE
754 bool "Change LCD initialization message ?"
757 This allows you to replace the boot message indicating the kernel version
758 and the driver version with a custom message. This is useful on appliances
759 where a simple 'Starting system' message can be enough to stop a customer
762 If you say 'Y' here, you'll be able to choose a message yourself. Otherwise,
763 say 'N' and keep the default message with the version.
765 config PANEL_BOOT_MESSAGE
766 depends on PANEL && PANEL_CHANGE_MESSAGE="y"
767 string "New initialization message"
770 This allows you to replace the boot message indicating the kernel version
771 and the driver version with a custom message. This is useful on appliances
772 where a simple 'Starting system' message can be enough to stop a customer
775 An empty message will only clear the display at driver init time. Any other
776 printf()-formatted message is valid with newline and escape codes.
779 tristate "Xilinx SDFEC 16"
781 This option enables support for the Xilinx SDFEC (Soft Decision
782 Forward Error Correction) driver. This enables a char driver
785 You may select this driver if your design instantiates the
786 SDFEC(16nm) hardened block. To compile this as a module choose M.
790 config XILINX_TRAFGEN
791 tristate "Xilinx Traffic Generator"
793 This option enables support for the Xilinx Traffic Generator driver.
794 It is designed to generate AXI4 traffic which can be used to stress
795 different modules/interconnect connected in the system. Different
796 configurable options which are provided through sysfs entries allow
797 allow the user to generate a wide variety of traffic based on their
803 tristate "Xilinx VCU Init"
806 Driver for the Xilinx VCU Init based on the logicoreIP.
808 source "drivers/misc/jesd204b/Kconfig"
809 source "drivers/misc/c2port/Kconfig"
810 source "drivers/misc/eeprom/Kconfig"
811 source "drivers/misc/cb710/Kconfig"
812 source "drivers/misc/ti-st/Kconfig"
813 source "drivers/misc/lis3lv02d/Kconfig"
814 source "drivers/misc/altera-stapl/Kconfig"
815 source "drivers/misc/mei/Kconfig"
816 source "drivers/misc/vmw_vmci/Kconfig"
817 source "drivers/misc/mic/Kconfig"
818 source "drivers/misc/genwqe/Kconfig"
819 source "drivers/misc/echo/Kconfig"
820 source "drivers/misc/cxl/Kconfig"