| lh | 9ed821d | 2023-04-07 01:36:19 -0700 | [diff] [blame] | 1 | # | 
 | 2 | # Misc strange devices | 
 | 3 | # | 
 | 4 |  | 
 | 5 | menu "Misc devices" | 
 | 6 |  | 
 | 7 | config SENSORS_LIS3LV02D | 
 | 8 | 	tristate | 
 | 9 | 	depends on INPUT | 
 | 10 | 	select INPUT_POLLDEV | 
 | 11 | 	default n | 
 | 12 |  | 
 | 13 | config 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 |  | 
 | 34 | config 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 |  | 
 | 43 | config 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 |  | 
 | 54 | config ATMEL_PWM | 
 | 55 | 	tristate "Atmel AT32/AT91 PWM support" | 
 | 56 | 	depends on HAVE_CLK | 
 | 57 | 	help | 
 | 58 | 	  This option enables device driver support for the PWM channels | 
 | 59 | 	  on certain Atmel processors.  Pulse Width Modulation is used for | 
 | 60 | 	  purposes including software controlled power-efficient backlights | 
 | 61 | 	  on LCD displays, motor control, and waveform generation. | 
 | 62 |  | 
 | 63 | config AB8500_PWM | 
 | 64 | 	bool "AB8500 PWM support" | 
 | 65 | 	depends on AB8500_CORE && ARCH_U8500 | 
 | 66 | 	select HAVE_PWM | 
 | 67 | 	help | 
 | 68 | 	  This driver exports functions to enable/disble/config/free Pulse | 
 | 69 | 	  Width Modulation in the Analog Baseband Chip AB8500. | 
 | 70 | 	  It is used by led and backlight driver to control the intensity. | 
 | 71 |  | 
 | 72 | config ATMEL_TCLIB | 
 | 73 | 	bool "Atmel AT32/AT91 Timer/Counter Library" | 
 | 74 | 	depends on (AVR32 || ARCH_AT91) | 
 | 75 | 	default y if PREEMPT_RT_FULL | 
 | 76 | 	help | 
 | 77 | 	  Select this if you want a library to allocate the Timer/Counter | 
 | 78 | 	  blocks found on many Atmel processors.  This facilitates using | 
 | 79 | 	  these blocks by different drivers despite processor differences. | 
 | 80 |  | 
 | 81 | config ATMEL_TCB_CLKSRC | 
 | 82 | 	bool "TC Block Clocksource" | 
 | 83 | 	depends on ATMEL_TCLIB | 
 | 84 | 	default y | 
 | 85 | 	help | 
 | 86 | 	  Select this to get a high precision clocksource based on a | 
 | 87 | 	  TC block with a 5+ MHz base clock rate.  Two timer channels | 
 | 88 | 	  are combined to make a single 32-bit timer. | 
 | 89 |  | 
 | 90 | 	  When GENERIC_CLOCKEVENTS is defined, the third timer channel | 
 | 91 | 	  may be used as a clock event device supporting oneshot mode. | 
 | 92 |  | 
 | 93 | config ATMEL_TCB_CLKSRC_BLOCK | 
 | 94 | 	int | 
 | 95 | 	depends on ATMEL_TCB_CLKSRC | 
 | 96 | 	prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X | 
 | 97 | 	default 0 | 
 | 98 | 	range 0 1 | 
 | 99 | 	help | 
 | 100 | 	  Some chips provide more than one TC block, so you have the | 
 | 101 | 	  choice of which one to use for the clock framework.  The other | 
 | 102 | 	  TC can be used for other purposes, such as PWM generation and | 
 | 103 | 	  interval timing. | 
 | 104 |  | 
 | 105 | config ATMEL_TCB_CLKSRC_USE_SLOW_CLOCK | 
 | 106 | 	bool "TC Block use 32 KiHz clock" | 
 | 107 | 	depends on ATMEL_TCB_CLKSRC | 
 | 108 | 	default y if !PREEMPT_RT_FULL | 
 | 109 | 	help | 
 | 110 | 	  Select this to use 32 KiHz base clock rate as TC block clock | 
 | 111 | 	  source for clock events. | 
 | 112 |  | 
 | 113 | config IBM_ASM | 
 | 114 | 	tristate "Device driver for IBM RSA service processor" | 
 | 115 | 	depends on X86 && PCI && INPUT && EXPERIMENTAL | 
 | 116 | 	---help--- | 
 | 117 | 	  This option enables device driver support for in-band access to the | 
 | 118 | 	  IBM RSA (Condor) service processor in eServer xSeries systems. | 
 | 119 | 	  The ibmasm device driver allows user space application to access | 
 | 120 | 	  ASM (Advanced Systems Management) functions on the service | 
 | 121 | 	  processor. The driver is meant to be used in conjunction with | 
 | 122 | 	  a user space API. | 
 | 123 | 	  The ibmasm driver also enables the OS to use the UART on the | 
 | 124 | 	  service processor board as a regular serial port. To make use of | 
 | 125 | 	  this feature serial driver support (CONFIG_SERIAL_8250) must be | 
 | 126 | 	  enabled. | 
 | 127 |  | 
 | 128 | 	  WARNING: This software may not be supported or function | 
 | 129 | 	  correctly on your IBM server. Please consult the IBM ServerProven | 
 | 130 | 	  website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/> | 
 | 131 | 	  for information on the specific driver level and support statement | 
 | 132 | 	  for your IBM server. | 
 | 133 |  | 
 | 134 | config HWLAT_DETECTOR | 
 | 135 | 	tristate "Testing module to detect hardware-induced latencies" | 
 | 136 | 	depends on DEBUG_FS | 
 | 137 | 	depends on RING_BUFFER | 
 | 138 | 	default m | 
 | 139 | 	---help--- | 
 | 140 | 	  A simple hardware latency detector. Use this module to detect | 
 | 141 | 	  large latencies introduced by the behavior of the underlying | 
 | 142 | 	  system firmware external to Linux. We do this using periodic | 
 | 143 | 	  use of stop_machine to grab all available CPUs and measure | 
 | 144 | 	  for unexplainable gaps in the CPU timestamp counter(s). By | 
 | 145 | 	  default, the module is not enabled until the "enable" file | 
 | 146 | 	  within the "hwlat_detector" debugfs directory is toggled. | 
 | 147 |  | 
 | 148 | 	  This module is often used to detect SMI (System Management | 
 | 149 | 	  Interrupts) on x86 systems, though is not x86 specific. To | 
 | 150 | 	  this end, we default to using a sample window of 1 second, | 
 | 151 | 	  during which we will sample for 0.5 seconds. If an SMI or | 
 | 152 | 	  similar event occurs during that time, it is recorded | 
 | 153 | 	  into an 8K samples global ring buffer until retreived. | 
 | 154 |  | 
 | 155 | 	  WARNING: This software should never be enabled (it can be built | 
 | 156 | 	  but should not be turned on after it is loaded) in a production | 
 | 157 | 	  environment where high latencies are a concern since the | 
 | 158 | 	  sampling mechanism actually introduces latencies for | 
 | 159 | 	  regular tasks while the CPU(s) are being held. | 
 | 160 |  | 
 | 161 | 	  If unsure, say N | 
 | 162 |  | 
 | 163 | config PHANTOM | 
 | 164 | 	tristate "Sensable PHANToM (PCI)" | 
 | 165 | 	depends on PCI | 
 | 166 | 	help | 
 | 167 | 	  Say Y here if you want to build a driver for Sensable PHANToM device. | 
 | 168 |  | 
 | 169 | 	  This driver is only for PCI PHANToMs. | 
 | 170 |  | 
 | 171 | 	  If you choose to build module, its name will be phantom. If unsure, | 
 | 172 | 	  say N here. | 
 | 173 |  | 
 | 174 | config INTEL_MID_PTI | 
 | 175 | 	tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard" | 
 | 176 | 	depends on PCI | 
 | 177 | 	default n | 
 | 178 | 	help | 
 | 179 | 	  The PTI (Parallel Trace Interface) driver directs | 
 | 180 | 	  trace data routed from various parts in the system out | 
 | 181 | 	  through an Intel Penwell PTI port and out of the mobile | 
 | 182 | 	  device for analysis with a debugging tool (Lauterbach or Fido). | 
 | 183 |  | 
 | 184 | 	  You should select this driver if the target kernel is meant for | 
 | 185 | 	  an Intel Atom (non-netbook) mobile device containing a MIPI | 
 | 186 | 	  P1149.7 standard implementation. | 
 | 187 |  | 
 | 188 | config SGI_IOC4 | 
 | 189 | 	tristate "SGI IOC4 Base IO support" | 
 | 190 | 	depends on PCI | 
 | 191 | 	---help--- | 
 | 192 | 	  This option enables basic support for the IOC4 chip on certain | 
 | 193 | 	  SGI IO controller cards (IO9, IO10, and PCI-RT).  This option | 
 | 194 | 	  does not enable any specific functions on such a card, but provides | 
 | 195 | 	  necessary infrastructure for other drivers to utilize. | 
 | 196 |  | 
 | 197 | 	  If you have an SGI Altix with an IOC4-based card say Y. | 
 | 198 | 	  Otherwise say N. | 
 | 199 |  | 
 | 200 | config TIFM_CORE | 
 | 201 | 	tristate "TI Flash Media interface support (EXPERIMENTAL)" | 
 | 202 | 	depends on EXPERIMENTAL && PCI | 
 | 203 | 	help | 
 | 204 | 	  If you want support for Texas Instruments(R) Flash Media adapters | 
 | 205 | 	  you should select this option and then also choose an appropriate | 
 | 206 | 	  host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter | 
 | 207 | 	  support', if you have a TI PCI74xx compatible card reader, for | 
 | 208 | 	  example. | 
 | 209 | 	  You will also have to select some flash card format drivers. MMC/SD | 
 | 210 | 	  cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD | 
 | 211 | 	  Interface support (MMC_TIFM_SD)'. | 
 | 212 |  | 
 | 213 | 	  To compile this driver as a module, choose M here: the module will | 
 | 214 | 	  be called tifm_core. | 
 | 215 |  | 
 | 216 | config TIFM_7XX1 | 
 | 217 | 	tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)" | 
 | 218 | 	depends on PCI && TIFM_CORE && EXPERIMENTAL | 
 | 219 | 	default TIFM_CORE | 
 | 220 | 	help | 
 | 221 | 	  This option enables support for Texas Instruments(R) PCI74xx and | 
 | 222 | 	  PCI76xx families of Flash Media adapters, found in many laptops. | 
 | 223 | 	  To make actual use of the device, you will have to select some | 
 | 224 | 	  flash card format drivers, as outlined in the TIFM_CORE Help. | 
 | 225 |  | 
 | 226 | 	  To compile this driver as a module, choose M here: the module will | 
 | 227 | 	  be called tifm_7xx1. | 
 | 228 |  | 
 | 229 | config ICS932S401 | 
 | 230 | 	tristate "Integrated Circuits ICS932S401" | 
 | 231 | 	depends on I2C && EXPERIMENTAL | 
 | 232 | 	help | 
 | 233 | 	  If you say yes here you get support for the Integrated Circuits | 
 | 234 | 	  ICS932S401 clock control chips. | 
 | 235 |  | 
 | 236 | 	  This driver can also be built as a module. If so, the module | 
 | 237 | 	  will be called ics932s401. | 
 | 238 |  | 
 | 239 | config ATMEL_SSC | 
 | 240 | 	tristate "Device driver for Atmel SSC peripheral" | 
 | 241 | 	depends on AVR32 || ARCH_AT91 | 
 | 242 | 	---help--- | 
 | 243 | 	  This option enables device driver support for Atmel Synchronized | 
 | 244 | 	  Serial Communication peripheral (SSC). | 
 | 245 |  | 
 | 246 | 	  The SSC peripheral supports a wide variety of serial frame based | 
 | 247 | 	  communications, i.e. I2S, SPI, etc. | 
 | 248 |  | 
 | 249 | 	  If unsure, say N. | 
 | 250 |  | 
 | 251 | config ENCLOSURE_SERVICES | 
 | 252 | 	tristate "Enclosure Services" | 
 | 253 | 	default n | 
 | 254 | 	help | 
 | 255 | 	  Provides support for intelligent enclosures (bays which | 
 | 256 | 	  contain storage devices).  You also need either a host | 
 | 257 | 	  driver (SCSI/ATA) which supports enclosures | 
 | 258 | 	  or a SCSI enclosure device (SES) to use these services. | 
 | 259 |  | 
 | 260 | config SGI_XP | 
 | 261 | 	tristate "Support communication between SGI SSIs" | 
 | 262 | 	depends on NET | 
 | 263 | 	depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP | 
 | 264 | 	select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2 | 
 | 265 | 	select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2 | 
 | 266 | 	select SGI_GRU if X86_64 && SMP | 
 | 267 | 	---help--- | 
 | 268 | 	  An SGI machine can be divided into multiple Single System | 
 | 269 | 	  Images which act independently of each other and have | 
 | 270 | 	  hardware based memory protection from the others.  Enabling | 
 | 271 | 	  this feature will allow for direct communication between SSIs | 
 | 272 | 	  based on a network adapter and DMA messaging. | 
 | 273 |  | 
 | 274 | config CS5535_MFGPT | 
 | 275 | 	tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support" | 
 | 276 | 	depends on PCI && X86 && MFD_CS5535 | 
 | 277 | 	default n | 
 | 278 | 	help | 
 | 279 | 	  This driver provides access to MFGPT functionality for other | 
 | 280 | 	  drivers that need timers.  MFGPTs are available in the CS5535 and | 
 | 281 | 	  CS5536 companion chips that are found in AMD Geode and several | 
 | 282 | 	  other platforms.  They have a better resolution and max interval | 
 | 283 | 	  than the generic PIT, and are suitable for use as high-res timers. | 
 | 284 | 	  You probably don't want to enable this manually; other drivers that | 
 | 285 | 	  make use of it should enable it. | 
 | 286 |  | 
 | 287 | config CS5535_MFGPT_DEFAULT_IRQ | 
 | 288 | 	int | 
 | 289 | 	depends on CS5535_MFGPT | 
 | 290 | 	default 7 | 
 | 291 | 	help | 
 | 292 | 	  MFGPTs on the CS5535 require an interrupt.  The selected IRQ | 
 | 293 | 	  can be overridden as a module option as well as by driver that | 
 | 294 | 	  use the cs5535_mfgpt_ API; however, different architectures might | 
 | 295 | 	  want to use a different IRQ by default.  This is here for | 
 | 296 | 	  architectures to set as necessary. | 
 | 297 |  | 
 | 298 | config CS5535_CLOCK_EVENT_SRC | 
 | 299 | 	tristate "CS5535/CS5536 high-res timer (MFGPT) events" | 
 | 300 | 	depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT | 
 | 301 | 	help | 
 | 302 | 	  This driver provides a clock event source based on the MFGPT | 
 | 303 | 	  timer(s) in the CS5535 and CS5536 companion chips. | 
 | 304 | 	  MFGPTs have a better resolution and max interval than the | 
 | 305 | 	  generic PIT, and are suitable for use as high-res timers. | 
 | 306 |  | 
 | 307 | config HP_ILO | 
 | 308 | 	tristate "Channel interface driver for the HP iLO processor" | 
 | 309 | 	depends on PCI | 
 | 310 | 	default n | 
 | 311 | 	help | 
 | 312 | 	  The channel interface driver allows applications to communicate | 
 | 313 | 	  with iLO management processors present on HP ProLiant servers. | 
 | 314 | 	  Upon loading, the driver creates /dev/hpilo/dXccbN files, which | 
 | 315 | 	  can be used to gather data from the management processor, via | 
 | 316 | 	  read and write system calls. | 
 | 317 |  | 
 | 318 | 	  To compile this driver as a module, choose M here: the | 
 | 319 | 	  module will be called hpilo. | 
 | 320 |  | 
 | 321 | config SGI_GRU | 
 | 322 | 	tristate "SGI GRU driver" | 
 | 323 | 	depends on X86_UV && SMP | 
 | 324 | 	default n | 
 | 325 | 	select MMU_NOTIFIER | 
 | 326 | 	---help--- | 
 | 327 | 	The GRU is a hardware resource located in the system chipset. The GRU | 
 | 328 | 	contains memory that can be mmapped into the user address space. This memory is | 
 | 329 | 	used to communicate with the GRU to perform functions such as load/store, | 
 | 330 | 	scatter/gather, bcopy, AMOs, etc.  The GRU is directly accessed by user | 
 | 331 | 	instructions using user virtual addresses. GRU instructions (ex., bcopy) use | 
 | 332 | 	user virtual addresses for operands. | 
 | 333 |  | 
 | 334 | 	If you are not running on a SGI UV system, say N. | 
 | 335 |  | 
 | 336 | config SGI_GRU_DEBUG | 
 | 337 | 	bool  "SGI GRU driver debug" | 
 | 338 | 	depends on SGI_GRU | 
 | 339 | 	default n | 
 | 340 | 	---help--- | 
 | 341 | 	This option enables addition debugging code for the SGI GRU driver. If | 
 | 342 | 	you are unsure, say N. | 
 | 343 |  | 
 | 344 | config APDS9802ALS | 
 | 345 | 	tristate "Medfield Avago APDS9802 ALS Sensor module" | 
 | 346 | 	depends on I2C | 
 | 347 | 	help | 
 | 348 | 	  If you say yes here you get support for the ALS APDS9802 ambient | 
 | 349 | 	  light sensor. | 
 | 350 |  | 
 | 351 | 	  This driver can also be built as a module.  If so, the module | 
 | 352 | 	  will be called apds9802als. | 
 | 353 |  | 
 | 354 | config ISL29003 | 
 | 355 | 	tristate "Intersil ISL29003 ambient light sensor" | 
 | 356 | 	depends on I2C && SYSFS | 
 | 357 | 	help | 
 | 358 | 	  If you say yes here you get support for the Intersil ISL29003 | 
 | 359 | 	  ambient light sensor. | 
 | 360 |  | 
 | 361 | 	  This driver can also be built as a module.  If so, the module | 
 | 362 | 	  will be called isl29003. | 
 | 363 |  | 
 | 364 | config ISL29020 | 
 | 365 | 	tristate "Intersil ISL29020 ambient light sensor" | 
 | 366 | 	depends on I2C | 
 | 367 | 	help | 
 | 368 | 	  If you say yes here you get support for the Intersil ISL29020 | 
 | 369 | 	  ambient light sensor. | 
 | 370 |  | 
 | 371 | 	  This driver can also be built as a module.  If so, the module | 
 | 372 | 	  will be called isl29020. | 
 | 373 |  | 
 | 374 | config SENSORS_TSL2550 | 
 | 375 | 	tristate "Taos TSL2550 ambient light sensor" | 
 | 376 | 	depends on I2C && SYSFS | 
 | 377 | 	help | 
 | 378 | 	  If you say yes here you get support for the Taos TSL2550 | 
 | 379 | 	  ambient light sensor. | 
 | 380 |  | 
 | 381 | 	  This driver can also be built as a module.  If so, the module | 
 | 382 | 	  will be called tsl2550. | 
 | 383 |  | 
 | 384 | config SENSORS_BH1780 | 
 | 385 | 	tristate "ROHM BH1780GLI ambient light sensor" | 
 | 386 | 	depends on I2C && SYSFS | 
 | 387 | 	help | 
 | 388 | 	  If you say yes here you get support for the ROHM BH1780GLI | 
 | 389 | 	  ambient light sensor. | 
 | 390 |  | 
 | 391 | 	  This driver can also be built as a module.  If so, the module | 
 | 392 | 	  will be called bh1780gli. | 
 | 393 |  | 
 | 394 | config SENSORS_BH1770 | 
 | 395 |          tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" | 
 | 396 |          depends on I2C | 
 | 397 |          ---help--- | 
 | 398 |            Say Y here if you want to build a driver for BH1770GLC (ROHM) or | 
 | 399 | 	   SFH7770 (Osram) combined ambient light and proximity sensor chip. | 
 | 400 |  | 
 | 401 |            To compile this driver as a module, choose M here: the | 
 | 402 |            module will be called bh1770glc. If unsure, say N here. | 
 | 403 |  | 
 | 404 | config SENSORS_APDS990X | 
 | 405 | 	 tristate "APDS990X combined als and proximity sensors" | 
 | 406 | 	 depends on I2C | 
 | 407 | 	 default n | 
 | 408 | 	 ---help--- | 
 | 409 | 	   Say Y here if you want to build a driver for Avago APDS990x | 
 | 410 | 	   combined ambient light and proximity sensor chip. | 
 | 411 |  | 
 | 412 | 	   To compile this driver as a module, choose M here: the | 
 | 413 | 	   module will be called apds990x. If unsure, say N here. | 
 | 414 |  | 
 | 415 | config HMC6352 | 
 | 416 | 	tristate "Honeywell HMC6352 compass" | 
 | 417 | 	depends on I2C | 
 | 418 | 	help | 
 | 419 | 	  This driver provides support for the Honeywell HMC6352 compass, | 
 | 420 | 	  providing configuration and heading data via sysfs. | 
 | 421 |  | 
 | 422 | config SENSORS_AK8975 | 
 | 423 | 	tristate "AK8975 compass support" | 
 | 424 | 	default n | 
 | 425 | 	depends on I2C | 
 | 426 | 	help | 
 | 427 | 	  If you say yes here you get support for Asahi Kasei's | 
 | 428 | 	  orientation sensor AK8975. | 
 | 429 |  | 
 | 430 | config EP93XX_PWM | 
 | 431 | 	tristate "EP93xx PWM support" | 
 | 432 | 	depends on ARCH_EP93XX | 
 | 433 | 	help | 
 | 434 | 	  This option enables device driver support for the PWM channels | 
 | 435 | 	  on the Cirrus EP93xx processors.  The EP9307 chip only has one | 
 | 436 | 	  PWM channel all the others have two, the second channel is an | 
 | 437 | 	  alternate function of the EGPIO14 pin.  A sysfs interface is | 
 | 438 | 	  provided to control the PWM channels. | 
 | 439 |  | 
 | 440 | 	  To compile this driver as a module, choose M here: the module will | 
 | 441 | 	  be called ep93xx_pwm. | 
 | 442 |  | 
 | 443 | config DS1682 | 
 | 444 | 	tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm" | 
 | 445 | 	depends on I2C && EXPERIMENTAL | 
 | 446 | 	help | 
 | 447 | 	  If you say yes here you get support for Dallas Semiconductor | 
 | 448 | 	  DS1682 Total Elapsed Time Recorder. | 
 | 449 |  | 
 | 450 | 	  This driver can also be built as a module.  If so, the module | 
 | 451 | 	  will be called ds1682. | 
 | 452 |  | 
 | 453 | config SPEAR13XX_PCIE_GADGET | 
 | 454 | 	bool "PCIe gadget support for SPEAr13XX platform" | 
 | 455 | 	depends on ARCH_SPEAR13XX | 
 | 456 | 	default n | 
 | 457 | 	help | 
 | 458 | 	 This option enables gadget support for PCIe controller. If | 
 | 459 | 	 board file defines any controller as PCIe endpoint then a sysfs | 
 | 460 | 	 entry will be created for that controller. User can use these | 
 | 461 | 	 sysfs node to configure PCIe EP as per his requirements. | 
 | 462 |  | 
 | 463 | config TI_DAC7512 | 
 | 464 | 	tristate "Texas Instruments DAC7512" | 
 | 465 | 	depends on SPI && SYSFS | 
 | 466 | 	help | 
 | 467 | 	  If you say yes here you get support for the Texas Instruments | 
 | 468 | 	  DAC7512 16-bit digital-to-analog converter. | 
 | 469 |  | 
 | 470 | 	  This driver can also be built as a module. If so, the module | 
 | 471 | 	  will be called ti_dac7512. | 
 | 472 |  | 
 | 473 | config UID_STAT | 
 | 474 | 	bool "UID based statistics tracking exported to /proc/uid_stat" | 
 | 475 | 	default n | 
 | 476 |  | 
 | 477 | config VMWARE_BALLOON | 
 | 478 | 	tristate "VMware Balloon Driver" | 
 | 479 | 	depends on X86 | 
 | 480 | 	help | 
 | 481 | 	  This is VMware physical memory management driver which acts | 
 | 482 | 	  like a "balloon" that can be inflated to reclaim physical pages | 
 | 483 | 	  by reserving them in the guest and invalidating them in the | 
 | 484 | 	  monitor, freeing up the underlying machine pages so they can | 
 | 485 | 	  be allocated to other guests. The balloon can also be deflated | 
 | 486 | 	  to allow the guest to use more physical memory. | 
 | 487 |  | 
 | 488 | 	  If unsure, say N. | 
 | 489 |  | 
 | 490 | 	  To compile this driver as a module, choose M here: the | 
 | 491 | 	  module will be called vmw_balloon. | 
 | 492 |  | 
 | 493 | config ARM_CHARLCD | 
 | 494 | 	bool "ARM Ltd. Character LCD Driver" | 
 | 495 | 	depends on PLAT_VERSATILE | 
 | 496 | 	help | 
 | 497 | 	  This is a driver for the character LCD found on the ARM Ltd. | 
 | 498 | 	  Versatile and RealView Platform Baseboards. It doesn't do | 
 | 499 | 	  very much more than display the text "ARM Linux" on the first | 
 | 500 | 	  line and the Linux version on the second line, but that's | 
 | 501 | 	  still useful. | 
 | 502 |  | 
 | 503 | config BMP085 | 
 | 504 | 	tristate "BMP085 digital pressure sensor" | 
 | 505 | 	depends on I2C && SYSFS | 
 | 506 | 	help | 
 | 507 | 	  If you say yes here you get support for the Bosch Sensortec | 
 | 508 | 	  BMP085 digital pressure sensor. | 
 | 509 |  | 
 | 510 | 	  To compile this driver as a module, choose M here: the | 
 | 511 | 	  module will be called bmp085. | 
 | 512 |  | 
 | 513 | config PCH_PHUB | 
 | 514 | 	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB" | 
 | 515 | 	depends on PCI | 
 | 516 | 	help | 
 | 517 | 	  This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of | 
 | 518 | 	  Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded | 
 | 519 | 	  processor. The Topcliff has MAC address and Option ROM data in SROM. | 
 | 520 | 	  This driver can access MAC address and Option ROM data in SROM. | 
 | 521 |  | 
 | 522 | 	  This driver also can be used for LAPIS Semiconductor's IOH, | 
 | 523 | 	  ML7213/ML7223/ML7831. | 
 | 524 | 	  ML7213 which is for IVI(In-Vehicle Infotainment) use. | 
 | 525 | 	  ML7223 IOH is for MP(Media Phone) use. | 
 | 526 | 	  ML7831 IOH is for general purpose use. | 
 | 527 | 	  ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. | 
 | 528 | 	  ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. | 
 | 529 |  | 
 | 530 | 	  To compile this driver as a module, choose M here: the module will | 
 | 531 | 	  be called pch_phub. | 
 | 532 |  | 
 | 533 | config USB_SWITCH_FSA9480 | 
 | 534 | 	tristate "FSA9480 USB Switch" | 
 | 535 | 	depends on I2C | 
 | 536 | 	help | 
 | 537 | 	  The FSA9480 is a USB port accessory detector and switch. | 
 | 538 | 	  The FSA9480 is fully controlled using I2C and enables USB data, | 
 | 539 | 	  stereo and mono audio, video, microphone and UART data to use | 
 | 540 | 	  a common connector port. | 
 | 541 |  | 
 | 542 | config MAX8997_MUIC | 
 | 543 | 	tristate "MAX8997 MUIC Support" | 
 | 544 | 	depends on MFD_MAX8997 | 
 | 545 | 	help | 
 | 546 | 	  If you say yes here you get support for the MUIC device of | 
 | 547 | 	  Maxim MAX8997 PMIC. | 
 | 548 | 	  The MAX8997 MUIC is a USB port accessory detector and switch. | 
 | 549 |  | 
 | 550 | config WL127X_RFKILL | 
 | 551 | 	tristate "Bluetooth power control driver for TI wl127x" | 
 | 552 | 	depends on RFKILL | 
 | 553 | 	default n | 
 | 554 | 	---help--- | 
 | 555 | 	 Creates an rfkill entry in sysfs for power control of Bluetooth | 
 | 556 | 	 TI wl127x chips. | 
 | 557 | 	  | 
 | 558 | source "drivers/misc/c2port/Kconfig" | 
 | 559 | source "drivers/misc/eeprom/Kconfig" | 
 | 560 | source "drivers/misc/cb710/Kconfig" | 
 | 561 | source "drivers/misc/iwmc3200top/Kconfig" | 
 | 562 | source "drivers/misc/ti-st/Kconfig" | 
 | 563 | source "drivers/misc/lis3lv02d/Kconfig" | 
 | 564 | source "drivers/misc/carma/Kconfig" | 
 | 565 | source "drivers/misc/altera-stapl/Kconfig" | 
 | 566 | endmenu |