Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # Misc strange devices
  4. #
  5. menu "Misc devices"
  6. config SENSORS_LIS3LV02D
  7. tristate
  8. depends on INPUT
  9. config AD525X_DPOT
  10. tristate "Analog Devices Digital Potentiometers"
  11. depends on (I2C || SPI) && SYSFS
  12. help
  13. If you say yes here, you get support for the Analog Devices
  14. AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
  15. AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
  16. AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
  17. AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
  18. AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
  19. AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
  20. ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
  21. AD5271, AD5272, AD5274
  22. digital potentiometer chips.
  23. See Documentation/misc-devices/ad525x_dpot.rst for the
  24. userspace interface.
  25. This driver can also be built as a module. If so, the module
  26. will be called ad525x_dpot.
  27. config AD525X_DPOT_I2C
  28. tristate "support I2C bus connection"
  29. depends on AD525X_DPOT && I2C
  30. help
  31. Say Y here if you have a digital potentiometers hooked to an I2C bus.
  32. To compile this driver as a module, choose M here: the
  33. module will be called ad525x_dpot-i2c.
  34. config AD525X_DPOT_SPI
  35. tristate "support SPI bus connection"
  36. depends on AD525X_DPOT && SPI_MASTER
  37. help
  38. Say Y here if you have a digital potentiometers hooked to an SPI bus.
  39. If unsure, say N (but it's safe to say "Y").
  40. To compile this driver as a module, choose M here: the
  41. module will be called ad525x_dpot-spi.
  42. config DUMMY_IRQ
  43. tristate "Dummy IRQ handler"
  44. help
  45. This module accepts a single 'irq' parameter, which it should register for.
  46. The sole purpose of this module is to help with debugging of systems on
  47. which spurious IRQs would happen on disabled IRQ vector.
  48. config IBM_ASM
  49. tristate "Device driver for IBM RSA service processor"
  50. depends on X86 && PCI && INPUT
  51. depends on SERIAL_8250 || SERIAL_8250=n
  52. help
  53. This option enables device driver support for in-band access to the
  54. IBM RSA (Condor) service processor in eServer xSeries systems.
  55. The ibmasm device driver allows user space application to access
  56. ASM (Advanced Systems Management) functions on the service
  57. processor. The driver is meant to be used in conjunction with
  58. a user space API.
  59. The ibmasm driver also enables the OS to use the UART on the
  60. service processor board as a regular serial port. To make use of
  61. this feature serial driver support (CONFIG_SERIAL_8250) must be
  62. enabled.
  63. WARNING: This software may not be supported or function
  64. correctly on your IBM server. Please consult the IBM ServerProven
  65. website <https://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
  66. for information on the specific driver level and support statement
  67. for your IBM server.
  68. config IBMVMC
  69. tristate "IBM Virtual Management Channel support"
  70. depends on PPC_PSERIES
  71. help
  72. This is the IBM POWER Virtual Management Channel
  73. This driver is to be used for the POWER Virtual
  74. Management Channel virtual adapter on the PowerVM
  75. platform. It provides both request/response and
  76. async message support through the /dev/ibmvmc node.
  77. To compile this driver as a module, choose M here: the
  78. module will be called ibmvmc.
  79. config PHANTOM
  80. tristate "Sensable PHANToM (PCI)"
  81. depends on PCI
  82. help
  83. Say Y here if you want to build a driver for Sensable PHANToM device.
  84. This driver is only for PCI PHANToMs.
  85. If you choose to build module, its name will be phantom. If unsure,
  86. say N here.
  87. config TIFM_CORE
  88. tristate "TI Flash Media interface support"
  89. depends on PCI
  90. help
  91. If you want support for Texas Instruments(R) Flash Media adapters
  92. you should select this option and then also choose an appropriate
  93. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  94. support', if you have a TI PCI74xx compatible card reader, for
  95. example.
  96. You will also have to select some flash card format drivers. MMC/SD
  97. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  98. Interface support (MMC_TIFM_SD)'.
  99. To compile this driver as a module, choose M here: the module will
  100. be called tifm_core.
  101. config TIFM_7XX1
  102. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
  103. depends on PCI && TIFM_CORE
  104. default TIFM_CORE
  105. help
  106. This option enables support for Texas Instruments(R) PCI74xx and
  107. PCI76xx families of Flash Media adapters, found in many laptops.
  108. To make actual use of the device, you will have to select some
  109. flash card format drivers, as outlined in the TIFM_CORE Help.
  110. To compile this driver as a module, choose M here: the module will
  111. be called tifm_7xx1.
  112. config ICS932S401
  113. tristate "Integrated Circuits ICS932S401"
  114. depends on I2C
  115. help
  116. If you say yes here you get support for the Integrated Circuits
  117. ICS932S401 clock control chips.
  118. This driver can also be built as a module. If so, the module
  119. will be called ics932s401.
  120. config ATMEL_SSC
  121. tristate "Device driver for Atmel SSC peripheral"
  122. depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
  123. help
  124. This option enables device driver support for Atmel Synchronized
  125. Serial Communication peripheral (SSC).
  126. The SSC peripheral supports a wide variety of serial frame based
  127. communications, i.e. I2S, SPI, etc.
  128. If unsure, say N.
  129. config ENCLOSURE_SERVICES
  130. tristate "Enclosure Services"
  131. help
  132. Provides support for intelligent enclosures (bays which
  133. contain storage devices). You also need either a host
  134. driver (SCSI/ATA) which supports enclosures
  135. or a SCSI enclosure device (SES) to use these services.
  136. config SGI_XP
  137. tristate "Support communication between SGI SSIs"
  138. depends on NET
  139. depends on (IA64_SGI_UV || X86_UV) && SMP
  140. depends on X86_64 || BROKEN
  141. select SGI_GRU if X86_64 && SMP
  142. help
  143. An SGI machine can be divided into multiple Single System
  144. Images which act independently of each other and have
  145. hardware based memory protection from the others. Enabling
  146. this feature will allow for direct communication between SSIs
  147. based on a network adapter and DMA messaging.
  148. config CS5535_MFGPT
  149. tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
  150. depends on MFD_CS5535
  151. help
  152. This driver provides access to MFGPT functionality for other
  153. drivers that need timers. MFGPTs are available in the CS5535 and
  154. CS5536 companion chips that are found in AMD Geode and several
  155. other platforms. They have a better resolution and max interval
  156. than the generic PIT, and are suitable for use as high-res timers.
  157. You probably don't want to enable this manually; other drivers that
  158. make use of it should enable it.
  159. config CS5535_MFGPT_DEFAULT_IRQ
  160. int
  161. depends on CS5535_MFGPT
  162. default 7
  163. help
  164. MFGPTs on the CS5535 require an interrupt. The selected IRQ
  165. can be overridden as a module option as well as by driver that
  166. use the cs5535_mfgpt_ API; however, different architectures might
  167. want to use a different IRQ by default. This is here for
  168. architectures to set as necessary.
  169. config CS5535_CLOCK_EVENT_SRC
  170. tristate "CS5535/CS5536 high-res timer (MFGPT) events"
  171. depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
  172. help
  173. This driver provides a clock event source based on the MFGPT
  174. timer(s) in the CS5535 and CS5536 companion chips.
  175. MFGPTs have a better resolution and max interval than the
  176. generic PIT, and are suitable for use as high-res timers.
  177. config GEHC_ACHC
  178. tristate "GEHC ACHC support"
  179. depends on SPI && SYSFS
  180. depends on SOC_IMX53 || COMPILE_TEST
  181. select FW_LOADER
  182. help
  183. Support for GE ACHC microcontroller, that is part of the GE
  184. PPD device.
  185. To compile this driver as a module, choose M here: the
  186. module will be called gehc-achc.
  187. config HI6421V600_IRQ
  188. tristate "HiSilicon Hi6421v600 IRQ and powerkey"
  189. depends on OF
  190. depends on SPMI
  191. depends on HAS_IOMEM
  192. select MFD_CORE
  193. select REGMAP_SPMI
  194. help
  195. This driver provides IRQ handling for Hi6421v600, used on
  196. some Kirin chipsets, like the one at Hikey 970.
  197. config HP_ILO
  198. tristate "Channel interface driver for the HP iLO processor"
  199. depends on PCI
  200. help
  201. The channel interface driver allows applications to communicate
  202. with iLO management processors present on HP ProLiant servers.
  203. Upon loading, the driver creates /dev/hpilo/dXccbN files, which
  204. can be used to gather data from the management processor, via
  205. read and write system calls.
  206. To compile this driver as a module, choose M here: the
  207. module will be called hpilo.
  208. config QCOM_COINCELL
  209. tristate "Qualcomm coincell charger support"
  210. depends on MFD_SPMI_PMIC || COMPILE_TEST
  211. help
  212. This driver supports the coincell block found inside of
  213. Qualcomm PMICs. The coincell charger provides a means to
  214. charge a coincell battery or backup capacitor which is used
  215. to maintain PMIC register and RTC state in the absence of
  216. external power.
  217. config QCOM_FASTRPC
  218. tristate "Qualcomm FastRPC"
  219. depends on ARCH_QCOM || COMPILE_TEST
  220. depends on RPMSG
  221. select DMA_SHARED_BUFFER
  222. select QCOM_SCM
  223. help
  224. Provides a communication mechanism that allows for clients to
  225. make remote method invocations across processor boundary to
  226. applications DSP processor. Say M if you want to enable this
  227. module.
  228. config SGI_GRU
  229. tristate "SGI GRU driver"
  230. depends on X86_UV && SMP
  231. select MMU_NOTIFIER
  232. help
  233. The GRU is a hardware resource located in the system chipset. The GRU
  234. contains memory that can be mmapped into the user address space. This memory is
  235. used to communicate with the GRU to perform functions such as load/store,
  236. scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
  237. instructions using user virtual addresses. GRU instructions (ex., bcopy) use
  238. user virtual addresses for operands.
  239. If you are not running on a SGI UV system, say N.
  240. config SGI_GRU_DEBUG
  241. bool "SGI GRU driver debug"
  242. depends on SGI_GRU
  243. help
  244. This option enables additional debugging code for the SGI GRU driver.
  245. If you are unsure, say N.
  246. config APDS9802ALS
  247. tristate "Medfield Avago APDS9802 ALS Sensor module"
  248. depends on I2C
  249. help
  250. If you say yes here you get support for the ALS APDS9802 ambient
  251. light sensor.
  252. This driver can also be built as a module. If so, the module
  253. will be called apds9802als.
  254. config ISL29003
  255. tristate "Intersil ISL29003 ambient light sensor"
  256. depends on I2C && SYSFS
  257. help
  258. If you say yes here you get support for the Intersil ISL29003
  259. ambient light sensor.
  260. This driver can also be built as a module. If so, the module
  261. will be called isl29003.
  262. config ISL29020
  263. tristate "Intersil ISL29020 ambient light sensor"
  264. depends on I2C
  265. help
  266. If you say yes here you get support for the Intersil ISL29020
  267. ambient light sensor.
  268. This driver can also be built as a module. If so, the module
  269. will be called isl29020.
  270. config SENSORS_TSL2550
  271. tristate "Taos TSL2550 ambient light sensor"
  272. depends on I2C && SYSFS
  273. help
  274. If you say yes here you get support for the Taos TSL2550
  275. ambient light sensor.
  276. This driver can also be built as a module. If so, the module
  277. will be called tsl2550.
  278. config SENSORS_BH1770
  279. tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
  280. depends on I2C
  281. help
  282. Say Y here if you want to build a driver for BH1770GLC (ROHM) or
  283. SFH7770 (Osram) combined ambient light and proximity sensor chip.
  284. To compile this driver as a module, choose M here: the
  285. module will be called bh1770glc. If unsure, say N here.
  286. config SENSORS_APDS990X
  287. tristate "APDS990X combined als and proximity sensors"
  288. depends on I2C
  289. help
  290. Say Y here if you want to build a driver for Avago APDS990x
  291. combined ambient light and proximity sensor chip.
  292. To compile this driver as a module, choose M here: the
  293. module will be called apds990x. If unsure, say N here.
  294. config HMC6352
  295. tristate "Honeywell HMC6352 compass"
  296. depends on I2C
  297. help
  298. This driver provides support for the Honeywell HMC6352 compass,
  299. providing configuration and heading data via sysfs.
  300. config DS1682
  301. tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
  302. depends on I2C
  303. help
  304. If you say yes here you get support for Dallas Semiconductor
  305. DS1682 Total Elapsed Time Recorder.
  306. This driver can also be built as a module. If so, the module
  307. will be called ds1682.
  308. config VMWARE_BALLOON
  309. tristate "VMware Balloon Driver"
  310. depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
  311. select MEMORY_BALLOON
  312. help
  313. This is VMware physical memory management driver which acts
  314. like a "balloon" that can be inflated to reclaim physical pages
  315. by reserving them in the guest and invalidating them in the
  316. monitor, freeing up the underlying machine pages so they can
  317. be allocated to other guests. The balloon can also be deflated
  318. to allow the guest to use more physical memory.
  319. If unsure, say N.
  320. To compile this driver as a module, choose M here: the
  321. module will be called vmw_balloon.
  322. config PCH_PHUB
  323. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
  324. select GENERIC_NET_UTILS
  325. depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
  326. help
  327. This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
  328. Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
  329. processor. The Topcliff has MAC address and Option ROM data in SROM.
  330. This driver can access MAC address and Option ROM data in SROM.
  331. This driver also can be used for LAPIS Semiconductor's IOH,
  332. ML7213/ML7223/ML7831.
  333. ML7213 which is for IVI(In-Vehicle Infotainment) use.
  334. ML7223 IOH is for MP(Media Phone) use.
  335. ML7831 IOH is for general purpose use.
  336. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  337. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  338. To compile this driver as a module, choose M here: the module will
  339. be called pch_phub.
  340. config LATTICE_ECP3_CONFIG
  341. tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
  342. depends on SPI && SYSFS
  343. select FW_LOADER
  344. default n
  345. help
  346. This option enables support for bitstream configuration (programming
  347. or loading) of the Lattice ECP3 FPGA family via SPI.
  348. If unsure, say N.
  349. config SRAM
  350. bool "Generic on-chip SRAM driver"
  351. depends on HAS_IOMEM
  352. select GENERIC_ALLOCATOR
  353. select SRAM_EXEC if ARM
  354. help
  355. This driver allows you to declare a memory region to be managed by
  356. the genalloc API. It is supposed to be used for small on-chip SRAM
  357. areas found on many SoCs.
  358. config SRAM_EXEC
  359. bool
  360. config DW_XDATA_PCIE
  361. depends on PCI
  362. tristate "Synopsys DesignWare xData PCIe driver"
  363. help
  364. This driver allows controlling Synopsys DesignWare PCIe traffic
  365. generator IP also known as xData, present in Synopsys DesignWare
  366. PCIe Endpoint prototype.
  367. If unsure, say N.
  368. config PCI_ENDPOINT_TEST
  369. depends on PCI
  370. select CRC32
  371. tristate "PCI Endpoint Test driver"
  372. help
  373. Enable this configuration option to enable the host side test driver
  374. for PCI Endpoint.
  375. config XILINX_SDFEC
  376. tristate "Xilinx SDFEC 16"
  377. depends on HAS_IOMEM
  378. help
  379. This option enables support for the Xilinx SDFEC (Soft Decision
  380. Forward Error Correction) driver. This enables a char driver
  381. for the SDFEC.
  382. You may select this driver if your design instantiates the
  383. SDFEC(16nm) hardened block. To compile this as a module choose M.
  384. If unsure, say N.
  385. config MISC_RTSX
  386. tristate
  387. default MISC_RTSX_PCI || MISC_RTSX_USB
  388. config UID_SYS_STATS
  389. bool "Per-UID statistics"
  390. depends on PROFILING && TASK_XACCT && TASK_IO_ACCOUNTING
  391. help
  392. Per UID based cpu time statistics exported to /proc/uid_cputime
  393. Per UID based io statistics exported to /proc/uid_io
  394. Per UID based procstat control in /proc/uid_procstat
  395. config HISI_HIKEY_USB
  396. tristate "USB GPIO Hub on HiSilicon Hikey 960/970 Platform"
  397. depends on (OF && GPIOLIB) || COMPILE_TEST
  398. depends on USB_ROLE_SWITCH
  399. help
  400. If you say yes here this adds support for the on-board USB GPIO hub
  401. found on HiKey 960/970 boards, which is necessary to support
  402. switching between the dual-role USB-C port and the USB-A host ports
  403. using only one USB controller.
  404. config OPEN_DICE
  405. tristate "Open Profile for DICE driver"
  406. depends on OF_RESERVED_MEM
  407. depends on HAS_IOMEM
  408. help
  409. This driver exposes a DICE reserved memory region to userspace via
  410. a character device. The memory region contains Compound Device
  411. Identifiers (CDIs) generated by firmware as an output of DICE
  412. measured boot flow. Userspace can use CDIs for remote attestation
  413. and sealing.
  414. If unsure, say N.
  415. config VCPU_STALL_DETECTOR
  416. tristate "Guest vCPU stall detector"
  417. depends on OF && HAS_IOMEM
  418. help
  419. When this driver is bound inside a KVM guest, it will
  420. periodically "pet" an MMIO stall detector device from each vCPU
  421. and allow the host to detect vCPU stalls.
  422. To compile this driver as a module, choose M here: the module
  423. will be called vcpu_stall_detector.
  424. If you do not intend to run this kernel as a guest, say N.
  425. config QSEECOM_PROXY
  426. tristate "To enable qseecom proxy driver for kernel client"
  427. help
  428. qseecom proxy driver serves the kernel clients by providing
  429. required ops via call back functions with a minimal framework.
  430. These callback functions can be used to start, shutdown and
  431. send commands to the trusted apps.
  432. source "drivers/misc/c2port/Kconfig"
  433. source "drivers/misc/eeprom/Kconfig"
  434. source "drivers/misc/cb710/Kconfig"
  435. source "drivers/misc/ti-st/Kconfig"
  436. source "drivers/misc/lis3lv02d/Kconfig"
  437. source "drivers/misc/altera-stapl/Kconfig"
  438. source "drivers/misc/mei/Kconfig"
  439. source "drivers/misc/vmw_vmci/Kconfig"
  440. source "drivers/misc/genwqe/Kconfig"
  441. source "drivers/misc/echo/Kconfig"
  442. source "drivers/misc/cxl/Kconfig"
  443. source "drivers/misc/ocxl/Kconfig"
  444. source "drivers/misc/bcm-vk/Kconfig"
  445. source "drivers/misc/cardreader/Kconfig"
  446. source "drivers/misc/habanalabs/Kconfig"
  447. source "drivers/misc/uacce/Kconfig"
  448. source "drivers/misc/pvpanic/Kconfig"
  449. source "drivers/misc/mchp_pci1xxxx/Kconfig"
  450. endmenu
  451. #
  452. # Dev-Ril-Bridge driver
  453. #
  454. config DEV_RIL_BRIDGE
  455. tristate "Support a bridge between device and RIL"
  456. default n