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