8 tristate "Rockchip Smartcard Reader Controller support"
11 say Y here to enable Rockchip Smartcard Reader Controller driver
12 for Soc such as RK3128,RK322x,RK3288,RK3368,RK3366 and etc.
14 config SENSORS_LIS3LV02D
21 tristate "Analog Devices Digital Potentiometers"
22 depends on (I2C || SPI) && SYSFS
24 If you say yes here, you get support for the Analog Devices
25 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
26 AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
27 AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
28 AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
29 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
30 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
31 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
32 AD5271, AD5272, AD5274
33 digital potentiometer chips.
35 See Documentation/misc-devices/ad525x_dpot.txt for the
38 This driver can also be built as a module. If so, the module
39 will be called ad525x_dpot.
41 config AD525X_DPOT_I2C
42 tristate "support I2C bus connection"
43 depends on AD525X_DPOT && I2C
45 Say Y here if you have a digital potentiometers hooked to an I2C bus.
47 To compile this driver as a module, choose M here: the
48 module will be called ad525x_dpot-i2c.
50 config AD525X_DPOT_SPI
51 tristate "support SPI bus connection"
52 depends on AD525X_DPOT && SPI_MASTER
54 Say Y here if you have a digital potentiometers hooked to an SPI bus.
56 If unsure, say N (but it's safe to say "Y").
58 To compile this driver as a module, choose M here: the
59 module will be called ad525x_dpot-spi.
62 bool "Atmel AT32/AT91 Timer/Counter Library"
63 depends on (AVR32 || ARCH_AT91)
65 Select this if you want a library to allocate the Timer/Counter
66 blocks found on many Atmel processors. This facilitates using
67 these blocks by different drivers despite processor differences.
69 config ATMEL_TCB_CLKSRC
70 bool "TC Block Clocksource"
71 depends on ATMEL_TCLIB
74 Select this to get a high precision clocksource based on a
75 TC block with a 5+ MHz base clock rate. Two timer channels
76 are combined to make a single 32-bit timer.
78 When GENERIC_CLOCKEVENTS is defined, the third timer channel
79 may be used as a clock event device supporting oneshot mode
80 (delays of up to two seconds) based on the 32 KiHz clock.
82 config ATMEL_TCB_CLKSRC_BLOCK
84 depends on ATMEL_TCB_CLKSRC
85 prompt "TC Block" if CPU_AT32AP700X
89 Some chips provide more than one TC block, so you have the
90 choice of which one to use for the clock framework. The other
91 TC can be used for other purposes, such as PWM generation and
95 tristate "Dummy IRQ handler"
98 This module accepts a single 'irq' parameter, which it should register for.
99 The sole purpose of this module is to help with debugging of systems on
100 which spurious IRQs would happen on disabled IRQ vector.
103 tristate "Device driver for IBM RSA service processor"
104 depends on X86 && PCI && INPUT
106 This option enables device driver support for in-band access to the
107 IBM RSA (Condor) service processor in eServer xSeries systems.
108 The ibmasm device driver allows user space application to access
109 ASM (Advanced Systems Management) functions on the service
110 processor. The driver is meant to be used in conjunction with
112 The ibmasm driver also enables the OS to use the UART on the
113 service processor board as a regular serial port. To make use of
114 this feature serial driver support (CONFIG_SERIAL_8250) must be
117 WARNING: This software may not be supported or function
118 correctly on your IBM server. Please consult the IBM ServerProven
119 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
120 for information on the specific driver level and support statement
124 tristate "Sensable PHANToM (PCI)"
127 Say Y here if you want to build a driver for Sensable PHANToM device.
129 This driver is only for PCI PHANToMs.
131 If you choose to build module, its name will be phantom. If unsure,
135 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
136 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
139 The PTI (Parallel Trace Interface) driver directs
140 trace data routed from various parts in the system out
141 through an Intel Penwell PTI port and out of the mobile
142 device for analysis with a debugging tool (Lauterbach or Fido).
144 You should select this driver if the target kernel is meant for
145 an Intel Atom (non-netbook) mobile device containing a MIPI
146 P1149.7 standard implementation.
149 tristate "SGI IOC4 Base IO support"
152 This option enables basic support for the IOC4 chip on certain
153 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
154 does not enable any specific functions on such a card, but provides
155 necessary infrastructure for other drivers to utilize.
157 If you have an SGI Altix with an IOC4-based card say Y.
161 tristate "TI Flash Media interface support"
164 If you want support for Texas Instruments(R) Flash Media adapters
165 you should select this option and then also choose an appropriate
166 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
167 support', if you have a TI PCI74xx compatible card reader, for
169 You will also have to select some flash card format drivers. MMC/SD
170 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
171 Interface support (MMC_TIFM_SD)'.
173 To compile this driver as a module, choose M here: the module will
177 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
178 depends on PCI && TIFM_CORE
181 This option enables support for Texas Instruments(R) PCI74xx and
182 PCI76xx families of Flash Media adapters, found in many laptops.
183 To make actual use of the device, you will have to select some
184 flash card format drivers, as outlined in the TIFM_CORE Help.
186 To compile this driver as a module, choose M here: the module will
190 tristate "Integrated Circuits ICS932S401"
193 If you say yes here you get support for the Integrated Circuits
194 ICS932S401 clock control chips.
196 This driver can also be built as a module. If so, the module
197 will be called ics932s401.
200 tristate "Device driver for Atmel SSC peripheral"
201 depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
203 This option enables device driver support for Atmel Synchronized
204 Serial Communication peripheral (SSC).
206 The SSC peripheral supports a wide variety of serial frame based
207 communications, i.e. I2S, SPI, etc.
211 config ENCLOSURE_SERVICES
212 tristate "Enclosure Services"
215 Provides support for intelligent enclosures (bays which
216 contain storage devices). You also need either a host
217 driver (SCSI/ATA) which supports enclosures
218 or a SCSI enclosure device (SES) to use these services.
221 tristate "Support communication between SGI SSIs"
223 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
224 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
225 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
226 select SGI_GRU if X86_64 && SMP
228 An SGI machine can be divided into multiple Single System
229 Images which act independently of each other and have
230 hardware based memory protection from the others. Enabling
231 this feature will allow for direct communication between SSIs
232 based on a network adapter and DMA messaging.
235 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
236 depends on MFD_CS5535
239 This driver provides access to MFGPT functionality for other
240 drivers that need timers. MFGPTs are available in the CS5535 and
241 CS5536 companion chips that are found in AMD Geode and several
242 other platforms. They have a better resolution and max interval
243 than the generic PIT, and are suitable for use as high-res timers.
244 You probably don't want to enable this manually; other drivers that
245 make use of it should enable it.
247 config CS5535_MFGPT_DEFAULT_IRQ
249 depends on CS5535_MFGPT
252 MFGPTs on the CS5535 require an interrupt. The selected IRQ
253 can be overridden as a module option as well as by driver that
254 use the cs5535_mfgpt_ API; however, different architectures might
255 want to use a different IRQ by default. This is here for
256 architectures to set as necessary.
258 config CS5535_CLOCK_EVENT_SRC
259 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
260 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
262 This driver provides a clock event source based on the MFGPT
263 timer(s) in the CS5535 and CS5536 companion chips.
264 MFGPTs have a better resolution and max interval than the
265 generic PIT, and are suitable for use as high-res timers.
268 tristate "Channel interface driver for the HP iLO processor"
272 The channel interface driver allows applications to communicate
273 with iLO management processors present on HP ProLiant servers.
274 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
275 can be used to gather data from the management processor, via
276 read and write system calls.
278 To compile this driver as a module, choose M here: the
279 module will be called hpilo.
282 tristate "Qualcomm coincell charger support"
283 depends on MFD_SPMI_PMIC || COMPILE_TEST
285 This driver supports the coincell block found inside of
286 Qualcomm PMICs. The coincell charger provides a means to
287 charge a coincell battery or backup capacitor which is used
288 to maintain PMIC register and RTC state in the absence of
292 tristate "SGI GRU driver"
293 depends on X86_UV && SMP
297 The GRU is a hardware resource located in the system chipset. The GRU
298 contains memory that can be mmapped into the user address space. This memory is
299 used to communicate with the GRU to perform functions such as load/store,
300 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
301 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
302 user virtual addresses for operands.
304 If you are not running on a SGI UV system, say N.
307 bool "SGI GRU driver debug"
311 This option enables additional debugging code for the SGI GRU driver.
312 If you are unsure, say N.
315 tristate "Medfield Avago APDS9802 ALS Sensor module"
318 If you say yes here you get support for the ALS APDS9802 ambient
321 This driver can also be built as a module. If so, the module
322 will be called apds9802als.
325 tristate "Intersil ISL29003 ambient light sensor"
326 depends on I2C && SYSFS
328 If you say yes here you get support for the Intersil ISL29003
329 ambient light sensor.
331 This driver can also be built as a module. If so, the module
332 will be called isl29003.
335 tristate "Intersil ISL29020 ambient light sensor"
338 If you say yes here you get support for the Intersil ISL29020
339 ambient light sensor.
341 This driver can also be built as a module. If so, the module
342 will be called isl29020.
344 config SENSORS_TSL2550
345 tristate "Taos TSL2550 ambient light sensor"
346 depends on I2C && SYSFS
348 If you say yes here you get support for the Taos TSL2550
349 ambient light sensor.
351 This driver can also be built as a module. If so, the module
352 will be called tsl2550.
354 config SENSORS_BH1780
355 tristate "ROHM BH1780GLI ambient light sensor"
356 depends on I2C && SYSFS
358 If you say yes here you get support for the ROHM BH1780GLI
359 ambient light sensor.
361 This driver can also be built as a module. If so, the module
362 will be called bh1780gli.
364 config SENSORS_BH1770
365 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
368 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
369 SFH7770 (Osram) combined ambient light and proximity sensor chip.
371 To compile this driver as a module, choose M here: the
372 module will be called bh1770glc. If unsure, say N here.
374 config SENSORS_APDS990X
375 tristate "APDS990X combined als and proximity sensors"
379 Say Y here if you want to build a driver for Avago APDS990x
380 combined ambient light and proximity sensor chip.
382 To compile this driver as a module, choose M here: the
383 module will be called apds990x. If unsure, say N here.
386 tristate "Honeywell HMC6352 compass"
389 This driver provides support for the Honeywell HMC6352 compass,
390 providing configuration and heading data via sysfs.
393 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
396 If you say yes here you get support for Dallas Semiconductor
397 DS1682 Total Elapsed Time Recorder.
399 This driver can also be built as a module. If so, the module
400 will be called ds1682.
402 config SPEAR13XX_PCIE_GADGET
403 bool "PCIe gadget support for SPEAr13XX platform"
404 depends on ARCH_SPEAR13XX && BROKEN
407 This option enables gadget support for PCIe controller. If
408 board file defines any controller as PCIe endpoint then a sysfs
409 entry will be created for that controller. User can use these
410 sysfs node to configure PCIe EP as per his requirements.
413 tristate "Texas Instruments DAC7512"
414 depends on SPI && SYSFS
416 If you say yes here you get support for the Texas Instruments
417 DAC7512 16-bit digital-to-analog converter.
419 This driver can also be built as a module. If so, the module
420 will be called ti_dac7512.
422 config VMWARE_BALLOON
423 tristate "VMware Balloon Driver"
424 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
426 This is VMware physical memory management driver which acts
427 like a "balloon" that can be inflated to reclaim physical pages
428 by reserving them in the guest and invalidating them in the
429 monitor, freeing up the underlying machine pages so they can
430 be allocated to other guests. The balloon can also be deflated
431 to allow the guest to use more physical memory.
435 To compile this driver as a module, choose M here: the
436 module will be called vmw_balloon.
439 bool "ARM Ltd. Character LCD Driver"
440 depends on PLAT_VERSATILE
442 This is a driver for the character LCD found on the ARM Ltd.
443 Versatile and RealView Platform Baseboards. It doesn't do
444 very much more than display the text "ARM Linux" on the first
445 line and the Linux version on the second line, but that's
453 tristate "BMP085 digital pressure sensor on I2C"
456 depends on I2C && SYSFS
458 Say Y here if you want to support Bosch Sensortec's digital pressure
459 sensor hooked to an I2C bus.
461 To compile this driver as a module, choose M here: the
462 module will be called bmp085-i2c.
465 tristate "BMP085 digital pressure sensor on SPI"
468 depends on SPI_MASTER && SYSFS
470 Say Y here if you want to support Bosch Sensortec's digital pressure
471 sensor hooked to an SPI bus.
473 To compile this driver as a module, choose M here: the
474 module will be called bmp085-spi.
477 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
478 select GENERIC_NET_UTILS
479 depends on PCI && (X86_32 || COMPILE_TEST)
481 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
482 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
483 processor. The Topcliff has MAC address and Option ROM data in SROM.
484 This driver can access MAC address and Option ROM data in SROM.
486 This driver also can be used for LAPIS Semiconductor's IOH,
487 ML7213/ML7223/ML7831.
488 ML7213 which is for IVI(In-Vehicle Infotainment) use.
489 ML7223 IOH is for MP(Media Phone) use.
490 ML7831 IOH is for general purpose use.
491 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
492 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
494 To compile this driver as a module, choose M here: the module will
497 config USB_SWITCH_FSA9480
498 tristate "FSA9480 USB Switch"
501 The FSA9480 is a USB port accessory detector and switch.
502 The FSA9480 is fully controlled using I2C and enables USB data,
503 stereo and mono audio, video, microphone and UART data to use
504 a common connector port.
506 config LATTICE_ECP3_CONFIG
507 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
508 depends on SPI && SYSFS
512 This option enables support for bitstream configuration (programming
513 or loading) of the Lattice ECP3 FPGA family via SPI.
518 bool "Generic on-chip SRAM driver"
520 select GENERIC_ALLOCATOR
522 This driver allows you to declare a memory region to be managed by
523 the genalloc API. It is supposed to be used for small on-chip SRAM
524 areas found on many SoCs.
526 config VEXPRESS_SYSCFG
527 bool "Versatile Express System Configuration driver"
528 depends on VEXPRESS_CONFIG
531 ARM Ltd. Versatile Express uses specialised platform configuration
532 bus. System Configuration interface is one of the possible means
533 of generating transactions on this bus.
536 bool "Per-UID cpu time statistics"
539 Per UID based cpu time statistics exported to /proc/uid_cputime
541 config MEMORY_STATE_TIME
542 tristate "Memory freq/bandwidth time statistics"
545 Memory time statistics exported to /sys/kernel/memory_state_time
547 source "drivers/misc/c2port/Kconfig"
548 source "drivers/misc/eeprom/Kconfig"
549 source "drivers/misc/cb710/Kconfig"
550 source "drivers/misc/ti-st/Kconfig"
551 source "drivers/misc/lis3lv02d/Kconfig"
552 source "drivers/misc/altera-stapl/Kconfig"
553 source "drivers/misc/mei/Kconfig"
554 source "drivers/misc/vmw_vmci/Kconfig"
555 source "drivers/misc/mic/Kconfig"
556 source "drivers/misc/genwqe/Kconfig"
557 source "drivers/misc/echo/Kconfig"
558 source "drivers/misc/cxl/Kconfig"