Kconfig 9.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355
  1. #
  2. # Light sensors
  3. #
  4. # When adding new entries keep the list in alphabetical order
  5. menu "Light sensors"
  6. config ACPI_ALS
  7. tristate "ACPI Ambient Light Sensor"
  8. depends on ACPI
  9. select IIO_BUFFER
  10. select IIO_TRIGGERED_BUFFER
  11. select IIO_KFIFO_BUF
  12. help
  13. Say Y here if you want to build a driver for the ACPI0008
  14. Ambient Light Sensor.
  15. To compile this driver as a module, choose M here: the module will
  16. be called acpi-als.
  17. config ADJD_S311
  18. tristate "ADJD-S311-CR999 digital color sensor"
  19. select IIO_BUFFER
  20. select IIO_TRIGGERED_BUFFER
  21. depends on I2C
  22. help
  23. If you say yes here you get support for the Avago ADJD-S311-CR999
  24. digital color light sensor.
  25. This driver can also be built as a module. If so, the module
  26. will be called adjd_s311.
  27. config AL3320A
  28. tristate "AL3320A ambient light sensor"
  29. depends on I2C
  30. help
  31. Say Y here if you want to build a driver for the Dyna Image AL3320A
  32. ambient light sensor.
  33. To compile this driver as a module, choose M here: the
  34. module will be called al3320a.
  35. config APDS9300
  36. tristate "APDS9300 ambient light sensor"
  37. depends on I2C
  38. help
  39. Say Y here if you want to build a driver for the Avago APDS9300
  40. ambient light sensor.
  41. To compile this driver as a module, choose M here: the
  42. module will be called apds9300.
  43. config APDS9960
  44. tristate "Avago APDS9960 gesture/RGB/ALS/proximity sensor"
  45. select REGMAP_I2C
  46. select IIO_BUFFER
  47. select IIO_KFIFO_BUF
  48. depends on I2C
  49. help
  50. Say Y here to build I2C interface support for the Avago
  51. APDS9960 gesture/RGB/ALS/proximity sensor.
  52. To compile this driver as a module, choose M here: the
  53. module will be called apds9960
  54. config BH1750
  55. tristate "ROHM BH1750 ambient light sensor"
  56. depends on I2C
  57. help
  58. Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
  59. BH1750, BH1751 ambient light sensors.
  60. To compile this driver as a module, choose M here: the module will
  61. be called bh1750.
  62. config BH1780
  63. tristate "ROHM BH1780 ambient light sensor"
  64. depends on I2C
  65. depends on !SENSORS_BH1780
  66. help
  67. Say Y here to build support for the ROHM BH1780GLI ambient
  68. light sensor.
  69. To compile this driver as a module, choose M here: the module will
  70. be called bh1780.
  71. config CM32181
  72. depends on I2C
  73. tristate "CM32181 driver"
  74. help
  75. Say Y here if you use cm32181.
  76. This option enables ambient light sensor using
  77. Capella cm32181 device driver.
  78. To compile this driver as a module, choose M here:
  79. the module will be called cm32181.
  80. config CM3232
  81. depends on I2C
  82. tristate "CM3232 ambient light sensor"
  83. help
  84. Say Y here if you use cm3232.
  85. This option enables ambient light sensor using
  86. Capella Microsystems cm3232 device driver.
  87. To compile this driver as a module, choose M here:
  88. the module will be called cm3232.
  89. config CM3323
  90. depends on I2C
  91. tristate "Capella CM3323 color light sensor"
  92. help
  93. Say Y here if you want to build a driver for Capella CM3323
  94. color sensor.
  95. To compile this driver as a module, choose M here: the module will
  96. be called cm3323.
  97. config CM36651
  98. depends on I2C
  99. tristate "CM36651 driver"
  100. help
  101. Say Y here if you use cm36651.
  102. This option enables proximity & RGB sensor using
  103. Capella cm36651 device driver.
  104. To compile this driver as a module, choose M here:
  105. the module will be called cm36651.
  106. config GP2AP020A00F
  107. tristate "Sharp GP2AP020A00F Proximity/ALS sensor"
  108. depends on I2C
  109. select REGMAP_I2C
  110. select IIO_BUFFER
  111. select IIO_TRIGGERED_BUFFER
  112. select IRQ_WORK
  113. help
  114. Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip
  115. hooked to an I2C bus.
  116. To compile this driver as a module, choose M here: the
  117. module will be called gp2ap020a00f.
  118. config ISL29125
  119. tristate "Intersil ISL29125 digital color light sensor"
  120. depends on I2C
  121. select IIO_BUFFER
  122. select IIO_TRIGGERED_BUFFER
  123. help
  124. Say Y here if you want to build a driver for the Intersil ISL29125
  125. RGB light sensor for I2C.
  126. To compile this driver as a module, choose M here: the module will be
  127. called isl29125.
  128. config HID_SENSOR_ALS
  129. depends on HID_SENSOR_HUB
  130. select IIO_BUFFER
  131. select IIO_TRIGGERED_BUFFER
  132. select HID_SENSOR_IIO_COMMON
  133. select HID_SENSOR_IIO_TRIGGER
  134. tristate "HID ALS"
  135. help
  136. Say yes here to build support for the HID SENSOR
  137. Ambient light sensor.
  138. To compile this driver as a module, choose M here: the
  139. module will be called hid-sensor-als.
  140. config HID_SENSOR_PROX
  141. depends on HID_SENSOR_HUB
  142. select IIO_BUFFER
  143. select IIO_TRIGGERED_BUFFER
  144. select HID_SENSOR_IIO_COMMON
  145. select HID_SENSOR_IIO_TRIGGER
  146. tristate "HID PROX"
  147. help
  148. Say yes here to build support for the HID SENSOR
  149. Proximity sensor.
  150. To compile this driver as a module, choose M here: the
  151. module will be called hid-sensor-prox.
  152. config JSA1212
  153. tristate "JSA1212 ALS and proximity sensor driver"
  154. depends on I2C
  155. select REGMAP_I2C
  156. help
  157. Say Y here if you want to build a IIO driver for JSA1212
  158. proximity & ALS sensor device.
  159. To compile this driver as a module, choose M here:
  160. the module will be called jsa1212.
  161. config RPR0521
  162. tristate "ROHM RPR0521 ALS and proximity sensor driver"
  163. depends on I2C
  164. select REGMAP_I2C
  165. help
  166. Say Y here if you want to build support for ROHM's RPR0521
  167. ambient light and proximity sensor device.
  168. To compile this driver as a module, choose M here:
  169. the module will be called rpr0521.
  170. config SENSORS_LM3533
  171. tristate "LM3533 ambient light sensor"
  172. depends on MFD_LM3533
  173. help
  174. If you say yes here you get support for the ambient light sensor
  175. interface on National Semiconductor / TI LM3533 Lighting Power
  176. chips.
  177. The sensor interface can be used to control the LEDs and backlights
  178. of the chip through defining five light zones and three sets of
  179. corresponding output-current values.
  180. The driver provides raw and mean adc readings along with the current
  181. light zone through sysfs. A threshold event can be generated on zone
  182. changes. The ALS-control output values can be set per zone for the
  183. three current output channels.
  184. config LTR501
  185. tristate "LTR-501ALS-01 light sensor"
  186. depends on I2C
  187. select REGMAP_I2C
  188. select IIO_BUFFER
  189. select IIO_TRIGGERED_BUFFER
  190. help
  191. If you say yes here you get support for the Lite-On LTR-501ALS-01
  192. ambient light and proximity sensor. This driver also supports LTR-559
  193. ALS/PS or LTR-301 ALS sensors.
  194. This driver can also be built as a module. If so, the module
  195. will be called ltr501.
  196. config MAX44000
  197. tristate "MAX44000 Ambient and Infrared Proximity Sensor"
  198. depends on I2C
  199. select REGMAP_I2C
  200. help
  201. Say Y here if you want to build support for Maxim Integrated's
  202. MAX44000 ambient and infrared proximity sensor device.
  203. To compile this driver as a module, choose M here:
  204. the module will be called max44000.
  205. config OPT3001
  206. tristate "Texas Instruments OPT3001 Light Sensor"
  207. depends on I2C
  208. help
  209. If you say Y or M here, you get support for Texas Instruments
  210. OPT3001 Ambient Light Sensor.
  211. If built as a dynamically linked module, it will be called
  212. opt3001.
  213. config PA12203001
  214. tristate "TXC PA12203001 light and proximity sensor"
  215. depends on I2C
  216. select REGMAP_I2C
  217. help
  218. If you say yes here you get support for the TXC PA12203001
  219. ambient light and proximity sensor.
  220. This driver can also be built as a module. If so, the module
  221. will be called pa12203001.
  222. config STK3310
  223. tristate "STK3310 ALS and proximity sensor"
  224. depends on I2C
  225. select REGMAP_I2C
  226. help
  227. Say yes here to get support for the Sensortek STK3310 ambient light
  228. and proximity sensor. The STK3311 model is also supported by this
  229. driver.
  230. Choosing M will build the driver as a module. If so, the module
  231. will be called stk3310.
  232. config TCS3414
  233. tristate "TAOS TCS3414 digital color sensor"
  234. depends on I2C
  235. select IIO_BUFFER
  236. select IIO_TRIGGERED_BUFFER
  237. help
  238. If you say yes here you get support for the TAOS TCS3414
  239. family of digital color sensors.
  240. This driver can also be built as a module. If so, the module
  241. will be called tcs3414.
  242. config TCS3472
  243. tristate "TAOS TCS3472 color light-to-digital converter"
  244. depends on I2C
  245. select IIO_BUFFER
  246. select IIO_TRIGGERED_BUFFER
  247. help
  248. If you say yes here you get support for the TAOS TCS3472
  249. family of color light-to-digital converters with IR filter.
  250. This driver can also be built as a module. If so, the module
  251. will be called tcs3472.
  252. config SENSORS_TSL2563
  253. tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors"
  254. depends on I2C
  255. help
  256. If you say yes here you get support for the Taos TSL2560,
  257. TSL2561, TSL2562 and TSL2563 ambient light sensors.
  258. This driver can also be built as a module. If so, the module
  259. will be called tsl2563.
  260. config TSL4531
  261. tristate "TAOS TSL4531 ambient light sensors"
  262. depends on I2C
  263. help
  264. Say Y here if you want to build a driver for the TAOS TSL4531 family
  265. of ambient light sensors with direct lux output.
  266. To compile this driver as a module, choose M here: the
  267. module will be called tsl4531.
  268. config US5182D
  269. tristate "UPISEMI light and proximity sensor"
  270. depends on I2C
  271. help
  272. If you say yes here you get support for the UPISEMI US5182D
  273. ambient light and proximity sensor.
  274. This driver can also be built as a module. If so, the module
  275. will be called us5182d.
  276. config VCNL4000
  277. tristate "VCNL4000 combined ALS and proximity sensor"
  278. depends on I2C
  279. help
  280. Say Y here if you want to build a driver for the Vishay VCNL4000
  281. combined ambient light and proximity sensor.
  282. To compile this driver as a module, choose M here: the
  283. module will be called vcnl4000.
  284. config VEML6070
  285. tristate "VEML6070 UV A light sensor"
  286. depends on I2C
  287. help
  288. Say Y here if you want to build a driver for the Vishay VEML6070 UV A
  289. light sensor.
  290. To compile this driver as a module, choose M here: the
  291. module will be called veml6070.
  292. endmenu