Файловый менеджер - Редактировать - /var/www/xthruster/html/wp-content/uploads/flags/iio.tar
Назад
afe/Kconfig 0000644 00000000751 14722071307 0006610 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Analog Front End drivers # # When adding new entries keep the list in alphabetical order menu "Analog Front Ends" config IIO_RESCALE tristate "IIO rescale" depends on OF || COMPILE_TEST help Say yes here to build support for the IIO rescaling that handles voltage dividers, current sense shunts and current sense amplifiers. To compile this driver as a module, choose M here: the module will be called iio-rescale. endmenu afe/Makefile 0000644 00000000314 14722071307 0006740 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for industrial I/O Analog Front Ends (AFE) # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_IIO_RESCALE) += iio-rescale.o buffer/Kconfig 0000644 00000003353 14722071307 0007327 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Industrial I/O generic buffer implementations # # When adding new entries keep the list in alphabetical order config IIO_BUFFER_CB tristate "IIO callback buffer used for push in-kernel interfaces" help Should be selected by any drivers that do in-kernel push usage. That is, those where the data is pushed to the consumer. config IIO_BUFFER_DMA tristate help Provides the generic IIO DMA buffer infrastructure that can be used by drivers for devices with DMA support to implement the IIO buffer. Should be selected by drivers that want to use the generic DMA buffer infrastructure. config IIO_BUFFER_DMAENGINE tristate select IIO_BUFFER_DMA help Provides a bonding of the generic IIO DMA buffer infrastructure with the DMAengine framework. This can be used by converter drivers with a DMA port connected to an external DMA controller which is supported by the DMAengine framework. Should be selected by drivers that want to use this functionality. config IIO_BUFFER_HW_CONSUMER tristate "Industrial I/O HW buffering" help Provides a way to bonding when an IIO device has a direct connection to another device in hardware. In this case buffers for data transfers are handled by hardware. Should be selected by drivers that want to use the generic Hw consumer interface. config IIO_KFIFO_BUF tristate "Industrial I/O buffering based on kfifo" help A simple fifo based on kfifo. Note that this currently provides no buffer events so it is up to userspace to work out how often to read from the buffer. config IIO_TRIGGERED_BUFFER tristate select IIO_TRIGGER select IIO_KFIFO_BUF help Provides helper functions for setting up triggered buffers. buffer/Makefile 0000644 00000001013 14722071307 0007453 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the industrial I/O buffer implementations # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_IIO_BUFFER_CB) += industrialio-buffer-cb.o obj-$(CONFIG_IIO_BUFFER_DMA) += industrialio-buffer-dma.o obj-$(CONFIG_IIO_BUFFER_DMAENGINE) += industrialio-buffer-dmaengine.o obj-$(CONFIG_IIO_BUFFER_HW_CONSUMER) += industrialio-hw-consumer.o obj-$(CONFIG_IIO_TRIGGERED_BUFFER) += industrialio-triggered-buffer.o obj-$(CONFIG_IIO_KFIFO_BUF) += kfifo_buf.o light/Kconfig 0000644 00000035465 14722071307 0007176 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Light sensors # # When adding new entries keep the list in alphabetical order menu "Light sensors" config ACPI_ALS tristate "ACPI Ambient Light Sensor" depends on ACPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER select IIO_KFIFO_BUF help Say Y here if you want to build a driver for the ACPI0008 Ambient Light Sensor. To compile this driver as a module, choose M here: the module will be called acpi-als. config ADJD_S311 tristate "ADJD-S311-CR999 digital color sensor" select IIO_BUFFER select IIO_TRIGGERED_BUFFER depends on I2C help If you say yes here you get support for the Avago ADJD-S311-CR999 digital color light sensor. This driver can also be built as a module. If so, the module will be called adjd_s311. config AL3320A tristate "AL3320A ambient light sensor" depends on I2C help Say Y here if you want to build a driver for the Dyna Image AL3320A ambient light sensor. To compile this driver as a module, choose M here: the module will be called al3320a. config APDS9300 tristate "APDS9300 ambient light sensor" depends on I2C help Say Y here if you want to build a driver for the Avago APDS9300 ambient light sensor. To compile this driver as a module, choose M here: the module will be called apds9300. config APDS9960 tristate "Avago APDS9960 gesture/RGB/ALS/proximity sensor" select REGMAP_I2C select IIO_BUFFER select IIO_KFIFO_BUF depends on I2C help Say Y here to build I2C interface support for the Avago APDS9960 gesture/RGB/ALS/proximity sensor. To compile this driver as a module, choose M here: the module will be called apds9960 config BH1750 tristate "ROHM BH1750 ambient light sensor" depends on I2C help Say Y here to build support for the ROHM BH1710, BH1715, BH1721, BH1750, BH1751 ambient light sensors. To compile this driver as a module, choose M here: the module will be called bh1750. config BH1780 tristate "ROHM BH1780 ambient light sensor" depends on I2C help Say Y here to build support for the ROHM BH1780GLI ambient light sensor. To compile this driver as a module, choose M here: the module will be called bh1780. config CM32181 depends on I2C tristate "CM32181 driver" help Say Y here if you use cm32181. This option enables ambient light sensor using Capella cm32181 device driver. To compile this driver as a module, choose M here: the module will be called cm32181. config CM3232 depends on I2C tristate "CM3232 ambient light sensor" help Say Y here if you use cm3232. This option enables ambient light sensor using Capella Microsystems cm3232 device driver. To compile this driver as a module, choose M here: the module will be called cm3232. config CM3323 depends on I2C tristate "Capella CM3323 color light sensor" help Say Y here if you want to build a driver for Capella CM3323 color sensor. To compile this driver as a module, choose M here: the module will be called cm3323. config CM3605 tristate "Capella CM3605 ambient light and proximity sensor" depends on OF help Say Y here if you want to build a driver for Capella CM3605 ambient light and short range proximity sensor. To compile this driver as a module, choose M here: the module will be called cm3605. config CM36651 depends on I2C tristate "CM36651 driver" help Say Y here if you use cm36651. This option enables proximity & RGB sensor using Capella cm36651 device driver. To compile this driver as a module, choose M here: the module will be called cm36651. config IIO_CROS_EC_LIGHT_PROX tristate "ChromeOS EC Light and Proximity Sensors" depends on IIO_CROS_EC_SENSORS_CORE help Say Y here if you use the light and proximity sensors presented by the ChromeOS EC Sensor hub. To compile this driver as a module, choose M here: the module will be called cros_ec_light_prox. config GP2AP020A00F tristate "Sharp GP2AP020A00F Proximity/ALS sensor" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER select IRQ_WORK help Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip hooked to an I2C bus. To compile this driver as a module, choose M here: the module will be called gp2ap020a00f. config SENSORS_ISL29018 tristate "Intersil 29018 light and proximity sensor" depends on I2C select REGMAP_I2C default n help If you say yes here you get support for ambient light sensing and proximity infrared sensing from Intersil ISL29018. This driver will provide the measurements of ambient light intensity in lux, proximity infrared sensing and normal infrared sensing. Data from sensor is accessible via sysfs. config SENSORS_ISL29028 tristate "Intersil ISL29028 Concurrent Light and Proximity Sensor" depends on I2C select REGMAP_I2C help Provides driver for the Intersil's ISL29028 device. This driver supports the sysfs interface to get the ALS, IR intensity, Proximity value via iio. The ISL29028 provides the concurrent sensing of ambient light and proximity. config ISL29125 tristate "Intersil ISL29125 digital color light sensor" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here if you want to build a driver for the Intersil ISL29125 RGB light sensor for I2C. To compile this driver as a module, choose M here: the module will be called isl29125. config HID_SENSOR_ALS depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID ALS" help Say yes here to build support for the HID SENSOR Ambient light sensor. To compile this driver as a module, choose M here: the module will be called hid-sensor-als. config HID_SENSOR_PROX depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID PROX" help Say yes here to build support for the HID SENSOR Proximity sensor. To compile this driver as a module, choose M here: the module will be called hid-sensor-prox. config JSA1212 tristate "JSA1212 ALS and proximity sensor driver" depends on I2C select REGMAP_I2C help Say Y here if you want to build a IIO driver for JSA1212 proximity & ALS sensor device. To compile this driver as a module, choose M here: the module will be called jsa1212. config RPR0521 tristate "ROHM RPR0521 ALS and proximity sensor driver" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here if you want to build support for ROHM's RPR0521 ambient light and proximity sensor device. To compile this driver as a module, choose M here: the module will be called rpr0521. config SENSORS_LM3533 tristate "LM3533 ambient light sensor" depends on MFD_LM3533 help If you say yes here you get support for the ambient light sensor interface on National Semiconductor / TI LM3533 Lighting Power chips. The sensor interface can be used to control the LEDs and backlights of the chip through defining five light zones and three sets of corresponding output-current values. The driver provides raw and mean adc readings along with the current light zone through sysfs. A threshold event can be generated on zone changes. The ALS-control output values can be set per zone for the three current output channels. config LTR501 tristate "LTR-501ALS-01 light sensor" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for the Lite-On LTR-501ALS-01 ambient light and proximity sensor. This driver also supports LTR-559 ALS/PS or LTR-301 ALS sensors. This driver can also be built as a module. If so, the module will be called ltr501. config LV0104CS tristate "LV0104CS Ambient Light Sensor" depends on I2C help Say Y here if you want to build support for the On Semiconductor LV0104CS ambient light sensor. To compile this driver as a module, choose M here: the module will be called lv0104cs. config MAX44000 tristate "MAX44000 Ambient and Infrared Proximity Sensor" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here if you want to build support for Maxim Integrated's MAX44000 ambient and infrared proximity sensor device. To compile this driver as a module, choose M here: the module will be called max44000. config MAX44009 tristate "MAX44009 Ambient Light Sensor" depends on I2C select REGMAP_I2C help Say Y here if you want to build support for Maxim Integrated's MAX44009 ambient light sensor device. To compile this driver as a module, choose M here: the module will be called max44009. config NOA1305 tristate "ON Semiconductor NOA1305 ambient light sensor" depends on I2C select REGMAP_I2C help Say Y here if you want to build support for the ON Semiconductor NOA1305 ambient light sensor. To compile this driver as a module, choose M here: The module will be called noa1305. config OPT3001 tristate "Texas Instruments OPT3001 Light Sensor" depends on I2C help If you say Y or M here, you get support for Texas Instruments OPT3001 Ambient Light Sensor. If built as a dynamically linked module, it will be called opt3001. config PA12203001 tristate "TXC PA12203001 light and proximity sensor" depends on I2C select REGMAP_I2C help If you say yes here you get support for the TXC PA12203001 ambient light and proximity sensor. This driver can also be built as a module. If so, the module will be called pa12203001. config SI1133 tristate "SI1133 UV Index Sensor and Ambient Light Sensor" depends on I2C select REGMAP_I2C help Say Y here if you want to build a driver for the Silicon Labs SI1133 UV Index Sensor and Ambient Light Sensor chip. To compile this driver as a module, choose M here: the module will be called si1133. config SI1145 tristate "SI1132 and SI1141/2/3/5/6/7 combined ALS, UV index and proximity sensor" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here if you want to build a driver for the Silicon Labs SI1132 or SI1141/2/3/5/6/7 combined ambient light, UV index and proximity sensor chips. To compile this driver as a module, choose M here: the module will be called si1145. config STK3310 tristate "STK3310 ALS and proximity sensor" depends on I2C select REGMAP_I2C help Say yes here to get support for the Sensortek STK3310 ambient light and proximity sensor. The STK3311 model is also supported by this driver. Choosing M will build the driver as a module. If so, the module will be called stk3310. config ST_UVIS25 tristate "STMicroelectronics UVIS25 sensor driver" depends on (I2C || SPI) select IIO_BUFFER select IIO_TRIGGERED_BUFFER select ST_UVIS25_I2C if (I2C) select ST_UVIS25_SPI if (SPI_MASTER) help Say yes here to build support for STMicroelectronics UVIS25 uv sensor To compile this driver as a module, choose M here: the module will be called st_uvis25. config ST_UVIS25_I2C tristate depends on ST_UVIS25 select REGMAP_I2C config ST_UVIS25_SPI tristate depends on ST_UVIS25 select REGMAP_SPI config TCS3414 tristate "TAOS TCS3414 digital color sensor" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for the TAOS TCS3414 family of digital color sensors. This driver can also be built as a module. If so, the module will be called tcs3414. config TCS3472 tristate "TAOS TCS3472 color light-to-digital converter" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for the TAOS TCS3472 family of color light-to-digital converters with IR filter. This driver can also be built as a module. If so, the module will be called tcs3472. config SENSORS_TSL2563 tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors" depends on I2C help If you say yes here you get support for the Taos TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors. This driver can also be built as a module. If so, the module will be called tsl2563. config TSL2583 tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters" depends on I2C help Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices. Access ALS data via iio, sysfs. config TSL2772 tristate "TAOS TSL/TMD2x71 and TSL/TMD2x72 Family of light and proximity sensors" depends on I2C help Support for: tsl2571, tsl2671, tmd2671, tsl2771, tmd2771, tsl2572, tsl2672, tmd2672, tsl2772, tmd2772 devices. Provides iio_events and direct access via sysfs. config TSL4531 tristate "TAOS TSL4531 ambient light sensors" depends on I2C help Say Y here if you want to build a driver for the TAOS TSL4531 family of ambient light sensors with direct lux output. To compile this driver as a module, choose M here: the module will be called tsl4531. config US5182D tristate "UPISEMI light and proximity sensor" depends on I2C help If you say yes here you get support for the UPISEMI US5182D ambient light and proximity sensor. This driver can also be built as a module. If so, the module will be called us5182d. config VCNL4000 tristate "VCNL4000/4010/4020/4200 combined ALS and proximity sensor" depends on I2C help Say Y here if you want to build a driver for the Vishay VCNL4000, VCNL4010, VCNL4020, VCNL4200 combined ambient light and proximity sensor. To compile this driver as a module, choose M here: the module will be called vcnl4000. config VCNL4035 tristate "VCNL4035 combined ALS and proximity sensor" select IIO_BUFFER select IIO_TRIGGERED_BUFFER select REGMAP_I2C depends on I2C help Say Y here if you want to build a driver for the Vishay VCNL4035, combined ambient light (ALS) and proximity sensor. Currently only ALS function is available. To compile this driver as a module, choose M here: the module will be called vcnl4035. config VEML6070 tristate "VEML6070 UV A light sensor" depends on I2C help Say Y here if you want to build a driver for the Vishay VEML6070 UV A light sensor. To compile this driver as a module, choose M here: the module will be called veml6070. config VL6180 tristate "VL6180 ALS, range and proximity sensor" depends on I2C help Say Y here if you want to build a driver for the STMicroelectronics VL6180 combined ambient light, range and proximity sensor. To compile this driver as a module, choose M here: the module will be called vl6180. config ZOPT2201 tristate "ZOPT2201 ALS and UV B sensor" depends on I2C help Say Y here if you want to build a driver for the IDT ZOPT2201 ambient light and UV B sensor. To compile this driver as a module, choose M here: the module will be called zopt2201. endmenu light/Makefile 0000644 00000003667 14722071307 0007332 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for IIO Light sensors # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_ACPI_ALS) += acpi-als.o obj-$(CONFIG_ADJD_S311) += adjd_s311.o obj-$(CONFIG_AL3320A) += al3320a.o obj-$(CONFIG_APDS9300) += apds9300.o obj-$(CONFIG_APDS9960) += apds9960.o obj-$(CONFIG_BH1750) += bh1750.o obj-$(CONFIG_BH1780) += bh1780.o obj-$(CONFIG_CM32181) += cm32181.o obj-$(CONFIG_CM3232) += cm3232.o obj-$(CONFIG_CM3323) += cm3323.o obj-$(CONFIG_CM3605) += cm3605.o obj-$(CONFIG_CM36651) += cm36651.o obj-$(CONFIG_IIO_CROS_EC_LIGHT_PROX) += cros_ec_light_prox.o obj-$(CONFIG_GP2AP020A00F) += gp2ap020a00f.o obj-$(CONFIG_HID_SENSOR_ALS) += hid-sensor-als.o obj-$(CONFIG_HID_SENSOR_PROX) += hid-sensor-prox.o obj-$(CONFIG_SENSORS_ISL29018) += isl29018.o obj-$(CONFIG_SENSORS_ISL29028) += isl29028.o obj-$(CONFIG_ISL29125) += isl29125.o obj-$(CONFIG_JSA1212) += jsa1212.o obj-$(CONFIG_SENSORS_LM3533) += lm3533-als.o obj-$(CONFIG_LTR501) += ltr501.o obj-$(CONFIG_LV0104CS) += lv0104cs.o obj-$(CONFIG_MAX44000) += max44000.o obj-$(CONFIG_MAX44009) += max44009.o obj-$(CONFIG_NOA1305) += noa1305.o obj-$(CONFIG_OPT3001) += opt3001.o obj-$(CONFIG_PA12203001) += pa12203001.o obj-$(CONFIG_RPR0521) += rpr0521.o obj-$(CONFIG_SENSORS_TSL2563) += tsl2563.o obj-$(CONFIG_SI1133) += si1133.o obj-$(CONFIG_SI1145) += si1145.o obj-$(CONFIG_STK3310) += stk3310.o obj-$(CONFIG_ST_UVIS25) += st_uvis25_core.o obj-$(CONFIG_ST_UVIS25_I2C) += st_uvis25_i2c.o obj-$(CONFIG_ST_UVIS25_SPI) += st_uvis25_spi.o obj-$(CONFIG_TCS3414) += tcs3414.o obj-$(CONFIG_TCS3472) += tcs3472.o obj-$(CONFIG_TSL2583) += tsl2583.o obj-$(CONFIG_TSL2772) += tsl2772.o obj-$(CONFIG_TSL4531) += tsl4531.o obj-$(CONFIG_US5182D) += us5182d.o obj-$(CONFIG_VCNL4000) += vcnl4000.o obj-$(CONFIG_VCNL4035) += vcnl4035.o obj-$(CONFIG_VEML6070) += veml6070.o obj-$(CONFIG_VL6180) += vl6180.o obj-$(CONFIG_ZOPT2201) += zopt2201.o health/Kconfig 0000644 00000003127 14722071307 0007322 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Health sensors # # When adding new entries keep the list in alphabetical order menu "Health Sensors" menu "Heart Rate Monitors" config AFE4403 tristate "TI AFE4403 Heart Rate Monitor" depends on SPI_MASTER select REGMAP_SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes to choose the Texas Instruments AFE4403 heart rate monitor and low-cost pulse oximeter. To compile this driver as a module, choose M here: the module will be called afe4403. config AFE4404 tristate "TI AFE4404 heart rate and pulse oximeter sensor" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes to choose the Texas Instruments AFE4404 heart rate monitor and low-cost pulse oximeter. To compile this driver as a module, choose M here: the module will be called afe4404. config MAX30100 tristate "MAX30100 heart rate and pulse oximeter sensor" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_KFIFO_BUF help Say Y here to build I2C interface support for the Maxim MAX30100 heart rate, and pulse oximeter sensor. To compile this driver as a module, choose M here: the module will be called max30100. config MAX30102 tristate "MAX30102 heart rate and pulse oximeter sensor" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_KFIFO_BUF help Say Y here to build I2C interface support for the Maxim MAX30102 heart rate, and pulse oximeter sensor. To compile this driver as a module, choose M here: the module will be called max30102. endmenu endmenu health/Makefile 0000644 00000000442 14722071307 0007454 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for IIO Health sensors # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AFE4403) += afe4403.o obj-$(CONFIG_AFE4404) += afe4404.o obj-$(CONFIG_MAX30100) += max30100.o obj-$(CONFIG_MAX30102) += max30102.o trigger/Kconfig 0000644 00000004235 14722071307 0007521 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Industrial I/O standalone triggers # # When adding new entries keep the list in alphabetical order menu "Triggers - standalone" config IIO_HRTIMER_TRIGGER tristate "High resolution timer trigger" depends on IIO_SW_TRIGGER help Provides a frequency based IIO trigger using high resolution timers as interrupt source. To compile this driver as a module, choose M here: the module will be called iio-trig-hrtimer. config IIO_INTERRUPT_TRIGGER tristate "Generic interrupt trigger" help Provides support for using an interrupt of any type as an IIO trigger. This may be provided by a gpio driver for example. To compile this driver as a module, choose M here: the module will be called iio-trig-interrupt. config IIO_STM32_LPTIMER_TRIGGER tristate "STM32 Low-Power Timer Trigger" depends on MFD_STM32_LPTIMER || COMPILE_TEST help Select this option to enable STM32 Low-Power Timer Trigger. This can be used as trigger source for STM32 internal ADC and/or DAC. To compile this driver as a module, choose M here: the module will be called stm32-lptimer-trigger. config IIO_STM32_TIMER_TRIGGER tristate "STM32 Timer Trigger" depends on (ARCH_STM32 && OF && MFD_STM32_TIMERS) || COMPILE_TEST help Select this option to enable STM32 Timer Trigger To compile this driver as a module, choose M here: the module will be called stm32-timer-trigger. config IIO_TIGHTLOOP_TRIGGER tristate "A kthread based hammering loop trigger" depends on IIO_SW_TRIGGER help An experimental trigger, used to allow sensors to be sampled as fast as possible under the limitations of whatever else is going on. Uses a tight loop in a kthread. Will only work with lower half only trigger consumers. To compile this driver as a module, choose M here: the module will be called iio-trig-loop. config IIO_SYSFS_TRIGGER tristate "SYSFS trigger" depends on SYSFS select IRQ_WORK help Provides support for using SYSFS entries as IIO triggers. If unsure, say N (but it's safe to say "Y"). To compile this driver as a module, choose M here: the module will be called iio-trig-sysfs. endmenu trigger/Makefile 0000644 00000001000 14722071307 0007641 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for triggers not associated with iio-devices # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_IIO_HRTIMER_TRIGGER) += iio-trig-hrtimer.o obj-$(CONFIG_IIO_INTERRUPT_TRIGGER) += iio-trig-interrupt.o obj-$(CONFIG_IIO_STM32_LPTIMER_TRIGGER) += stm32-lptimer-trigger.o obj-$(CONFIG_IIO_STM32_TIMER_TRIGGER) += stm32-timer-trigger.o obj-$(CONFIG_IIO_SYSFS_TRIGGER) += iio-trig-sysfs.o obj-$(CONFIG_IIO_TIGHTLOOP_TRIGGER) += iio-trig-loop.o accel/Kconfig 0000644 00000030157 14722071307 0007127 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Accelerometer drivers # # When adding new entries keep the list in alphabetical order menu "Accelerometers" config ADIS16201 tristate "Analog Devices ADIS16201 Dual-Axis Digital Inclinometer and Accelerometer" depends on SPI select IIO_ADIS_LIB select IIO_ADIS_LIB_BUFFER if IIO_BUFFER help Say Y here to build support for Analog Devices adis16201 dual-axis digital inclinometer and accelerometer. To compile this driver as a module, say M here: the module will be called adis16201. config ADIS16209 tristate "Analog Devices ADIS16209 Dual-Axis Digital Inclinometer and Accelerometer" depends on SPI select IIO_ADIS_LIB select IIO_ADIS_LIB_BUFFER if IIO_BUFFER help Say Y here to build support for Analog Devices adis16209 dual-axis digital inclinometer and accelerometer. To compile this driver as a module, say M here: the module will be called adis16209. config ADXL345 tristate config ADXL345_I2C tristate "Analog Devices ADXL345 3-Axis Digital Accelerometer I2C Driver" depends on INPUT_ADXL34X=n depends on I2C select ADXL345 select REGMAP_I2C help Say Y here if you want to build support for the Analog Devices ADXL345 or ADXL375 3-axis digital accelerometer. To compile this driver as a module, choose M here: the module will be called adxl345_i2c and you will also get adxl345_core for the core module. config ADXL345_SPI tristate "Analog Devices ADXL345 3-Axis Digital Accelerometer SPI Driver" depends on INPUT_ADXL34X=n depends on SPI select ADXL345 select REGMAP_SPI help Say Y here if you want to build support for the Analog Devices ADXL345 or ADXL375 3-axis digital accelerometer. To compile this driver as a module, choose M here: the module will be called adxl345_spi and you will also get adxl345_core for the core module. config ADXL372 tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config ADXL372_SPI tristate "Analog Devices ADXL372 3-Axis Accelerometer SPI Driver" depends on SPI select ADXL372 select REGMAP_SPI help Say yes here to add support for the Analog Devices ADXL372 triaxial acceleration sensor. To compile this driver as a module, choose M here: the module will be called adxl372_spi. config ADXL372_I2C tristate "Analog Devices ADXL372 3-Axis Accelerometer I2C Driver" depends on I2C select ADXL372 select REGMAP_I2C help Say yes here to add support for the Analog Devices ADXL372 triaxial acceleration sensor. To compile this driver as a module, choose M here: the module will be called adxl372_i2c. config BMA180 tristate "Bosch BMA180/BMA250 3-Axis Accelerometer Driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here if you want to build a driver for the Bosch BMA180 or BMA250 triaxial acceleration sensor. To compile this driver as a module, choose M here: the module will be called bma180. config BMA220 tristate "Bosch BMA220 3-Axis Accelerometer Driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to add support for the Bosch BMA220 triaxial acceleration sensor. To compile this driver as a module, choose M here: the module will be called bma220_spi. config BMC150_ACCEL tristate "Bosch BMC150 Accelerometer Driver" select IIO_BUFFER select IIO_TRIGGERED_BUFFER select REGMAP select BMC150_ACCEL_I2C if I2C select BMC150_ACCEL_SPI if SPI help Say yes here to build support for the following Bosch accelerometers: BMC150, BMI055, BMA250E, BMA222E, BMA255, BMA280. This is a combo module with both accelerometer and magnetometer. This driver is only implementing accelerometer part, which has its own address and register map. config BMC150_ACCEL_I2C tristate select REGMAP_I2C config BMC150_ACCEL_SPI tristate select REGMAP_SPI config DA280 tristate "MiraMEMS DA280 3-axis 14-bit digital accelerometer driver" depends on I2C help Say yes here to build support for the MiraMEMS DA280 3-axis 14-bit digital accelerometer. To compile this driver as a module, choose M here: the module will be called da280. config DA311 tristate "MiraMEMS DA311 3-axis 12-bit digital accelerometer driver" depends on I2C help Say yes here to build support for the MiraMEMS DA311 3-axis 12-bit digital accelerometer. To compile this driver as a module, choose M here: the module will be called da311. config DMARD06 tristate "Domintech DMARD06 Digital Accelerometer Driver" depends on OF || COMPILE_TEST depends on I2C help Say yes here to build support for the Domintech low-g tri-axial digital accelerometers: DMARD05, DMARD06, DMARD07. To compile this driver as a module, choose M here: the module will be called dmard06. config DMARD09 tristate "Domintech DMARD09 3-axis Accelerometer Driver" depends on I2C help Say yes here to get support for the Domintech DMARD09 3-axis accelerometer. Choosing M will build the driver as a module. If so, the module will be called dmard09. config DMARD10 tristate "Domintech DMARD10 3-axis Accelerometer Driver" depends on I2C help Say yes here to get support for the Domintech DMARD10 3-axis accelerometer. Choosing M will build the driver as a module. If so, the module will be called dmard10. config HID_SENSOR_ACCEL_3D depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID Accelerometers 3D" help Say yes here to build support for the HID SENSOR accelerometers 3D. To compile this driver as a module, choose M here: the module will be called hid-sensor-accel-3d. config IIO_CROS_EC_ACCEL_LEGACY tristate "ChromeOS EC Legacy Accelerometer Sensor" depends on IIO_CROS_EC_SENSORS_CORE help Say yes here to get support for accelerometers on Chromebook using legacy EC firmware. Sensor data is retrieved through IO memory. Newer devices should use IIO_CROS_EC_SENSORS. config IIO_ST_ACCEL_3AXIS tristate "STMicroelectronics accelerometers 3-Axis Driver" depends on (I2C || SPI_MASTER) && SYSFS depends on !SENSORS_LIS3_I2C depends on !SENSORS_LIS3_SPI select IIO_ST_SENSORS_CORE select IIO_ST_ACCEL_I2C_3AXIS if (I2C) select IIO_ST_ACCEL_SPI_3AXIS if (SPI_MASTER) select IIO_TRIGGERED_BUFFER if (IIO_BUFFER) help Say yes here to build support for STMicroelectronics accelerometers: LSM303DLH, LSM303DLHC, LIS3DH, LSM330D, LSM330DL, LSM330DLC, LIS331DLH, LSM303DL, LSM303DLM, LSM330, LIS2DH12, H3LIS331DL, LNG2DM, LIS3DE, LIS2DE12 This driver can also be built as a module. If so, these modules will be created: - st_accel (core functions for the driver [it is mandatory]); - st_accel_i2c (necessary for the I2C devices [optional*]); - st_accel_spi (necessary for the SPI devices [optional*]); (*) one of these is necessary to do something. config IIO_ST_ACCEL_I2C_3AXIS tristate depends on IIO_ST_ACCEL_3AXIS depends on IIO_ST_SENSORS_I2C config IIO_ST_ACCEL_SPI_3AXIS tristate depends on IIO_ST_ACCEL_3AXIS depends on IIO_ST_SENSORS_SPI config KXSD9 tristate "Kionix KXSD9 Accelerometer Driver" select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for the Kionix KXSD9 accelerometer. It can be accessed using an (optional) SPI or I2C interface. To compile this driver as a module, choose M here: the module will be called kxsd9. config KXSD9_SPI tristate "Kionix KXSD9 SPI transport" depends on KXSD9 depends on SPI default KXSD9 select REGMAP_SPI help Say yes here to enable the Kionix KXSD9 accelerometer SPI transport channel. config KXSD9_I2C tristate "Kionix KXSD9 I2C transport" depends on KXSD9 depends on I2C default KXSD9 select REGMAP_I2C help Say yes here to enable the Kionix KXSD9 accelerometer I2C transport channel. config KXCJK1013 tristate "Kionix 3-Axis Accelerometer Driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here if you want to build a driver for the Kionix KXCJK-1013 triaxial acceleration sensor. This driver also supports KXCJ9-1008, KXTJ2-1009 and KXTF9. To compile this driver as a module, choose M here: the module will be called kxcjk-1013. config MC3230 tristate "mCube MC3230 Digital Accelerometer Driver" depends on I2C help Say yes here to build support for the mCube MC3230 low-g tri-axial digital accelerometer. To compile this driver as a module, choose M here: the module will be called mc3230. config MMA7455 tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config MMA7455_I2C tristate "Freescale MMA7455L/MMA7456L Accelerometer I2C Driver" depends on I2C select MMA7455 select REGMAP_I2C help Say yes here to build support for the Freescale MMA7455L and MMA7456L 3-axis accelerometer. To compile this driver as a module, choose M here: the module will be called mma7455_i2c. config MMA7455_SPI tristate "Freescale MMA7455L/MMA7456L Accelerometer SPI Driver" depends on SPI_MASTER select MMA7455 select REGMAP_SPI help Say yes here to build support for the Freescale MMA7455L and MMA7456L 3-axis accelerometer. To compile this driver as a module, choose M here: the module will be called mma7455_spi. config MMA7660 tristate "Freescale MMA7660FC 3-Axis Accelerometer Driver" depends on I2C help Say yes here to get support for the Freescale MMA7660FC 3-Axis accelerometer. Choosing M will build the driver as a module. If so, the module will be called mma7660. config MMA8452 tristate "Freescale / NXP MMA8452Q and similar Accelerometers Driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for the following Freescale / NXP 3-axis accelerometers: MMA8451Q, MMA8452Q, MMA8453Q, MMA8652FC, MMA8653FC, FXLS8471Q. To compile this driver as a module, choose M here: the module will be called mma8452. config MMA9551_CORE tristate config MMA9551 tristate "Freescale MMA9551L Intelligent Motion-Sensing Platform Driver" depends on I2C select MMA9551_CORE help Say yes here to build support for the Freescale MMA9551L Intelligent Motion-Sensing Platform Driver. To compile this driver as a module, choose M here: the module will be called mma9551. config MMA9553 tristate "Freescale MMA9553L Intelligent Pedometer Platform Driver" depends on I2C select MMA9551_CORE help Say yes here to build support for the Freescale MMA9553L Intelligent Pedometer Platform Driver. To compile this driver as a module, choose M here: the module will be called mma9553. config MXC4005 tristate "Memsic MXC4005XC 3-Axis Accelerometer Driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER select REGMAP_I2C help Say yes here to build support for the Memsic MXC4005XC 3-axis accelerometer. To compile this driver as a module, choose M. The module will be called mxc4005. config MXC6255 tristate "Memsic MXC6255 Orientation Sensing Accelerometer Driver" depends on I2C select REGMAP_I2C help Say yes here to build support for the Memsic MXC6255 Orientation Sensing Accelerometer Driver. To compile this driver as a module, choose M here: the module will be called mxc6255. config SCA3000 select IIO_BUFFER select IIO_KFIFO_BUF depends on SPI tristate "VTI SCA3000 series accelerometers" help Say Y here to build support for the VTI SCA3000 series of SPI accelerometers. These devices use a hardware ring buffer. To compile this driver as a module, say M here: the module will be called sca3000. config STK8312 tristate "Sensortek STK8312 3-Axis Accelerometer Driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to get support for the Sensortek STK8312 3-axis accelerometer. Choosing M will build the driver as a module. If so, the module will be called stk8312. config STK8BA50 tristate "Sensortek STK8BA50 3-Axis Accelerometer Driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to get support for the Sensortek STK8BA50 3-axis accelerometer. Choosing M will build the driver as a module. If so, the module will be called stk8ba50. endmenu accel/Makefile 0000644 00000003677 14722071307 0007273 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O accelerometer drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_ADIS16201) += adis16201.o obj-$(CONFIG_ADIS16209) += adis16209.o obj-$(CONFIG_ADXL345) += adxl345_core.o obj-$(CONFIG_ADXL345_I2C) += adxl345_i2c.o obj-$(CONFIG_ADXL345_SPI) += adxl345_spi.o obj-$(CONFIG_ADXL372) += adxl372.o obj-$(CONFIG_ADXL372_I2C) += adxl372_i2c.o obj-$(CONFIG_ADXL372_SPI) += adxl372_spi.o obj-$(CONFIG_BMA180) += bma180.o obj-$(CONFIG_BMA220) += bma220_spi.o obj-$(CONFIG_BMC150_ACCEL) += bmc150-accel-core.o obj-$(CONFIG_BMC150_ACCEL_I2C) += bmc150-accel-i2c.o obj-$(CONFIG_BMC150_ACCEL_SPI) += bmc150-accel-spi.o obj-$(CONFIG_DA280) += da280.o obj-$(CONFIG_DA311) += da311.o obj-$(CONFIG_DMARD06) += dmard06.o obj-$(CONFIG_DMARD09) += dmard09.o obj-$(CONFIG_DMARD10) += dmard10.o obj-$(CONFIG_HID_SENSOR_ACCEL_3D) += hid-sensor-accel-3d.o obj-$(CONFIG_KXCJK1013) += kxcjk-1013.o obj-$(CONFIG_KXSD9) += kxsd9.o obj-$(CONFIG_KXSD9_SPI) += kxsd9-spi.o obj-$(CONFIG_KXSD9_I2C) += kxsd9-i2c.o obj-$(CONFIG_MC3230) += mc3230.o obj-$(CONFIG_MMA7455) += mma7455_core.o obj-$(CONFIG_MMA7455_I2C) += mma7455_i2c.o obj-$(CONFIG_MMA7455_SPI) += mma7455_spi.o obj-$(CONFIG_MMA7660) += mma7660.o obj-$(CONFIG_MMA8452) += mma8452.o obj-$(CONFIG_MMA9551_CORE) += mma9551_core.o obj-$(CONFIG_MMA9551) += mma9551.o obj-$(CONFIG_MMA9553) += mma9553.o obj-$(CONFIG_MXC4005) += mxc4005.o obj-$(CONFIG_MXC6255) += mxc6255.o obj-$(CONFIG_SCA3000) += sca3000.o obj-$(CONFIG_STK8312) += stk8312.o obj-$(CONFIG_STK8BA50) += stk8ba50.o obj-$(CONFIG_IIO_CROS_EC_ACCEL_LEGACY) += cros_ec_accel_legacy.o obj-$(CONFIG_IIO_SSP_SENSORS_COMMONS) += ssp_accel_sensor.o obj-$(CONFIG_IIO_ST_ACCEL_3AXIS) += st_accel.o st_accel-y := st_accel_core.o st_accel-$(CONFIG_IIO_BUFFER) += st_accel_buffer.o obj-$(CONFIG_IIO_ST_ACCEL_I2C_3AXIS) += st_accel_i2c.o obj-$(CONFIG_IIO_ST_ACCEL_SPI_3AXIS) += st_accel_spi.o amplifiers/Kconfig 0000644 00000001320 14722071307 0010201 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Gain Amplifiers, etc. # # When adding new entries keep the list in alphabetical order menu "Amplifiers" config AD8366 tristate "Analog Devices AD8366 and similar Gain Amplifiers" depends on SPI depends on GPIOLIB select BITREVERSE help Say yes here to build support for Analog Devices AD8366 and similar gain amplifiers. This driver supports the following gain amplifiers from Analog Devices: AD8366 Dual-Digital Variable Gain Amplifier (VGA) ADA4961 BiCMOS RF Digital Gain Amplifier (DGA) ADL5240 Digitally controlled variable gain amplifier (VGA) To compile this driver as a module, choose M here: the module will be called ad8366. endmenu amplifiers/Makefile 0000644 00000000246 14722071307 0010344 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile iio/amplifiers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AD8366) += ad8366.o adc/Kconfig 0000644 00000100061 14722071307 0006577 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # ADC drivers # # When adding new entries keep the list in alphabetical order menu "Analog to digital converters" config AD_SIGMA_DELTA tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config AD7124 tristate "Analog Devices AD7124 and similar sigma-delta ADCs driver" depends on SPI_MASTER select AD_SIGMA_DELTA help Say yes here to build support for Analog Devices AD7124-4 and AD7124-8 SPI analog to digital converters (ADC). To compile this driver as a module, choose M here: the module will be called ad7124. config AD7266 tristate "Analog Devices AD7265/AD7266 ADC driver" depends on SPI_MASTER select IIO_BUFFER select IIO_TRIGGER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Analog Devices AD7265 and AD7266 ADCs. To compile this driver as a module, choose M here: the module will be called ad7266. config AD7291 tristate "Analog Devices AD7291 ADC driver" depends on I2C help Say yes here to build support for Analog Devices AD7291 8 Channel ADC with temperature sensor. To compile this driver as a module, choose M here: the module will be called ad7291. config AD7298 tristate "Analog Devices AD7298 ADC driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Analog Devices AD7298 8 Channel ADC with temperature sensor. To compile this driver as a module, choose M here: the module will be called ad7298. config AD7476 tristate "Analog Devices AD7476 1-channel ADCs driver and other similar devices from AD an TI" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for the following SPI analog to digital converters (ADCs): Analog Devices: AD7273, AD7274, AD7276, AD7277, AD7278, AD7475, AD7476, AD7477, AD7478, AD7466, AD7467, AD7468, AD7495, AD7910, AD7920. Texas Instruments: ADS7866, ADS7867, ADS7868. To compile this driver as a module, choose M here: the module will be called ad7476. config AD7606 tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config AD7606_IFACE_PARALLEL tristate "Analog Devices AD7606 ADC driver with parallel interface support" depends on HAS_IOMEM select AD7606 help Say yes here to build parallel interface support for Analog Devices: ad7605-4, ad7606, ad7606-6, ad7606-4 analog to digital converters (ADC). To compile this driver as a module, choose M here: the module will be called ad7606_parallel. config AD7606_IFACE_SPI tristate "Analog Devices AD7606 ADC driver with spi interface support" depends on SPI select AD7606 help Say yes here to build spi interface support for Analog Devices: ad7605-4, ad7606, ad7606-6, ad7606-4 analog to digital converters (ADC). To compile this driver as a module, choose M here: the module will be called ad7606_spi. config AD7766 tristate "Analog Devices AD7766/AD7767 ADC driver" depends on SPI_MASTER select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Analog Devices AD7766, AD7766-1, AD7766-2, AD7767, AD7767-1, AD7767-2 SPI analog to digital converters. To compile this driver as a module, choose M here: the module will be called ad7766. config AD7768_1 tristate "Analog Devices AD7768-1 ADC driver" depends on SPI select IIO_BUFFER select IIO_TRIGGER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Analog Devices AD7768-1 SPI simultaneously sampling sigma-delta analog to digital converter (ADC). To compile this driver as a module, choose M here: the module will be called ad7768-1. config AD7780 tristate "Analog Devices AD7780 and similar ADCs driver" depends on SPI depends on GPIOLIB || COMPILE_TEST select AD_SIGMA_DELTA help Say yes here to build support for Analog Devices AD7170, AD7171, AD7780 and AD7781 SPI analog to digital converters (ADC). To compile this driver as a module, choose M here: the module will be called ad7780. config AD7791 tristate "Analog Devices AD7791 ADC driver" depends on SPI select AD_SIGMA_DELTA help Say yes here to build support for Analog Devices AD7787, AD7788, AD7789, AD7790 and AD7791 SPI analog to digital converters (ADC). To compile this driver as a module, choose M here: the module will be called ad7791. config AD7793 tristate "Analog Devices AD7793 and similar ADCs driver" depends on SPI select AD_SIGMA_DELTA help Say yes here to build support for Analog Devices AD7785, AD7792, AD7793, AD7794 and AD7795 SPI analog to digital converters (ADC). To compile this driver as a module, choose M here: the module will be called AD7793. config AD7887 tristate "Analog Devices AD7887 ADC driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Analog Devices AD7887 SPI analog to digital converter (ADC). To compile this driver as a module, choose M here: the module will be called ad7887. config AD7923 tristate "Analog Devices AD7923 and similar ADCs driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Analog Devices AD7904, AD7914, AD7923, AD7924 4 Channel ADCs. To compile this driver as a module, choose M here: the module will be called ad7923. config AD7949 tristate "Analog Devices AD7949 and similar ADCs driver" depends on SPI help Say yes here to build support for Analog Devices AD7949, AD7682, AD7689 8 Channel ADCs. To compile this driver as a module, choose M here: the module will be called ad7949. config AD799X tristate "Analog Devices AD799x ADC driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Analog Devices: ad7991, ad7995, ad7999, ad7992, ad7993, ad7994, ad7997, ad7998 i2c analog to digital converters (ADC). Provides direct access via sysfs. To compile this driver as a module, choose M here: the module will be called ad799x. config ASPEED_ADC tristate "Aspeed ADC" depends on ARCH_ASPEED || COMPILE_TEST depends on COMMON_CLK help If you say yes here you get support for the ADC included in Aspeed BMC SoCs. To compile this driver as a module, choose M here: the module will be called aspeed_adc. config AT91_ADC tristate "Atmel AT91 ADC" depends on ARCH_AT91 depends on INPUT && SYSFS select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Atmel AT91 ADC. To compile this driver as a module, choose M here: the module will be called at91_adc. config AT91_SAMA5D2_ADC tristate "Atmel AT91 SAMA5D2 ADC" depends on ARCH_AT91 || COMPILE_TEST depends on HAS_IOMEM select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Atmel SAMA5D2 ADC which is available on SAMA5D2 SoC family. To compile this driver as a module, choose M here: the module will be called at91-sama5d2_adc. config AXP20X_ADC tristate "X-Powers AXP20X and AXP22X ADC driver" depends on MFD_AXP20X help Say yes here to have support for X-Powers power management IC (PMIC) AXP20X and AXP22X ADC devices. To compile this driver as a module, choose M here: the module will be called axp20x_adc. config AXP288_ADC tristate "X-Powers AXP288 ADC driver" depends on MFD_AXP20X help Say yes here to have support for X-Powers power management IC (PMIC) ADC device. Depending on platform configuration, this general purpose ADC can be used for sampling sensors such as thermal resistors. To compile this driver as a module, choose M here: the module will be called axp288_adc. config BCM_IPROC_ADC tristate "Broadcom IPROC ADC driver" depends on ARCH_BCM_IPROC || COMPILE_TEST depends on MFD_SYSCON default ARCH_BCM_CYGNUS help Say Y here if you want to add support for the Broadcom static ADC driver. Broadcom iProc ADC driver. Broadcom iProc ADC controller has 8 channels. The driver allows the user to read voltage values. config BERLIN2_ADC tristate "Marvell Berlin2 ADC driver" depends on ARCH_BERLIN help Marvell Berlin2 ADC driver. This ADC has 8 channels, with one used for temperature measurement. config CC10001_ADC tristate "Cosmic Circuits 10001 ADC driver" depends on HAS_IOMEM && HAVE_CLK && REGULATOR select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Cosmic Circuits 10001 ADC. This driver can also be built as a module. If so, the module will be called cc10001_adc. config CPCAP_ADC tristate "Motorola CPCAP PMIC ADC driver" depends on MFD_CPCAP select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Motorola CPCAP PMIC ADC. This driver can also be built as a module. If so, the module will be called cpcap-adc. config DA9150_GPADC tristate "Dialog DA9150 GPADC driver support" depends on MFD_DA9150 help Say yes here to build support for Dialog DA9150 GPADC. This driver can also be built as a module. If chosen, the module name will be da9150-gpadc. To compile this driver as a module, choose M here: the module will be called berlin2-adc. config DLN2_ADC tristate "Diolan DLN-2 ADC driver support" depends on MFD_DLN2 select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Diolan DLN-2 ADC. This driver can also be built as a module. If so, the module will be called adc_dln2. config ENVELOPE_DETECTOR tristate "Envelope detector using a DAC and a comparator" depends on OF help Say yes here to build support for an envelope detector using a DAC and a comparator. To compile this driver as a module, choose M here: the module will be called envelope-detector. config EP93XX_ADC tristate "Cirrus Logic EP93XX ADC driver" depends on ARCH_EP93XX help Driver for the ADC module on the EP93XX series of SoC from Cirrus Logic. It's recommended to switch on CONFIG_HIGH_RES_TIMERS option, in this case driver will reduce its CPU usage by 90% in some use cases. To compile this driver as a module, choose M here: the module will be called ep93xx_adc. config EXYNOS_ADC tristate "Exynos ADC driver support" depends on ARCH_EXYNOS || ARCH_S3C24XX || ARCH_S3C64XX || ARCH_S5PV210 || (OF && COMPILE_TEST) depends on HAS_IOMEM help Core support for the ADC block found in the Samsung EXYNOS series of SoCs for drivers such as the touchscreen and hwmon to use to share this resource. To compile this driver as a module, choose M here: the module will be called exynos_adc. config MXS_LRADC_ADC tristate "Freescale i.MX23/i.MX28 LRADC ADC" depends on MFD_MXS_LRADC select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for the ADC functions of the i.MX23/i.MX28 LRADC. This includes general-purpose ADC readings, battery voltage measurement, and die temperature measurement. This driver can also be built as a module. If so, the module will be called mxs-lradc-adc. config FSL_MX25_ADC tristate "Freescale MX25 ADC driver" depends on MFD_MX25_TSADC help Generic Conversion Queue driver used for general purpose ADC in the MX25. This driver supports single measurements using the MX25 ADC. config HI8435 tristate "Holt Integrated Circuits HI-8435 threshold detector" select IIO_TRIGGERED_EVENT depends on SPI help If you say yes here you get support for Holt Integrated Circuits HI-8435 chip. This driver can also be built as a module. If so, the module will be called hi8435. config HX711 tristate "AVIA HX711 ADC for weight cells" depends on GPIOLIB select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for AVIA HX711 ADC which is used for weigh cells This driver uses two GPIOs, one acts as the clock and controls the channel selection and gain, the other one is used for the measurement data Currently the raw value is read from the chip and delivered. To get an actual weight one needs to subtract the zero offset and multiply by a scale factor. This should be done in userspace. This driver can also be built as a module. If so, the module will be called hx711. config INA2XX_ADC tristate "Texas Instruments INA2xx Power Monitors IIO driver" depends on I2C && !SENSORS_INA2XX select REGMAP_I2C select IIO_BUFFER select IIO_KFIFO_BUF help Say yes here to build support for TI INA2xx family of Power Monitors. This driver is mutually exclusive with the HWMON version. config INGENIC_ADC tristate "Ingenic JZ47xx SoCs ADC driver" depends on MIPS || COMPILE_TEST help Say yes here to build support for the Ingenic JZ47xx SoCs ADC unit. This driver can also be built as a module. If so, the module will be called ingenic_adc. config IMX7D_ADC tristate "Freescale IMX7D ADC driver" depends on ARCH_MXC || COMPILE_TEST depends on HAS_IOMEM help Say yes here to build support for IMX7D ADC. This driver can also be built as a module. If so, the module will be called imx7d_adc. config LP8788_ADC tristate "LP8788 ADC driver" depends on MFD_LP8788 help Say yes here to build support for TI LP8788 ADC. To compile this driver as a module, choose M here: the module will be called lp8788_adc. config LPC18XX_ADC tristate "NXP LPC18xx ADC driver" depends on ARCH_LPC18XX || COMPILE_TEST depends on OF && HAS_IOMEM help Say yes here to build support for NXP LPC18XX ADC. To compile this driver as a module, choose M here: the module will be called lpc18xx_adc. config LPC32XX_ADC tristate "NXP LPC32XX ADC" depends on ARCH_LPC32XX || COMPILE_TEST depends on HAS_IOMEM help Say yes here to build support for the integrated ADC inside the LPC32XX SoC. Note that this feature uses the same hardware as the touchscreen driver, so you should either select only one of the two drivers (lpc32xx_adc or lpc32xx_ts) or, in the OpenFirmware case, activate only one via device tree selection. Provides direct access via sysfs. config LTC2471 tristate "Linear Technology LTC2471 and LTC2473 ADC driver" depends on I2C help Say yes here to build support for Linear Technology LTC2471 and LTC2473 16-bit I2C ADC. This driver can also be built as a module. If so, the module will be called ltc2471. config LTC2485 tristate "Linear Technology LTC2485 ADC driver" depends on I2C help Say yes here to build support for Linear Technology LTC2485 ADC. To compile this driver as a module, choose M here: the module will be called ltc2485. config LTC2497 tristate "Linear Technology LTC2497 ADC driver" depends on I2C help Say yes here to build support for Linear Technology LTC2497 16-Bit 8-/16-Channel Delta Sigma ADC. To compile this driver as a module, choose M here: the module will be called ltc2497. config MAX1027 tristate "Maxim max1027 ADC driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Maxim SPI ADC models max1027, max1029 and max1031. To compile this driver as a module, choose M here: the module will be called max1027. config MAX11100 tristate "Maxim max11100 ADC driver" depends on SPI_MASTER help Say yes here to build support for Maxim max11100 SPI ADC To compile this driver as a module, choose M here: the module will be called max11100. config MAX1118 tristate "Maxim max1117/max1118/max1119 ADCs driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Maxim max1117/max1118/max1119 8-bit, dual-channel ADCs. To compile this driver as a module, choose M here: the module will be called max1118. config MAX1363 tristate "Maxim max1363 ADC driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for many Maxim i2c analog to digital converters (ADC). (max1361, max1362, max1363, max1364, max1036, max1037, max1038, max1039, max1136, max1136, max1137, max1138, max1139, max1236, max1237, max11238, max1239, max11600, max11601, max11602, max11603, max11604, max11605, max11606, max11607, max11608, max11609, max11610, max11611, max11612, max11613, max11614, max11615, max11616, max11617, max11644, max11645, max11646, max11647) Provides direct access via sysfs and buffered data via the iio dev interface. To compile this driver as a module, choose M here: the module will be called max1363. config MAX9611 tristate "Maxim max9611/max9612 ADC driver" depends on I2C help Say yes here to build support for Maxim max9611/max9612 current sense amplifier with 12-bits ADC interface. To compile this driver as a module, choose M here: the module will be called max9611. config MCP320X tristate "Microchip Technology MCP3x01/02/04/08 and MCP3550/1/3" depends on SPI help Say yes here to build support for Microchip Technology's MCP3001, MCP3002, MCP3004, MCP3008, MCP3201, MCP3202, MCP3204, MCP3208, MCP3301, MCP3550, MCP3551 and MCP3553 analog to digital converters. This driver can also be built as a module. If so, the module will be called mcp320x. config MCP3422 tristate "Microchip Technology MCP3421/2/3/4/5/6/7/8 driver" depends on I2C help Say yes here to build support for Microchip Technology's MCP3421 MCP3422, MCP3423, MCP3424, MCP3425, MCP3426, MCP3427 or MCP3428 analog to digital converters. This driver can also be built as a module. If so, the module will be called mcp3422. config MCP3911 tristate "Microchip Technology MCP3911 driver" depends on SPI help Say yes here to build support for Microchip Technology's MCP3911 analog to digital converter. This driver can also be built as a module. If so, the module will be called mcp3911. config MEDIATEK_MT6577_AUXADC tristate "MediaTek AUXADC driver" depends on ARCH_MEDIATEK || COMPILE_TEST depends on HAS_IOMEM help Say yes here to enable support for MediaTek mt65xx AUXADC. The driver supports immediate mode operation to read from one of sixteen channels (external or internal). This driver can also be built as a module. If so, the module will be called mt6577_auxadc. config MEN_Z188_ADC tristate "MEN 16z188 ADC IP Core support" depends on MCB help Say yes here to enable support for the MEN 16z188 ADC IP-Core on a MCB carrier. This driver can also be built as a module. If so, the module will be called men_z188_adc. config MESON_SARADC tristate "Amlogic Meson SAR ADC driver" default ARCH_MESON depends on OF && COMMON_CLK && (ARCH_MESON || COMPILE_TEST) select REGMAP_MMIO help Say yes here to build support for the SAR ADC found in Amlogic Meson SoCs. To compile this driver as a module, choose M here: the module will be called meson_saradc. config NAU7802 tristate "Nuvoton NAU7802 ADC driver" depends on I2C help Say yes here to build support for Nuvoton NAU7802 ADC. To compile this driver as a module, choose M here: the module will be called nau7802. config NPCM_ADC tristate "Nuvoton NPCM ADC driver" depends on ARCH_NPCM || COMPILE_TEST depends on HAS_IOMEM help Say yes here to build support for Nuvoton NPCM ADC. This driver can also be built as a module. If so, the module will be called npcm_adc. config PALMAS_GPADC tristate "TI Palmas General Purpose ADC" depends on MFD_PALMAS help Palmas series pmic chip by Texas Instruments (twl6035/6037) is used in smartphones and tablets and supports a 16 channel general purpose ADC. config QCOM_VADC_COMMON tristate config QCOM_PM8XXX_XOADC tristate "Qualcomm SSBI PM8xxx PMIC XOADCs" depends on MFD_PM8XXX select QCOM_VADC_COMMON help ADC driver for the XOADC portions of the Qualcomm PM8xxx PMICs using SSBI transport: PM8018, PM8038, PM8058, PM8921. To compile this driver as a module, choose M here: the module will be called qcom-pm8xxx-xoadc. config QCOM_SPMI_IADC tristate "Qualcomm SPMI PMIC current ADC" depends on SPMI select REGMAP_SPMI help This is the IIO Current ADC driver for Qualcomm QPNP IADC Chip. The driver supports single mode operation to read from one of two channels (external or internal). Hardware have additional channels internally used for gain and offset calibration. To compile this driver as a module, choose M here: the module will be called qcom-spmi-iadc. config QCOM_SPMI_VADC tristate "Qualcomm SPMI PMIC voltage ADC" depends on SPMI select REGMAP_SPMI select QCOM_VADC_COMMON help This is the IIO Voltage ADC driver for Qualcomm QPNP VADC Chip. The driver supports multiple channels read. The VADC is a 15-bit sigma-delta ADC. Some of the channels are internally used for calibration. To compile this driver as a module, choose M here: the module will be called qcom-spmi-vadc. config QCOM_SPMI_ADC5 tristate "Qualcomm Technologies Inc. SPMI PMIC5 ADC" depends on SPMI select REGMAP_SPMI select QCOM_VADC_COMMON help This is the IIO Voltage PMIC5 ADC driver for Qualcomm Technologies Inc. The driver supports multiple channels read. The ADC is a 16-bit sigma-delta ADC. The hardware supports calibrated results for conversion requests and clients include reading voltage phone power, on board system thermistors connected to the PMIC ADC, PMIC die temperature, charger temperature, battery current, USB voltage input, voltage signals connected to supported PMIC GPIO inputs. The hardware supports internal pull-up for thermistors and can choose between a 100k, 30k and 400k pull up using the ADC channels. To compile this driver as a module, choose M here: the module will be called qcom-spmi-adc5. config RCAR_GYRO_ADC tristate "Renesas R-Car GyroADC driver" depends on ARCH_RCAR_GEN2 || COMPILE_TEST help Say yes here to build support for the GyroADC found in Renesas R-Car Gen2 SoCs. This block is a simple SPI offload engine for reading data out of attached compatible ADCs in a round-robin fashion. Up to 4 or 8 ADC channels are supported by this block, depending on which ADCs are attached. To compile this driver as a module, choose M here: the module will be called rcar-gyroadc. config ROCKCHIP_SARADC tristate "Rockchip SARADC driver" depends on ARCH_ROCKCHIP || (ARM && COMPILE_TEST) depends on RESET_CONTROLLER help Say yes here to build support for the SARADC found in SoCs from Rockchip. To compile this driver as a module, choose M here: the module will be called rockchip_saradc. config SC27XX_ADC tristate "Spreadtrum SC27xx series PMICs ADC" depends on MFD_SC27XX_PMIC || COMPILE_TEST help Say yes here to build support for the integrated ADC inside the Spreadtrum SC27xx series PMICs. This driver can also be built as a module. If so, the module will be called sc27xx_adc. config SPEAR_ADC tristate "ST SPEAr ADC" depends on PLAT_SPEAR || COMPILE_TEST depends on HAS_IOMEM help Say yes here to build support for the integrated ADC inside the ST SPEAr SoC. Provides direct access via sysfs. To compile this driver as a module, choose M here: the module will be called spear_adc. config SD_ADC_MODULATOR tristate "Generic sigma delta modulator" depends on OF select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Select this option to enables sigma delta modulator. This driver can support generic sigma delta modulators. This driver can also be built as a module. If so, the module will be called sd_adc_modulator. config STM32_ADC_CORE tristate "STMicroelectronics STM32 adc core" depends on ARCH_STM32 || COMPILE_TEST depends on OF depends on REGULATOR depends on HAS_IOMEM select IIO_BUFFER select MFD_STM32_TIMERS select IIO_STM32_TIMER_TRIGGER select IIO_TRIGGERED_BUFFER help Select this option to enable the core driver for STMicroelectronics STM32 analog-to-digital converter (ADC). This driver can also be built as a module. If so, the module will be called stm32-adc-core. config STM32_ADC tristate "STMicroelectronics STM32 adc" depends on STM32_ADC_CORE help Say yes here to build support for STMicroelectronics stm32 Analog to Digital Converter (ADC). This driver can also be built as a module. If so, the module will be called stm32-adc. config STM32_DFSDM_CORE tristate "STMicroelectronics STM32 DFSDM core" depends on (ARCH_STM32 && OF) || COMPILE_TEST select REGMAP select REGMAP_MMIO help Select this option to enable the driver for STMicroelectronics STM32 digital filter for sigma delta converter. This driver can also be built as a module. If so, the module will be called stm32-dfsdm-core. config STM32_DFSDM_ADC tristate "STMicroelectronics STM32 dfsdm adc" depends on (ARCH_STM32 && OF) || COMPILE_TEST select STM32_DFSDM_CORE select REGMAP_MMIO select IIO_BUFFER select IIO_BUFFER_HW_CONSUMER select IIO_TRIGGERED_BUFFER help Select this option to support ADCSigma delta modulator for STMicroelectronics STM32 digital filter for sigma delta converter. This driver can also be built as a module. If so, the module will be called stm32-dfsdm-adc. config STMPE_ADC tristate "STMicroelectronics STMPE ADC driver" depends on OF && MFD_STMPE help Say yes here to build support for ST Microelectronics STMPE built-in ADC block (stmpe811). config SUN4I_GPADC tristate "Support for the Allwinner SoCs GPADC" depends on IIO depends on MFD_SUN4I_GPADC || MACH_SUN8I depends on THERMAL || !THERMAL_OF select REGMAP_IRQ help Say yes here to build support for Allwinner (A10, A13 and A31) SoCs GPADC. This ADC provides 4 channels which can be used as an ADC or as a touchscreen input and one channel for thermal sensor. The thermal sensor slows down ADC readings and can be disabled by disabling CONFIG_THERMAL_OF. However, the thermal sensor should be enabled by default since the SoC temperature is usually more critical than ADC readings. To compile this driver as a module, choose M here: the module will be called sun4i-gpadc-iio. config TI_ADC081C tristate "Texas Instruments ADC081C/ADC101C/ADC121C family" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for Texas Instruments ADC081C, ADC101C and ADC121C ADC chips. This driver can also be built as a module. If so, the module will be called ti-adc081c. config TI_ADC0832 tristate "Texas Instruments ADC0831/ADC0832/ADC0834/ADC0838" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for Texas Instruments ADC0831, ADC0832, ADC0834, ADC0838 ADC chips. This driver can also be built as a module. If so, the module will be called ti-adc0832. config TI_ADC084S021 tristate "Texas Instruments ADC084S021" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for Texas Instruments ADC084S021 chips. This driver can also be built as a module. If so, the module will be called ti-adc084s021. config TI_ADC12138 tristate "Texas Instruments ADC12130/ADC12132/ADC12138" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for Texas Instruments ADC12130, ADC12132 and ADC12138 chips. This driver can also be built as a module. If so, the module will be called ti-adc12138. config TI_ADC108S102 tristate "Texas Instruments ADC108S102 and ADC128S102 driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Texas Instruments ADC108S102 and ADC128S102 ADC. To compile this driver as a module, choose M here: the module will be called ti-adc108s102. config TI_ADC128S052 tristate "Texas Instruments ADC128S052/ADC122S021/ADC124S021" depends on SPI help If you say yes here you get support for Texas Instruments ADC128S052, ADC122S021 and ADC124S021 chips. This driver can also be built as a module. If so, the module will be called ti-adc128s052. config TI_ADC161S626 tristate "Texas Instruments ADC161S626 1-channel differential ADC" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for Texas Instruments ADC141S626, and ADC161S626 chips. This driver can also be built as a module. If so, the module will be called ti-adc161s626. config TI_ADS1015 tristate "Texas Instruments ADS1015 ADC" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for Texas Instruments ADS1015 ADC chip. This driver can also be built as a module. If so, the module will be called ti-ads1015. config TI_ADS7950 tristate "Texas Instruments ADS7950 ADC driver" depends on SPI && GPIOLIB select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Texas Instruments ADS7950, ADS7951, ADS7952, ADS7953, ADS7954, ADS7955, ADS7956, ADS7957, ADS7958, ADS7959. ADS7960, ADS7961. To compile this driver as a module, choose M here: the module will be called ti-ads7950. config TI_ADS8344 tristate "Texas Instruments ADS8344" depends on SPI && OF help If you say yes here you get support for Texas Instruments ADS8344 ADC chips This driver can also be built as a module. If so, the module will be called ti-ads8344. config TI_ADS8688 tristate "Texas Instruments ADS8688" depends on SPI && OF help If you say yes here you get support for Texas Instruments ADS8684 and and ADS8688 ADC chips This driver can also be built as a module. If so, the module will be called ti-ads8688. config TI_ADS124S08 tristate "Texas Instruments ADS124S08" depends on SPI && OF help If you say yes here you get support for Texas Instruments ADS124S08 and ADS124S06 ADC chips This driver can also be built as a module. If so, the module will be called ti-ads124s08. config TI_AM335X_ADC tristate "TI's AM335X ADC driver" depends on MFD_TI_AM335X_TSCADC && HAS_DMA select IIO_BUFFER select IIO_KFIFO_BUF help Say yes here to build support for Texas Instruments ADC driver which is also a MFD client. To compile this driver as a module, choose M here: the module will be called ti_am335x_adc. config TI_TLC4541 tristate "Texas Instruments TLC4541 ADC driver" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Texas Instruments TLC4541 / TLC3541 ADC chips. This driver can also be built as a module. If so, the module will be called ti-tlc4541. config TWL4030_MADC tristate "TWL4030 MADC (Monitoring A/D Converter)" depends on TWL4030_CORE help This driver provides support for Triton TWL4030-MADC. The driver supports both RT and SW conversion methods. This driver can also be built as a module. If so, the module will be called twl4030-madc. config TWL6030_GPADC tristate "TWL6030 GPADC (General Purpose A/D Converter) Support" depends on TWL4030_CORE default n help Say yes here if you want support for the TWL6030/TWL6032 General Purpose A/D Converter. This will add support for battery type detection, battery voltage and temperature measurement, die temperature measurement, system supply voltage, audio accessory, USB ID detection. This driver can also be built as a module. If so, the module will be called twl6030-gpadc. config VF610_ADC tristate "Freescale vf610 ADC driver" depends on OF depends on HAS_IOMEM select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to support for Vybrid board analog-to-digital converter. Since the IP is used for i.MX6SLX, the driver also support i.MX6SLX. This driver can also be built as a module. If so, the module will be called vf610_adc. config VIPERBOARD_ADC tristate "Viperboard ADC support" depends on MFD_VIPERBOARD && USB help Say yes here to access the ADC part of the Nano River Technologies Viperboard. To compile this driver as a module, choose M here: the module will be called viperboard_adc. config XILINX_XADC tristate "Xilinx XADC driver" depends on HAS_IOMEM select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to have support for the Xilinx XADC. The driver does support both the ZYNQ interface to the XADC as well as the AXI-XADC interface. The driver can also be build as a module. If so, the module will be called xilinx-xadc. endmenu adc/Makefile 0000644 00000007776 14722071307 0006757 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for IIO ADC drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AD_SIGMA_DELTA) += ad_sigma_delta.o obj-$(CONFIG_AD7124) += ad7124.o obj-$(CONFIG_AD7266) += ad7266.o obj-$(CONFIG_AD7291) += ad7291.o obj-$(CONFIG_AD7298) += ad7298.o obj-$(CONFIG_AD7923) += ad7923.o obj-$(CONFIG_AD7476) += ad7476.o obj-$(CONFIG_AD7606_IFACE_PARALLEL) += ad7606_par.o obj-$(CONFIG_AD7606_IFACE_SPI) += ad7606_spi.o obj-$(CONFIG_AD7606) += ad7606.o obj-$(CONFIG_AD7766) += ad7766.o obj-$(CONFIG_AD7768_1) += ad7768-1.o obj-$(CONFIG_AD7780) += ad7780.o obj-$(CONFIG_AD7791) += ad7791.o obj-$(CONFIG_AD7793) += ad7793.o obj-$(CONFIG_AD7887) += ad7887.o obj-$(CONFIG_AD7949) += ad7949.o obj-$(CONFIG_AD799X) += ad799x.o obj-$(CONFIG_ASPEED_ADC) += aspeed_adc.o obj-$(CONFIG_AT91_ADC) += at91_adc.o obj-$(CONFIG_AT91_SAMA5D2_ADC) += at91-sama5d2_adc.o obj-$(CONFIG_AXP20X_ADC) += axp20x_adc.o obj-$(CONFIG_AXP288_ADC) += axp288_adc.o obj-$(CONFIG_BCM_IPROC_ADC) += bcm_iproc_adc.o obj-$(CONFIG_BERLIN2_ADC) += berlin2-adc.o obj-$(CONFIG_CC10001_ADC) += cc10001_adc.o obj-$(CONFIG_CPCAP_ADC) += cpcap-adc.o obj-$(CONFIG_DA9150_GPADC) += da9150-gpadc.o obj-$(CONFIG_DLN2_ADC) += dln2-adc.o obj-$(CONFIG_ENVELOPE_DETECTOR) += envelope-detector.o obj-$(CONFIG_EP93XX_ADC) += ep93xx_adc.o obj-$(CONFIG_EXYNOS_ADC) += exynos_adc.o obj-$(CONFIG_FSL_MX25_ADC) += fsl-imx25-gcq.o obj-$(CONFIG_HI8435) += hi8435.o obj-$(CONFIG_HX711) += hx711.o obj-$(CONFIG_IMX7D_ADC) += imx7d_adc.o obj-$(CONFIG_INA2XX_ADC) += ina2xx-adc.o obj-$(CONFIG_INGENIC_ADC) += ingenic-adc.o obj-$(CONFIG_LP8788_ADC) += lp8788_adc.o obj-$(CONFIG_LPC18XX_ADC) += lpc18xx_adc.o obj-$(CONFIG_LPC32XX_ADC) += lpc32xx_adc.o obj-$(CONFIG_LTC2471) += ltc2471.o obj-$(CONFIG_LTC2485) += ltc2485.o obj-$(CONFIG_LTC2497) += ltc2497.o obj-$(CONFIG_MAX1027) += max1027.o obj-$(CONFIG_MAX11100) += max11100.o obj-$(CONFIG_MAX1118) += max1118.o obj-$(CONFIG_MAX1363) += max1363.o obj-$(CONFIG_MAX9611) += max9611.o obj-$(CONFIG_MCP320X) += mcp320x.o obj-$(CONFIG_MCP3422) += mcp3422.o obj-$(CONFIG_MCP3911) += mcp3911.o obj-$(CONFIG_MEDIATEK_MT6577_AUXADC) += mt6577_auxadc.o obj-$(CONFIG_MEN_Z188_ADC) += men_z188_adc.o obj-$(CONFIG_MESON_SARADC) += meson_saradc.o obj-$(CONFIG_MXS_LRADC_ADC) += mxs-lradc-adc.o obj-$(CONFIG_NAU7802) += nau7802.o obj-$(CONFIG_NPCM_ADC) += npcm_adc.o obj-$(CONFIG_PALMAS_GPADC) += palmas_gpadc.o obj-$(CONFIG_QCOM_SPMI_ADC5) += qcom-spmi-adc5.o obj-$(CONFIG_QCOM_SPMI_IADC) += qcom-spmi-iadc.o obj-$(CONFIG_QCOM_VADC_COMMON) += qcom-vadc-common.o obj-$(CONFIG_QCOM_SPMI_VADC) += qcom-spmi-vadc.o obj-$(CONFIG_QCOM_PM8XXX_XOADC) += qcom-pm8xxx-xoadc.o obj-$(CONFIG_RCAR_GYRO_ADC) += rcar-gyroadc.o obj-$(CONFIG_ROCKCHIP_SARADC) += rockchip_saradc.o obj-$(CONFIG_SC27XX_ADC) += sc27xx_adc.o obj-$(CONFIG_SPEAR_ADC) += spear_adc.o obj-$(CONFIG_SUN4I_GPADC) += sun4i-gpadc-iio.o obj-$(CONFIG_STM32_ADC_CORE) += stm32-adc-core.o obj-$(CONFIG_STM32_ADC) += stm32-adc.o obj-$(CONFIG_STM32_DFSDM_CORE) += stm32-dfsdm-core.o obj-$(CONFIG_STM32_DFSDM_ADC) += stm32-dfsdm-adc.o obj-$(CONFIG_STMPE_ADC) += stmpe-adc.o obj-$(CONFIG_TI_ADC081C) += ti-adc081c.o obj-$(CONFIG_TI_ADC0832) += ti-adc0832.o obj-$(CONFIG_TI_ADC084S021) += ti-adc084s021.o obj-$(CONFIG_TI_ADC12138) += ti-adc12138.o obj-$(CONFIG_TI_ADC108S102) += ti-adc108s102.o obj-$(CONFIG_TI_ADC128S052) += ti-adc128s052.o obj-$(CONFIG_TI_ADC161S626) += ti-adc161s626.o obj-$(CONFIG_TI_ADS1015) += ti-ads1015.o obj-$(CONFIG_TI_ADS7950) += ti-ads7950.o obj-$(CONFIG_TI_ADS8344) += ti-ads8344.o obj-$(CONFIG_TI_ADS8688) += ti-ads8688.o obj-$(CONFIG_TI_ADS124S08) += ti-ads124s08.o obj-$(CONFIG_TI_AM335X_ADC) += ti_am335x_adc.o obj-$(CONFIG_TI_TLC4541) += ti-tlc4541.o obj-$(CONFIG_TWL4030_MADC) += twl4030-madc.o obj-$(CONFIG_TWL6030_GPADC) += twl6030-gpadc.o obj-$(CONFIG_VF610_ADC) += vf610_adc.o obj-$(CONFIG_VIPERBOARD_ADC) += viperboard_adc.o xilinx-xadc-y := xilinx-xadc-core.o xilinx-xadc-events.o obj-$(CONFIG_XILINX_XADC) += xilinx-xadc.o obj-$(CONFIG_SD_ADC_MODULATOR) += sd_adc_modulator.o Kconfig 0000644 00000005521 14722071307 0006055 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Industrial I/O subsystem configuration # menuconfig IIO tristate "Industrial I/O support" help The industrial I/O subsystem provides a unified framework for drivers for many different types of embedded sensors using a number of different physical interfaces (i2c, spi, etc). if IIO config IIO_BUFFER bool "Enable buffer support within IIO" help Provide core support for various buffer based data acquisition methods. if IIO_BUFFER source "drivers/iio/buffer/Kconfig" endif # IIO_BUFFER config IIO_CONFIGFS tristate "Enable IIO configuration via configfs" select CONFIGFS_FS help This allows configuring various IIO bits through configfs (e.g. software triggers). For more info see Documentation/iio/iio_configfs.rst. config IIO_TRIGGER bool "Enable triggered sampling support" help Provides IIO core support for triggers. Currently these are used to initialize capture of samples to push into buffers. The triggers are effectively a 'capture data now' interrupt. config IIO_CONSUMERS_PER_TRIGGER int "Maximum number of consumers per trigger" depends on IIO_TRIGGER default "2" help This value controls the maximum number of consumers that a given trigger may handle. Default is 2. config IIO_SW_DEVICE tristate "Enable software IIO device support" select IIO_CONFIGFS help Provides IIO core support for software devices. A software device can be created via configfs or directly by a driver using the API provided. config IIO_SW_TRIGGER tristate "Enable software triggers support" select IIO_CONFIGFS help Provides IIO core support for software triggers. A software trigger can be created via configfs or directly by a driver using the API provided. config IIO_TRIGGERED_EVENT tristate select IIO_TRIGGER help Provides helper functions for setting up triggered events. source "drivers/iio/accel/Kconfig" source "drivers/iio/adc/Kconfig" source "drivers/iio/addac/Kconfig" source "drivers/iio/afe/Kconfig" source "drivers/iio/amplifiers/Kconfig" source "drivers/iio/chemical/Kconfig" source "drivers/iio/common/Kconfig" source "drivers/iio/dac/Kconfig" source "drivers/iio/dummy/Kconfig" source "drivers/iio/frequency/Kconfig" source "drivers/iio/gyro/Kconfig" source "drivers/iio/health/Kconfig" source "drivers/iio/humidity/Kconfig" source "drivers/iio/imu/Kconfig" source "drivers/iio/light/Kconfig" source "drivers/iio/magnetometer/Kconfig" source "drivers/iio/multiplexer/Kconfig" source "drivers/iio/orientation/Kconfig" if IIO_TRIGGER source "drivers/iio/trigger/Kconfig" endif #IIO_TRIGGER source "drivers/iio/potentiometer/Kconfig" source "drivers/iio/potentiostat/Kconfig" source "drivers/iio/pressure/Kconfig" source "drivers/iio/proximity/Kconfig" source "drivers/iio/resolver/Kconfig" source "drivers/iio/temperature/Kconfig" endif # IIO addac/Kconfig 0000644 00000001260 14722071307 0007105 0 ustar 00 # # ADC DAC drivers # # When adding new entries keep the list in alphabetical order menu "Analog to digital and digital to analog converters" config STX104 tristate "Apex Embedded Systems STX104 driver" depends on PC104 && X86 select ISA_BUS_API select GPIOLIB help Say yes here to build support for the Apex Embedded Systems STX104 integrated analog PC/104 card. This driver supports the 16 channels of single-ended (8 channels of differential) analog inputs, 2 channels of analog output, 4 digital inputs, and 4 digital outputs provided by the STX104. The base port addresses for the devices may be configured via the base array module parameter. endmenu addac/Makefile 0000644 00000000263 14722071307 0007244 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O ADDAC drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_STX104) += stx104.o resolver/Kconfig 0000644 00000001430 14722071307 0007711 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Resolver/Synchro drivers # menu "Resolver to digital converters" config AD2S90 tristate "Analog Devices ad2s90 driver" depends on SPI help Say yes here to build support for Analog Devices spi resolver to digital converters, ad2s90, provides direct access via sysfs. To compile this driver as a module, choose M here: the module will be called ad2s90. config AD2S1200 tristate "Analog Devices ad2s1200/ad2s1205 driver" depends on SPI depends on GPIOLIB || COMPILE_TEST help Say yes here to build support for Analog Devices spi resolver to digital converters, ad2s1200 and ad2s1205, provides direct access via sysfs. To compile this driver as a module, choose M here: the module will be called ad2s1200. endmenu resolver/Makefile 0000644 00000000233 14722071307 0010046 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for Resolver/Synchro drivers # obj-$(CONFIG_AD2S90) += ad2s90.o obj-$(CONFIG_AD2S1200) += ad2s1200.o gyro/Kconfig 0000644 00000011223 14722071307 0007031 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # IIO Digital Gyroscope Sensor drivers configuration # # When adding new entries keep the list in alphabetical order menu "Digital gyroscope sensors" config ADIS16080 tristate "Analog Devices ADIS16080/100 Yaw Rate Gyroscope with SPI driver" depends on SPI help Say yes here to build support for Analog Devices ADIS16080, ADIS16100 Yaw Rate Gyroscope with SPI. config ADIS16130 tristate "Analog Devices ADIS16130 High Precision Angular Rate Sensor driver" depends on SPI help Say yes here to build support for Analog Devices ADIS16130 High Precision Angular Rate Sensor driver. config ADIS16136 tristate "Analog devices ADIS16136 and similar gyroscopes driver" depends on SPI_MASTER select IIO_ADIS_LIB select IIO_ADIS_LIB_BUFFER if IIO_BUFFER help Say yes here to build support for the Analog Devices ADIS16133, ADIS16135, ADIS16136 gyroscope devices. config ADIS16260 tristate "Analog Devices ADIS16260 Digital Gyroscope Sensor SPI driver" depends on SPI select IIO_ADIS_LIB select IIO_ADIS_LIB_BUFFER if IIO_BUFFER help Say yes here to build support for Analog Devices ADIS16260 ADIS16265 ADIS16250 ADIS16255 and ADIS16251 programmable digital gyroscope sensors. This driver can also be built as a module. If so, the module will be called adis16260. config ADXRS450 tristate "Analog Devices ADXRS450/3 Digital Output Gyroscope SPI driver" depends on SPI help Say yes here to build support for Analog Devices ADXRS450 and ADXRS453 programmable digital output gyroscope. This driver can also be built as a module. If so, the module will be called adxrs450. config BMG160 tristate "BOSCH BMG160 Gyro Sensor" depends on (I2C || SPI_MASTER) select IIO_BUFFER select IIO_TRIGGERED_BUFFER select BMG160_I2C if (I2C) select BMG160_SPI if (SPI) help Say yes here to build support for BOSCH BMG160 Tri-axis Gyro Sensor driver connected via I2C or SPI. This driver also supports BMI055 gyroscope. This driver can also be built as a module. If so, the module will be called bmg160_i2c or bmg160_spi. config BMG160_I2C tristate select REGMAP_I2C config BMG160_SPI tristate select REGMAP_SPI config FXAS21002C tristate "NXP FXAS21002C Gyro Sensor" select IIO_BUFFER select IIO_TRIGGERED_BUFFER select FXAS21002C_I2C if (I2C) select FXAS21002C_SPI if (SPI) depends on (I2C || SPI_MASTER) help Say yes here to build support for NXP FXAS21002C Tri-axis Gyro Sensor driver connected via I2C or SPI. This driver can also be built as a module. If so, the module will be called fxas21002c_i2c or fxas21002c_spi. config FXAS21002C_I2C tristate select REGMAP_I2C config FXAS21002C_SPI tristate select REGMAP_SPI config HID_SENSOR_GYRO_3D depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID Gyroscope 3D" help Say yes here to build support for the HID SENSOR Gyroscope 3D. config MPU3050 tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER select REGMAP config MPU3050_I2C tristate "Invensense MPU3050 devices on I2C" depends on !(INPUT_MPU3050=y || INPUT_MPU3050=m) depends on I2C select MPU3050 select REGMAP_I2C select I2C_MUX help This driver supports the Invensense MPU3050 gyroscope over I2C. This driver can be built as a module. The module will be called inv-mpu3050-i2c. config IIO_ST_GYRO_3AXIS tristate "STMicroelectronics gyroscopes 3-Axis Driver" depends on (I2C || SPI_MASTER) && SYSFS select IIO_ST_SENSORS_CORE select IIO_ST_GYRO_I2C_3AXIS if (I2C) select IIO_ST_GYRO_SPI_3AXIS if (SPI_MASTER) select IIO_TRIGGERED_BUFFER if (IIO_BUFFER) help Say yes here to build support for STMicroelectronics gyroscopes: L3G4200D, LSM330DL, L3GD20, LSM330DLC, L3G4IS, LSM330, LSM9DS0. This driver can also be built as a module. If so, these modules will be created: - st_gyro (core functions for the driver [it is mandatory]); - st_gyro_i2c (necessary for the I2C devices [optional*]); - st_gyro_spi (necessary for the SPI devices [optional*]); (*) one of these is necessary to do something. config IIO_ST_GYRO_I2C_3AXIS tristate depends on IIO_ST_GYRO_3AXIS depends on IIO_ST_SENSORS_I2C config IIO_ST_GYRO_SPI_3AXIS tristate depends on IIO_ST_GYRO_3AXIS depends on IIO_ST_SENSORS_SPI config ITG3200 tristate "InvenSense ITG3200 Digital 3-Axis Gyroscope I2C driver" depends on I2C select IIO_TRIGGERED_BUFFER if IIO_BUFFER help Say yes here to add support for the InvenSense ITG3200 digital 3-axis gyroscope sensor. endmenu gyro/Makefile 0000644 00000002403 14722071307 0007166 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O gyroscope sensor drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_ADIS16080) += adis16080.o obj-$(CONFIG_ADIS16130) += adis16130.o obj-$(CONFIG_ADIS16136) += adis16136.o obj-$(CONFIG_ADIS16260) += adis16260.o obj-$(CONFIG_ADXRS450) += adxrs450.o obj-$(CONFIG_BMG160) += bmg160_core.o obj-$(CONFIG_BMG160_I2C) += bmg160_i2c.o obj-$(CONFIG_BMG160_SPI) += bmg160_spi.o obj-$(CONFIG_FXAS21002C) += fxas21002c_core.o obj-$(CONFIG_FXAS21002C_I2C) += fxas21002c_i2c.o obj-$(CONFIG_FXAS21002C_SPI) += fxas21002c_spi.o obj-$(CONFIG_HID_SENSOR_GYRO_3D) += hid-sensor-gyro-3d.o # Currently this is rolled into one module, split it if # we ever create a separate SPI interface for MPU-3050 obj-$(CONFIG_MPU3050) += mpu3050.o mpu3050-objs := mpu3050-core.o mpu3050-i2c.o itg3200-y := itg3200_core.o itg3200-$(CONFIG_IIO_BUFFER) += itg3200_buffer.o obj-$(CONFIG_ITG3200) += itg3200.o obj-$(CONFIG_IIO_SSP_SENSORS_COMMONS) += ssp_gyro_sensor.o obj-$(CONFIG_IIO_ST_GYRO_3AXIS) += st_gyro.o st_gyro-y := st_gyro_core.o st_gyro-$(CONFIG_IIO_BUFFER) += st_gyro_buffer.o obj-$(CONFIG_IIO_ST_GYRO_I2C_3AXIS) += st_gyro_i2c.o obj-$(CONFIG_IIO_ST_GYRO_SPI_3AXIS) += st_gyro_spi.o chemical/Kconfig 0000644 00000005266 14722071307 0007630 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Chemical sensors # menu "Chemical Sensors" config ATLAS_PH_SENSOR tristate "Atlas Scientific OEM SM sensors" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER select IRQ_WORK help Say Y here to build I2C interface support for the following Atlas Scientific OEM SM sensors: * pH SM sensor * EC SM sensor * ORP SM sensor To compile this driver as module, choose M here: the module will be called atlas-ph-sensor. config BME680 tristate "Bosch Sensortec BME680 sensor driver" depends on (I2C || SPI) select REGMAP select BME680_I2C if I2C select BME680_SPI if SPI help Say yes here to build support for Bosch Sensortec BME680 sensor with temperature, pressure, humidity and gas sensing capability. This driver can also be built as a module. If so, the module for I2C would be called bme680_i2c and bme680_spi for SPI support. config BME680_I2C tristate depends on I2C && BME680 select REGMAP_I2C config BME680_SPI tristate depends on SPI && BME680 select REGMAP_SPI config CCS811 tristate "AMS CCS811 VOC sensor" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here to build I2C interface support for the AMS CCS811 VOC (Volatile Organic Compounds) sensor config IAQCORE tristate "AMS iAQ-Core VOC sensors" depends on I2C help Say Y here to build I2C interface support for the AMS iAQ-Core Continuous/Pulsed VOC (Volatile Organic Compounds) sensors config PMS7003 tristate "Plantower PMS7003 particulate matter sensor" depends on SERIAL_DEV_BUS select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here to build support for the Plantower PMS7003 particulate matter sensor. To compile this driver as a module, choose M here: the module will be called pms7003. config SENSIRION_SGP30 tristate "Sensirion SGPxx gas sensors" depends on I2C select CRC8 help Say Y here to build I2C interface support for the following Sensirion SGP gas sensors: * SGP30 gas sensor * SGPC3 low power gas sensor To compile this driver as module, choose M here: the module will be called sgp30. config SPS30 tristate "SPS30 particulate matter sensor" depends on I2C select CRC8 select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here to build support for the Sensirion SPS30 particulate matter sensor. To compile this driver as a module, choose M here: the module will be called sps30. config VZ89X tristate "SGX Sensortech MiCS VZ89X VOC sensor" depends on I2C help Say Y here to build I2C interface support for the SGX Sensortech MiCS VZ89X VOC (Volatile Organic Compounds) sensors endmenu chemical/Makefile 0000644 00000001020 14722071307 0007745 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for IIO chemical sensors # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_ATLAS_PH_SENSOR) += atlas-ph-sensor.o obj-$(CONFIG_BME680) += bme680_core.o obj-$(CONFIG_BME680_I2C) += bme680_i2c.o obj-$(CONFIG_BME680_SPI) += bme680_spi.o obj-$(CONFIG_CCS811) += ccs811.o obj-$(CONFIG_IAQCORE) += ams-iaq-core.o obj-$(CONFIG_PMS7003) += pms7003.o obj-$(CONFIG_SENSIRION_SGP30) += sgp30.o obj-$(CONFIG_SPS30) += sps30.o obj-$(CONFIG_VZ89X) += vz89x.o dac/Kconfig 0000644 00000027700 14722071307 0006607 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # DAC drivers # # When adding new entries keep the list in alphabetical order menu "Digital to analog converters" config AD5064 tristate "Analog Devices AD5064 and similar multi-channel DAC driver" depends on (SPI_MASTER && I2C!=m) || I2C help Say yes here to build support for Analog Devices AD5024, AD5025, AD5044, AD5045, AD5064, AD5064-1, AD5065, AD5625, AD5625R, AD5627, AD5627R, AD5628, AD5629R, AD5645R, AD5647R, AD5648, AD5665, AD5665R, AD5666, AD5667, AD5667R, AD5668, AD5669R, LTC2606, LTC2607, LTC2609, LTC2616, LTC2617, LTC2619, LTC2626, LTC2627, LTC2629, LTC2631, LTC2633, LTC2635 Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5064. config AD5360 tristate "Analog Devices AD5360/61/62/63/70/71/73 DAC driver" depends on SPI help Say yes here to build support for Analog Devices AD5360, AD5361, AD5362, AD5363, AD5370, AD5371, AD5373 multi-channel Digital to Analog Converters (DAC). To compile this driver as module choose M here: the module will be called ad5360. config AD5380 tristate "Analog Devices AD5380/81/82/83/84/90/91/92 DAC driver" depends on (SPI_MASTER && I2C!=m) || I2C select REGMAP_I2C if I2C select REGMAP_SPI if SPI_MASTER help Say yes here to build support for Analog Devices AD5380, AD5381, AD5382, AD5383, AD5384, AD5390, AD5391, AD5392 multi-channel Digital to Analog Converters (DAC). To compile this driver as module choose M here: the module will be called ad5380. config AD5421 tristate "Analog Devices AD5421 DAC driver" depends on SPI help Say yes here to build support for Analog Devices AD5421 loop-powered digital-to-analog convertors (DAC). To compile this driver as module choose M here: the module will be called ad5421. config AD5446 tristate "Analog Devices AD5446 and similar single channel DACs driver" depends on (SPI_MASTER && I2C!=m) || I2C help Say yes here to build support for Analog Devices AD5300, AD5301, AD5310, AD5311, AD5320, AD5321, AD5444, AD5446, AD5450, AD5451, AD5452, AD5453, AD5512A, AD5541A, AD5542A, AD5543, AD5553, AD5600, AD5601, AD5602, AD5611, AD5612, AD5620, AD5621, AD5622, AD5640, AD5641, AD5660, AD5662 DACs as well as Texas Instruments DAC081S101, DAC101S101, DAC121S101. To compile this driver as a module, choose M here: the module will be called ad5446. config AD5449 tristate "Analog Devices AD5449 and similar DACs driver" depends on SPI_MASTER help Say yes here to build support for Analog Devices AD5415, AD5426, AD5429, AD5432, AD5439, AD5443, AD5449 Digital to Analog Converters. To compile this driver as a module, choose M here: the module will be called ad5449. config AD5592R_BASE tristate config AD5592R tristate "Analog Devices AD5592R ADC/DAC driver" depends on SPI_MASTER select GPIOLIB select AD5592R_BASE help Say yes here to build support for Analog Devices AD5592R Digital to Analog / Analog to Digital Converter. To compile this driver as a module, choose M here: the module will be called ad5592r. config AD5593R tristate "Analog Devices AD5593R ADC/DAC driver" depends on I2C select GPIOLIB select AD5592R_BASE help Say yes here to build support for Analog Devices AD5593R Digital to Analog / Analog to Digital Converter. To compile this driver as a module, choose M here: the module will be called ad5593r. config AD5504 tristate "Analog Devices AD5504/AD5501 DAC SPI driver" depends on SPI help Say yes here to build support for Analog Devices AD5504, AD5501, High Voltage Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5504. config AD5624R_SPI tristate "Analog Devices AD5624/44/64R DAC spi driver" depends on SPI help Say yes here to build support for Analog Devices AD5624R, AD5644R and AD5664R converters (DAC). This driver uses the common SPI interface. config LTC1660 tristate "Linear Technology LTC1660/LTC1665 DAC SPI driver" depends on SPI help Say yes here to build support for Linear Technology LTC1660 and LTC1665 Digital to Analog Converters. To compile this driver as a module, choose M here: the module will be called ltc1660. config LTC2632 tristate "Linear Technology LTC2632-12/10/8 DAC spi driver" depends on SPI help Say yes here to build support for Linear Technology LTC2632-12, LTC2632-10, LTC2632-8 converters (DAC). To compile this driver as a module, choose M here: the module will be called ltc2632. config AD5686 tristate config AD5686_SPI tristate "Analog Devices AD5686 and similar multi-channel DACs (SPI)" depends on SPI select AD5686 help Say yes here to build support for Analog Devices AD5672R, AD5674R, AD5676, AD5676R, AD5679R, AD5684, AD5684R, AD5684R, AD5685R, AD5686, AD5686R Voltage Output Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5686. config AD5696_I2C tristate "Analog Devices AD5696 and similar multi-channel DACs (I2C)" depends on I2C select AD5686 help Say yes here to build support for Analog Devices AD5671R, AD5675R, AD5694, AD5694R, AD5695R, AD5696, AD5696R Voltage Output Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5696. config AD5755 tristate "Analog Devices AD5755/AD5755-1/AD5757/AD5735/AD5737 DAC driver" depends on SPI_MASTER help Say yes here to build support for Analog Devices AD5755, AD5755-1, AD5757, AD5735, AD5737 quad channel Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5755. config AD5758 tristate "Analog Devices AD5758 DAC driver" depends on SPI_MASTER help Say yes here to build support for Analog Devices AD5758 single channel Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5758. config AD5761 tristate "Analog Devices AD5761/61R/21/21R DAC driver" depends on SPI_MASTER help Say yes here to build support for Analog Devices AD5761, AD5761R, AD5721, AD5721R Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5761. config AD5764 tristate "Analog Devices AD5764/64R/44/44R DAC driver" depends on SPI_MASTER help Say yes here to build support for Analog Devices AD5764, AD5764R, AD5744, AD5744R Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5764. config AD5791 tristate "Analog Devices AD5760/AD5780/AD5781/AD5790/AD5791 DAC SPI driver" depends on SPI help Say yes here to build support for Analog Devices AD5760, AD5780, AD5781, AD5790, AD5791 High Resolution Voltage Output Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5791. config AD7303 tristate "Analog Devices AD7303 DAC driver" depends on SPI help Say yes here to build support for Analog Devices AD7303 Digital to Analog Converters (DAC). To compile this driver as module choose M here: the module will be called ad7303. config CIO_DAC tristate "Measurement Computing CIO-DAC IIO driver" depends on X86 && (ISA_BUS || PC104) select ISA_BUS_API help Say yes here to build support for the Measurement Computing CIO-DAC analog output device family (CIO-DAC16, CIO-DAC08, PC104-DAC06). The base port addresses for the devices may be configured via the base array module parameter. config AD8801 tristate "Analog Devices AD8801/AD8803 DAC driver" depends on SPI_MASTER help Say yes here to build support for Analog Devices AD8801, AD8803 Digital to Analog Converters (DAC). To compile this driver as a module choose M here: the module will be called ad8801. config DPOT_DAC tristate "DAC emulation using a DPOT" depends on OF help Say yes here to build support for DAC emulation using a digital potentiometer. To compile this driver as a module, choose M here: the module will be called dpot-dac. config DS4424 tristate "Maxim Integrated DS4422/DS4424 DAC driver" depends on I2C help If you say yes here you get support for Maxim chips DS4422, DS4424. This driver can also be built as a module. If so, the module will be called ds4424. config LPC18XX_DAC tristate "NXP LPC18xx DAC driver" depends on ARCH_LPC18XX || COMPILE_TEST depends on OF && HAS_IOMEM help Say yes here to build support for NXP LPC18XX DAC. To compile this driver as a module, choose M here: the module will be called lpc18xx_dac. config M62332 tristate "Mitsubishi M62332 DAC driver" depends on I2C help If you say yes here you get support for the Mitsubishi M62332 (I2C 8-Bit DACs with rail-to-rail outputs). This driver can also be built as a module. If so, the module will be called m62332. config MAX517 tristate "Maxim MAX517/518/519/520/521 DAC driver" depends on I2C help If you say yes here you get support for the following Maxim chips (I2C 8-Bit DACs with rail-to-rail outputs): MAX517 - Single channel, single reference MAX518 - Dual channel, ref=Vdd MAX519 - Dual channel, dual reference MAX520 - Quad channel, quad reference MAX521 - Octal channel, independent ref for ch0-3, shared ref for ch4-7 This driver can also be built as a module. If so, the module will be called max517. config MAX5821 tristate "Maxim MAX5821 DAC driver" depends on I2C depends on OF help Say yes here to build support for Maxim MAX5821 10 bits DAC. config MCP4725 tristate "MCP4725/6 DAC driver" depends on I2C ---help--- Say Y here if you want to build a driver for the Microchip MCP 4725/6 12-bit digital-to-analog converter (DAC) with I2C interface. To compile this driver as a module, choose M here: the module will be called mcp4725. config MCP4922 tristate "MCP4902, MCP4912, MCP4922 DAC driver" depends on SPI help Say yes here to build the driver for the Microchip MCP4902 MCP4912, and MCP4922 DAC devices. To compile this driver as a module, choose M here: the module will be called mcp4922. config STM32_DAC tristate "STMicroelectronics STM32 DAC" depends on (ARCH_STM32 && OF) || COMPILE_TEST depends on REGULATOR select STM32_DAC_CORE help Say yes here to build support for STMicroelectronics STM32 Digital to Analog Converter (DAC). This driver can also be built as a module. If so, the module will be called stm32-dac. config STM32_DAC_CORE tristate config TI_DAC082S085 tristate "Texas Instruments 8/10/12-bit 2/4-channel DAC driver" depends on SPI_MASTER help Driver for the Texas Instruments (formerly National Semiconductor) DAC082S085, DAC102S085, DAC122S085, DAC084S085, DAC104S085 and DAC124S085. If compiled as a module, it will be called ti-dac082s085. config TI_DAC5571 tristate "Texas Instruments 8/10/12/16-bit 1/2/4-channel DAC driver" depends on I2C help Driver for the Texas Instruments DAC5571, DAC6571, DAC7571, DAC5574, DAC6574, DAC7574, DAC5573, DAC6573, DAC7573, DAC8571, DAC8574. If compiled as a module, it will be called ti-dac5571. config TI_DAC7311 tristate "Texas Instruments 8/10/12-bit 1-channel DAC driver" depends on SPI help Driver for the Texas Instruments DAC7311, DAC6311, DAC5311. If compiled as a module, it will be called ti-dac7311. config TI_DAC7612 tristate "Texas Instruments 12-bit 2-channel DAC driver" depends on SPI_MASTER && GPIOLIB help Driver for the Texas Instruments DAC7612, DAC7612U, DAC7612UB The driver hand drive the load pin automatically, otherwise it needs to be toggled manually. If compiled as a module, it will be called ti-dac7612. config VF610_DAC tristate "Vybrid vf610 DAC driver" depends on OF depends on HAS_IOMEM help Say yes here to support Vybrid board digital-to-analog converter. This driver can also be built as a module. If so, the module will be called vf610_dac. endmenu dac/Makefile 0000644 00000003035 14722071307 0006737 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O DAC drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AD5360) += ad5360.o obj-$(CONFIG_AD5380) += ad5380.o obj-$(CONFIG_AD5421) += ad5421.o obj-$(CONFIG_AD5624R_SPI) += ad5624r_spi.o obj-$(CONFIG_AD5064) += ad5064.o obj-$(CONFIG_AD5504) += ad5504.o obj-$(CONFIG_AD5446) += ad5446.o obj-$(CONFIG_AD5449) += ad5449.o obj-$(CONFIG_AD5592R_BASE) += ad5592r-base.o obj-$(CONFIG_AD5592R) += ad5592r.o obj-$(CONFIG_AD5593R) += ad5593r.o obj-$(CONFIG_AD5755) += ad5755.o obj-$(CONFIG_AD5758) += ad5758.o obj-$(CONFIG_AD5761) += ad5761.o obj-$(CONFIG_AD5764) += ad5764.o obj-$(CONFIG_AD5791) += ad5791.o obj-$(CONFIG_AD5686) += ad5686.o obj-$(CONFIG_AD5686_SPI) += ad5686-spi.o obj-$(CONFIG_AD5696_I2C) += ad5696-i2c.o obj-$(CONFIG_AD7303) += ad7303.o obj-$(CONFIG_AD8801) += ad8801.o obj-$(CONFIG_CIO_DAC) += cio-dac.o obj-$(CONFIG_DPOT_DAC) += dpot-dac.o obj-$(CONFIG_DS4424) += ds4424.o obj-$(CONFIG_LPC18XX_DAC) += lpc18xx_dac.o obj-$(CONFIG_LTC1660) += ltc1660.o obj-$(CONFIG_LTC2632) += ltc2632.o obj-$(CONFIG_M62332) += m62332.o obj-$(CONFIG_MAX517) += max517.o obj-$(CONFIG_MAX5821) += max5821.o obj-$(CONFIG_MCP4725) += mcp4725.o obj-$(CONFIG_MCP4922) += mcp4922.o obj-$(CONFIG_STM32_DAC_CORE) += stm32-dac-core.o obj-$(CONFIG_STM32_DAC) += stm32-dac.o obj-$(CONFIG_TI_DAC082S085) += ti-dac082s085.o obj-$(CONFIG_TI_DAC5571) += ti-dac5571.o obj-$(CONFIG_TI_DAC7311) += ti-dac7311.o obj-$(CONFIG_TI_DAC7612) += ti-dac7612.o obj-$(CONFIG_VF610_DAC) += vf610_dac.o orientation/Kconfig 0000644 00000001451 14722071307 0010406 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Inclinometer sensors # # When adding new entries keep the list in alphabetical order menu "Inclinometer sensors" config HID_SENSOR_INCLINOMETER_3D depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID Inclinometer 3D" help Say yes here to build support for the HID SENSOR Inclinometer 3D. config HID_SENSOR_DEVICE_ROTATION depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID Device Rotation" help Say yes here to build support for the HID SENSOR device rotation. The output of a device rotation sensor is presented using quaternion format. endmenu orientation/Makefile 0000644 00000000450 14722071307 0010541 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for industrial I/O Inclinometer sensor drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_HID_SENSOR_INCLINOMETER_3D) += hid-sensor-incl-3d.o obj-$(CONFIG_HID_SENSOR_DEVICE_ROTATION) += hid-sensor-rotation.o magnetometer/Kconfig 0000644 00000013400 14722071307 0010537 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Magnetometer sensors # # When adding new entries keep the list in alphabetical order menu "Magnetometer sensors" config AK8974 tristate "Asahi Kasei AK8974 3-Axis Magnetometer" depends on I2C depends on OF select REGMAP_I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Asahi Kasei AK8974, AMI305 or AMI306 I2C-based 3-axis magnetometer chips. To compile this driver as a module, choose M here: the module will be called ak8974. config AK8975 tristate "Asahi Kasei AK8975 3-Axis Magnetometer" depends on I2C depends on GPIOLIB || COMPILE_TEST select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for Asahi Kasei AK8975, AK8963, AK09911 or AK09912 3-Axis Magnetometer. To compile this driver as a module, choose M here: the module will be called ak8975. config AK09911 tristate "Asahi Kasei AK09911 3-axis Compass" depends on I2C depends on GPIOLIB || COMPILE_TEST select AK8975 help Deprecated: AK09911 is now supported by AK8975 driver. config BMC150_MAGN tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config BMC150_MAGN_I2C tristate "Bosch BMC150 I2C Magnetometer Driver" depends on I2C select BMC150_MAGN select REGMAP_I2C help Say yes here to build support for the BMC150 magnetometer with I2C interface. This is a combo module with both accelerometer and magnetometer. This driver is only implementing magnetometer part, which has its own address and register map. This driver also supports I2C Bosch BMC156 and BMM150 chips. To compile this driver as a module, choose M here: the module will be called bmc150_magn_i2c. config BMC150_MAGN_SPI tristate "Bosch BMC150 SPI Magnetometer Driver" depends on SPI select BMC150_MAGN select REGMAP_SPI help Say yes here to build support for the BMC150 magnetometer with SPI interface. This is a combo module with both accelerometer and magnetometer. This driver is only implementing magnetometer part, which has its own address and register map. This driver also supports SPI Bosch BMC156 and BMM150 chips. To compile this driver as a module, choose M here: the module will be called bmc150_magn_spi. config MAG3110 tristate "Freescale MAG3110 3-Axis Magnetometer" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for the Freescale MAG3110 3-Axis magnetometer. To compile this driver as a module, choose M here: the module will be called mag3110. config HID_SENSOR_MAGNETOMETER_3D depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID Magenetometer 3D" help Say yes here to build support for the HID SENSOR Magnetometer 3D. config MMC35240 tristate "MEMSIC MMC35240 3-axis magnetic sensor" select REGMAP_I2C depends on I2C help Say yes here to build support for the MEMSIC MMC35240 3-axis magnetic sensor. To compile this driver as a module, choose M here: the module will be called mmc35240. config IIO_ST_MAGN_3AXIS tristate "STMicroelectronics magnetometers 3-Axis Driver" depends on (I2C || SPI_MASTER) && SYSFS select IIO_ST_SENSORS_CORE select IIO_ST_MAGN_I2C_3AXIS if (I2C) select IIO_ST_MAGN_SPI_3AXIS if (SPI_MASTER) select IIO_TRIGGERED_BUFFER if (IIO_BUFFER) help Say yes here to build support for STMicroelectronics magnetometers: LSM303DLHC, LSM303DLM, LIS3MDL. This driver can also be built as a module. If so, these modules will be created: - st_magn (core functions for the driver [it is mandatory]); - st_magn_i2c (necessary for the I2C devices [optional*]); - st_magn_spi (necessary for the SPI devices [optional*]); (*) one of these is necessary to do something. config IIO_ST_MAGN_I2C_3AXIS tristate depends on IIO_ST_MAGN_3AXIS depends on IIO_ST_SENSORS_I2C config IIO_ST_MAGN_SPI_3AXIS tristate depends on IIO_ST_MAGN_3AXIS depends on IIO_ST_SENSORS_SPI config SENSORS_HMC5843 tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config SENSORS_HMC5843_I2C tristate "Honeywell HMC5843/5883/5883L 3-Axis Magnetometer (I2C)" depends on I2C select SENSORS_HMC5843 select REGMAP_I2C help Say Y here to add support for the Honeywell HMC5843, HMC5883 and HMC5883L 3-Axis Magnetometer (digital compass). This driver can also be compiled as a set of modules. If so, these modules will be created: - hmc5843_core (core functions) - hmc5843_i2c (support for HMC5843, HMC5883, HMC5883L and HMC5983) config SENSORS_HMC5843_SPI tristate "Honeywell HMC5983 3-Axis Magnetometer (SPI)" depends on SPI_MASTER select SENSORS_HMC5843 select REGMAP_SPI help Say Y here to add support for the Honeywell HMC5983 3-Axis Magnetometer (digital compass). This driver can also be compiled as a set of modules. If so, these modules will be created: - hmc5843_core (core functions) - hmc5843_spi (support for HMC5983) config SENSORS_RM3100 tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config SENSORS_RM3100_I2C tristate "PNI RM3100 3-Axis Magnetometer (I2C)" depends on I2C select SENSORS_RM3100 select REGMAP_I2C help Say Y here to add support for the PNI RM3100 3-Axis Magnetometer. This driver can also be compiled as a module. To compile this driver as a module, choose M here: the module will be called rm3100-i2c. config SENSORS_RM3100_SPI tristate "PNI RM3100 3-Axis Magnetometer (SPI)" depends on SPI_MASTER select SENSORS_RM3100 select REGMAP_SPI help Say Y here to add support for the PNI RM3100 3-Axis Magnetometer. This driver can also be compiled as a module. To compile this driver as a module, choose M here: the module will be called rm3100-spi. endmenu magnetometer/Makefile 0000644 00000002015 14722071307 0010674 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O Magnetometer sensor drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AK8974) += ak8974.o obj-$(CONFIG_AK8975) += ak8975.o obj-$(CONFIG_BMC150_MAGN) += bmc150_magn.o obj-$(CONFIG_BMC150_MAGN_I2C) += bmc150_magn_i2c.o obj-$(CONFIG_BMC150_MAGN_SPI) += bmc150_magn_spi.o obj-$(CONFIG_MAG3110) += mag3110.o obj-$(CONFIG_HID_SENSOR_MAGNETOMETER_3D) += hid-sensor-magn-3d.o obj-$(CONFIG_MMC35240) += mmc35240.o obj-$(CONFIG_IIO_ST_MAGN_3AXIS) += st_magn.o st_magn-y := st_magn_core.o st_magn-$(CONFIG_IIO_BUFFER) += st_magn_buffer.o obj-$(CONFIG_IIO_ST_MAGN_I2C_3AXIS) += st_magn_i2c.o obj-$(CONFIG_IIO_ST_MAGN_SPI_3AXIS) += st_magn_spi.o obj-$(CONFIG_SENSORS_HMC5843) += hmc5843_core.o obj-$(CONFIG_SENSORS_HMC5843_I2C) += hmc5843_i2c.o obj-$(CONFIG_SENSORS_HMC5843_SPI) += hmc5843_spi.o obj-$(CONFIG_SENSORS_RM3100) += rm3100-core.o obj-$(CONFIG_SENSORS_RM3100_I2C) += rm3100-i2c.o obj-$(CONFIG_SENSORS_RM3100_SPI) += rm3100-spi.o humidity/Kconfig 0000644 00000006270 14722071307 0007713 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # humidity sensor drivers # menu "Humidity sensors" config AM2315 tristate "Aosong AM2315 relative humidity and temperature sensor" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for the Aosong AM2315 relative humidity and ambient temperature sensor. This driver can also be built as a module. If so, the module will be called am2315. config DHT11 tristate "DHT11 (and compatible sensors) driver" depends on GPIOLIB || COMPILE_TEST help This driver supports reading data via a single interrupt generating GPIO line. Currently tested are DHT11 and DHT22. Other sensors should work as well as long as they speak the same protocol. config HDC100X tristate "TI HDC100x relative humidity and temperature sensor" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for the Texas Instruments HDC1000, HDC1008, HDC1010, HDC1050, and HDC1080 relative humidity and temperature sensors. To compile this driver as a module, choose M here: the module will be called hdc100x. config HID_SENSOR_HUMIDITY tristate "HID Environmental humidity sensor" depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER help Say yes here to build support for the HID SENSOR humidity driver To compile this driver as a module, choose M here: the module will be called hid-sensor-humidity. config HTS221 tristate "STMicroelectronics HTS221 sensor Driver" depends on (I2C || SPI) select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HTS221_I2C if (I2C) select HTS221_SPI if (SPI_MASTER) help Say yes here to build support for STMicroelectronics HTS221 temperature-humidity sensor To compile this driver as a module, choose M here: the module will be called hts221. config HTS221_I2C tristate depends on HTS221 select REGMAP_I2C config HTS221_SPI tristate depends on HTS221 select REGMAP_SPI config HTU21 tristate "Measurement Specialties HTU21 humidity & temperature sensor" depends on I2C select IIO_MS_SENSORS_I2C help If you say yes here you get support for the Measurement Specialties HTU21 humidity and temperature sensor. This driver is also used for MS8607 temperature, pressure & humidity sensor This driver can also be built as a module. If so, the module will be called htu21. config SI7005 tristate "SI7005 relative humidity and temperature sensor" depends on I2C help Say yes here to build support for the Silabs Si7005 relative humidity and temperature sensor. To compile this driver as a module, choose M here: the module will be called si7005. This driver also supports Hoperf TH02 Humidity and Temperature Sensor. config SI7020 tristate "Si7013/20/21 Relative Humidity and Temperature Sensors" depends on I2C help Say yes here to build support for the Silicon Labs Si7013/20/21 Relative Humidity and Temperature Sensors. This driver also supports Hoperf TH06 Humidity and Temperature Sensor. To compile this driver as a module, choose M here: the module will be called si7020. endmenu humidity/Makefile 0000644 00000001062 14722071307 0010042 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for IIO humidity sensor drivers # obj-$(CONFIG_AM2315) += am2315.o obj-$(CONFIG_DHT11) += dht11.o obj-$(CONFIG_HDC100X) += hdc100x.o obj-$(CONFIG_HID_SENSOR_HUMIDITY) += hid-sensor-humidity.o hts221-y := hts221_core.o \ hts221_buffer.o obj-$(CONFIG_HTS221) += hts221.o obj-$(CONFIG_HTS221_I2C) += hts221_i2c.o obj-$(CONFIG_HTS221_SPI) += hts221_spi.o obj-$(CONFIG_HTU21) += htu21.o obj-$(CONFIG_SI7005) += si7005.o obj-$(CONFIG_SI7020) += si7020.o ccflags-y += -I$(srctree)/drivers/iio/common/hid-sensors potentiometer/Kconfig 0000644 00000007012 14722071307 0010750 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Potentiometer drivers # # When adding new entries keep the list in alphabetical order menu "Digital potentiometers" config AD5272 tristate "Analog Devices AD5272 and similar Digital Potentiometer driver" depends on I2C help Say yes here to build support for the Analog Devices AD5272 and AD5274 digital potentiometer chip. To compile this driver as a module, choose M here: the module will be called ad5272. config DS1803 tristate "Maxim Integrated DS1803 Digital Potentiometer driver" depends on I2C help Say yes here to build support for the Maxim Integrated DS1803 digital potentiometer chip. To compile this driver as a module, choose M here: the module will be called ds1803. config MAX5432 tristate "Maxim MAX5432-MAX5435 Digital Potentiometer driver" depends on I2C help Say yes here to build support for the Maxim MAX5432, MAX5433, MAX5434 and MAX5435 digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called max5432. config MAX5481 tristate "Maxim MAX5481-MAX5484 Digital Potentiometer driver" depends on SPI help Say yes here to build support for the Maxim MAX5481, MAX5482, MAX5483, MAX5484 digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called max5481. config MAX5487 tristate "Maxim MAX5487/MAX5488/MAX5489 Digital Potentiometer driver" depends on SPI help Say yes here to build support for the Maxim MAX5487, MAX5488, MAX5489 digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called max5487. config MCP4018 tristate "Microchip MCP4017/18/19 Digital Potentiometer driver" depends on I2C help Say yes here to build support for the Microchip MCP4017, MCP4018, MCP4019 digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called mcp4018. config MCP4131 tristate "Microchip MCP413X/414X/415X/416X/423X/424X/425X/426X Digital Potentiometer driver" depends on SPI help Say yes here to build support for the Microchip MCP4131, MCP4132, MCP4141, MCP4142, MCP4151, MCP4152, MCP4161, MCP4162, MCP4231, MCP4232, MCP4241, MCP4242, MCP4251, MCP4252, MCP4261, MCP4262, digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called mcp4131. config MCP4531 tristate "Microchip MCP45xx/MCP46xx Digital Potentiometer driver" depends on I2C help Say yes here to build support for the Microchip MCP4531, MCP4532, MCP4541, MCP4542, MCP4551, MCP4552, MCP4561, MCP4562, MCP4631, MCP4632, MCP4641, MCP4642, MCP4651, MCP4652, MCP4661, MCP4662 digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called mcp4531. config MCP41010 tristate "Microchip MCP41xxx/MCP42xxx Digital Potentiometer driver" depends on SPI help Say yes here to build support for the Microchip MCP41010, MCP41050, MCP41100, MCP42010, MCP42050, MCP42100 digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called mcp41010. config TPL0102 tristate "Texas Instruments digital potentiometer driver" depends on I2C select REGMAP_I2C help Say yes here to build support for the Texas Instruments TPL0102, TPL0402 digital potentiometer chips. To compile this driver as a module, choose M here: the module will be called tpl0102. endmenu potentiometer/Makefile 0000644 00000000766 14722071307 0011116 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O potentiometer drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AD5272) += ad5272.o obj-$(CONFIG_DS1803) += ds1803.o obj-$(CONFIG_MAX5432) += max5432.o obj-$(CONFIG_MAX5481) += max5481.o obj-$(CONFIG_MAX5487) += max5487.o obj-$(CONFIG_MCP4018) += mcp4018.o obj-$(CONFIG_MCP4131) += mcp4131.o obj-$(CONFIG_MCP4531) += mcp4531.o obj-$(CONFIG_MCP41010) += mcp41010.o obj-$(CONFIG_TPL0102) += tpl0102.o Makefile 0000644 00000003613 14722071307 0006212 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 include ../scripts/Makefile.include bindir ?= /usr/bin ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) endif # Do not use make's built-in rules # (this improves performance and avoids hard-to-debug behaviour); MAKEFLAGS += -r override CFLAGS += -O2 -Wall -g -D_GNU_SOURCE -I$(OUTPUT)include ALL_TARGETS := iio_event_monitor lsiio iio_generic_buffer ALL_PROGRAMS := $(patsubst %,$(OUTPUT)%,$(ALL_TARGETS)) all: $(ALL_PROGRAMS) export srctree OUTPUT CC LD CFLAGS include $(srctree)/tools/build/Makefile.include # # We need the following to be outside of kernel tree # $(OUTPUT)include/linux/iio: ../../include/uapi/linux/iio mkdir -p $(OUTPUT)include/linux/iio 2>&1 || true ln -sf $(CURDIR)/../../include/uapi/linux/iio/events.h $@ ln -sf $(CURDIR)/../../include/uapi/linux/iio/types.h $@ prepare: $(OUTPUT)include/linux/iio LSIIO_IN := $(OUTPUT)lsiio-in.o $(LSIIO_IN): prepare FORCE $(Q)$(MAKE) $(build)=lsiio $(OUTPUT)lsiio: $(LSIIO_IN) $(QUIET_LINK)$(CC) $(CFLAGS) $(LDFLAGS) $< -o $@ IIO_EVENT_MONITOR_IN := $(OUTPUT)iio_event_monitor-in.o $(IIO_EVENT_MONITOR_IN): prepare FORCE $(Q)$(MAKE) $(build)=iio_event_monitor $(OUTPUT)iio_event_monitor: $(IIO_EVENT_MONITOR_IN) $(QUIET_LINK)$(CC) $(CFLAGS) $(LDFLAGS) $< -o $@ IIO_GENERIC_BUFFER_IN := $(OUTPUT)iio_generic_buffer-in.o $(IIO_GENERIC_BUFFER_IN): prepare FORCE $(Q)$(MAKE) $(build)=iio_generic_buffer $(OUTPUT)iio_generic_buffer: $(IIO_GENERIC_BUFFER_IN) $(QUIET_LINK)$(CC) $(CFLAGS) $(LDFLAGS) $< -o $@ clean: rm -f $(ALL_PROGRAMS) rm -rf $(OUTPUT)include/linux/iio find $(if $(OUTPUT),$(OUTPUT),.) -name '*.o' -delete -o -name '\.*.d' -delete install: $(ALL_PROGRAMS) install -d -m 755 $(DESTDIR)$(bindir); \ for program in $(ALL_PROGRAMS); do \ install $$program $(DESTDIR)$(bindir); \ done FORCE: .PHONY: all install clean FORCE prepare common/ms_sensors/Kconfig 0000644 00000000203 14722071307 0011530 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Measurements Specialties sensors common library # config IIO_MS_SENSORS_I2C tristate common/ms_sensors/Makefile 0000644 00000000244 14722071307 0011672 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Measurement Specialties sensor common modules. # obj-$(CONFIG_IIO_MS_SENSORS_I2C) += ms_sensors_i2c.o common/cros_ec_sensors/Kconfig 0000644 00000002020 14722071307 0012525 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Chrome OS Embedded Controller managed sensors library # config IIO_CROS_EC_SENSORS_CORE tristate "ChromeOS EC Sensors Core" depends on SYSFS && CROS_EC select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Base module for the ChromeOS EC Sensors module. Contains core functions used by other IIO CrosEC sensor drivers. Define common attributes and sysfs interrupt handler. config IIO_CROS_EC_SENSORS tristate "ChromeOS EC Contiguous Sensors" depends on IIO_CROS_EC_SENSORS_CORE help Module to handle 3d contiguous sensors like Accelerometers, Gyroscope and Magnetometer that are presented by the ChromeOS EC Sensor hub. Creates an IIO device for each functions. config IIO_CROS_EC_SENSORS_LID_ANGLE tristate "ChromeOS EC Sensor for lid angle" depends on IIO_CROS_EC_SENSORS_CORE help Module to report the angle between lid and base for some convertible devices. This module is loaded when the EC can calculate the angle between the base and the lid. common/cros_ec_sensors/Makefile 0000644 00000000450 14722071307 0012667 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for sensors seen through the ChromeOS EC sensor hub. # obj-$(CONFIG_IIO_CROS_EC_SENSORS_CORE) += cros_ec_sensors_core.o obj-$(CONFIG_IIO_CROS_EC_SENSORS) += cros_ec_sensors.o obj-$(CONFIG_IIO_CROS_EC_SENSORS_LID_ANGLE) += cros_ec_lid_angle.o common/Kconfig 0000644 00000000464 14722071307 0007346 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # IIO common modules # source "drivers/iio/common/cros_ec_sensors/Kconfig" source "drivers/iio/common/hid-sensors/Kconfig" source "drivers/iio/common/ms_sensors/Kconfig" source "drivers/iio/common/ssp_sensors/Kconfig" source "drivers/iio/common/st_sensors/Kconfig" common/st_sensors/Kconfig 0000644 00000000471 14722071307 0011546 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # STMicroelectronics sensors common library # config IIO_ST_SENSORS_I2C tristate select REGMAP_I2C config IIO_ST_SENSORS_SPI tristate select REGMAP_SPI config IIO_ST_SENSORS_CORE tristate select IIO_ST_SENSORS_I2C if I2C select IIO_ST_SENSORS_SPI if SPI_MASTER common/st_sensors/Makefile 0000644 00000000623 14722071307 0011702 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the STMicroelectronics sensor common modules. # obj-$(CONFIG_IIO_ST_SENSORS_I2C) += st_sensors_i2c.o obj-$(CONFIG_IIO_ST_SENSORS_SPI) += st_sensors_spi.o obj-$(CONFIG_IIO_ST_SENSORS_CORE) += st_sensors.o st_sensors-y := st_sensors_core.o st_sensors-$(CONFIG_IIO_BUFFER) += st_sensors_buffer.o st_sensors-$(CONFIG_IIO_TRIGGER) += st_sensors_trigger.o common/hid-sensors/Kconfig 0000644 00000001650 14722071307 0011602 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Hid Sensor common modules # menu "Hid Sensor IIO Common" config HID_SENSOR_IIO_COMMON tristate "Common modules for all HID Sensor IIO drivers" depends on HID_SENSOR_HUB select HID_SENSOR_IIO_TRIGGER if IIO_BUFFER help Say yes here to build support for HID sensor to use HID sensor common processing for attributes and IIO triggers. There are many attributes which can be shared among multiple HID sensor drivers, this module contains processing for those attributes. config HID_SENSOR_IIO_TRIGGER tristate "Common module (trigger) for all HID Sensor IIO drivers" depends on HID_SENSOR_HUB && HID_SENSOR_IIO_COMMON && IIO_BUFFER select IIO_TRIGGER help Say yes here to build trigger support for HID sensors. Triggers will be send if all requested attributes were read. If this driver is compiled as a module, it will be named hid-sensor-trigger. endmenu common/hid-sensors/Makefile 0000644 00000000412 14722071307 0011732 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Hid sensor common modules. # obj-$(CONFIG_HID_SENSOR_IIO_COMMON) += hid-sensor-iio-common.o obj-$(CONFIG_HID_SENSOR_IIO_TRIGGER) += hid-sensor-trigger.o hid-sensor-iio-common-y := hid-sensor-attributes.o common/Makefile 0000644 00000000760 14722071307 0007502 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the IIO common modules. # Common modules contains modules, which can be shared among multiple # IIO modules. For example if the trigger processing is common for # multiple IIO modules then this can be moved to a common module # instead of duplicating in each module. # # When adding new entries keep the list in alphabetical order obj-y += cros_ec_sensors/ obj-y += hid-sensors/ obj-y += ms_sensors/ obj-y += ssp_sensors/ obj-y += st_sensors/ common/ssp_sensors/Kconfig 0000644 00000001277 14722071307 0011732 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # SSP sensor drivers and commons configuration # menu "SSP Sensor Common" config IIO_SSP_SENSORS_COMMONS tristate "Commons for all SSP Sensor IIO drivers" depends on IIO_SSP_SENSORHUB select IIO_BUFFER select IIO_KFIFO_BUF help Say yes here to build commons for SSP sensors. To compile this as a module, choose M here: the module will be called ssp_iio. config IIO_SSP_SENSORHUB tristate "Samsung Sensorhub driver" depends on SPI select MFD_CORE help SSP driver for sensorhub. If you say yes here you get ssp support for sensorhub. To compile this driver as a module, choose M here: the module will be called sensorhub. endmenu common/ssp_sensors/Makefile 0000644 00000000352 14722071307 0012060 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for SSP sensor drivers and commons. # sensorhub-objs := ssp_dev.o ssp_spi.o obj-$(CONFIG_IIO_SSP_SENSORHUB) += sensorhub.o obj-$(CONFIG_IIO_SSP_SENSORS_COMMONS) += ssp_iio.o temperature/Kconfig 0000644 00000006055 14722071307 0010415 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Temperature sensor drivers # menu "Temperature sensors" config MAXIM_THERMOCOUPLE tristate "Maxim thermocouple sensors" depends on SPI select IIO_BUFFER select IIO_TRIGGERED_BUFFER help If you say yes here you get support for the Maxim series of thermocouple sensors connected via SPI. Supported sensors: * MAX6675 * MAX31855 This driver can also be built as a module. If so, the module will be called maxim_thermocouple. config HID_SENSOR_TEMP tristate "HID Environmental temperature sensor" depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER help Say yes here to build support for the HID SENSOR temperature driver To compile this driver as a module, choose M here: the module will be called hid-sensor-temperature. config MLX90614 tristate "MLX90614 contact-less infrared sensor" depends on I2C help If you say yes here you get support for the Melexis MLX90614 contact-less infrared sensor connected with I2C. This driver can also be built as a module. If so, the module will be called mlx90614. config MLX90632 tristate "MLX90632 contact-less infrared sensor with medical accuracy" depends on I2C select REGMAP_I2C help If you say yes here you get support for the Melexis MLX90632 contact-less infrared sensor with medical accuracy connected with I2C. This driver can also be built as a module. If so, the module will be called mlx90632. config TMP006 tristate "TMP006 infrared thermopile sensor" depends on I2C help If you say yes here you get support for the Texas Instruments TMP006 infrared thermopile sensor. This driver can also be built as a module. If so, the module will be called tmp006. config TMP007 tristate "TMP007 infrared thermopile sensor with Integrated Math Engine" depends on I2C help If you say yes here you get support for the Texas Instruments TMP007 infrared thermopile sensor with Integrated Math Engine. This driver can also be built as a module. If so, the module will be called tmp007. config TSYS01 tristate "Measurement Specialties TSYS01 temperature sensor using I2C bus connection" depends on I2C select IIO_MS_SENSORS_I2C help If you say yes here you get support for the Measurement Specialties TSYS01 I2C temperature sensor. This driver can also be built as a module. If so, the module will be called tsys01. config TSYS02D tristate "Measurement Specialties TSYS02D temperature sensor" depends on I2C select IIO_MS_SENSORS_I2C help If you say yes here you get support for the Measurement Specialties TSYS02D temperature sensor. This driver can also be built as a module. If so, the module will be called tsys02d. config MAX31856 tristate "MAX31856 thermocouple sensor" depends on SPI help If you say yes here you get support for MAX31856 thermocouple sensor chip connected via SPI. This driver can also be built as a module. If so, the module will be called max31856. endmenu temperature/Makefile 0000644 00000000702 14722071307 0010543 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O temperature drivers # obj-$(CONFIG_HID_SENSOR_TEMP) += hid-sensor-temperature.o obj-$(CONFIG_MAXIM_THERMOCOUPLE) += maxim_thermocouple.o obj-$(CONFIG_MAX31856) += max31856.o obj-$(CONFIG_MLX90614) += mlx90614.o obj-$(CONFIG_MLX90632) += mlx90632.o obj-$(CONFIG_TMP006) += tmp006.o obj-$(CONFIG_TMP007) += tmp007.o obj-$(CONFIG_TSYS01) += tsys01.o obj-$(CONFIG_TSYS02D) += tsys02d.o potentiostat/Kconfig 0000644 00000001042 14722071307 0010604 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Potentiostat drivers # # When adding new entries keep the list in alphabetical order menu "Digital potentiostats" config LMP91000 tristate "Texas Instruments LMP91000 potentiostat driver" depends on I2C select REGMAP_I2C select IIO_BUFFER select IIO_BUFFER_CB select IIO_TRIGGERED_BUFFER help Say yes here to build support for the Texas Instruments LMP91000 digital potentiostat chip. To compile this driver as a module, choose M here: the module will be called lmp91000 endmenu potentiostat/Makefile 0000644 00000000303 14722071307 0010740 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for industrial I/O potentiostat drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_LMP91000) += lmp91000.o frequency/Kconfig 0000644 00000002701 14722071307 0010053 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Frequency # Direct Digital Synthesis drivers (DDS) # Clock Distribution device drivers # Phase-Locked Loop (PLL) frequency synthesizers # # When adding new entries keep the list in alphabetical order menu "Frequency Synthesizers DDS/PLL" menu "Clock Generator/Distribution" config AD9523 tristate "Analog Devices AD9523 Low Jitter Clock Generator" depends on SPI help Say yes here to build support for Analog Devices AD9523 Low Jitter Clock Generator. The driver provides direct access via sysfs. To compile this driver as a module, choose M here: the module will be called ad9523. endmenu # # Phase-Locked Loop (PLL) frequency synthesizers # menu "Phase-Locked Loop (PLL) frequency synthesizers" config ADF4350 tristate "Analog Devices ADF4350/ADF4351 Wideband Synthesizers" depends on SPI help Say yes here to build support for Analog Devices ADF4350/ADF4351 Wideband Synthesizers. The driver provides direct access via sysfs. To compile this driver as a module, choose M here: the module will be called adf4350. config ADF4371 tristate "Analog Devices ADF4371/ADF4372 Wideband Synthesizers" depends on SPI select REGMAP_SPI help Say yes here to build support for Analog Devices ADF4371 and ADF4372 Wideband Synthesizers. The driver provides direct access via sysfs. To compile this driver as a module, choose M here: the module will be called adf4371. endmenu endmenu frequency/Makefile 0000644 00000000353 14722071307 0010211 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile iio/frequency # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AD9523) += ad9523.o obj-$(CONFIG_ADF4350) += adf4350.o obj-$(CONFIG_ADF4371) += adf4371.o multiplexer/Kconfig 0000644 00000000641 14722071307 0010425 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Multiplexer drivers # # When adding new entries keep the list in alphabetical order menu "Multiplexers" config IIO_MUX tristate "IIO multiplexer driver" select MULTIPLEXER depends on OF || COMPILE_TEST help Say yes here to build support for the IIO multiplexer. To compile this driver as a module, choose M here: the module will be called iio-mux. endmenu multiplexer/Makefile 0000644 00000000300 14722071307 0010552 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for industrial I/O multiplexer drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_IIO_MUX) += iio-mux.o dummy/Kconfig 0000644 00000002117 14722071307 0007206 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Industrial I/O subsystem Dummy Driver configuration # menu "IIO dummy driver" depends on IIO config IIO_DUMMY_EVGEN select IRQ_SIM tristate config IIO_SIMPLE_DUMMY tristate "An example driver with no hardware requirements" depends on IIO_SW_DEVICE help Driver intended mainly as documentation for how to write a driver. May also be useful for testing userspace code without hardware. if IIO_SIMPLE_DUMMY config IIO_SIMPLE_DUMMY_EVENTS bool "Event generation support" select IIO_DUMMY_EVGEN help Add some dummy events to the simple dummy driver. The purpose of this is to generate 'fake' event interrupts thus allowing that driver's code to be as close as possible to that a normal driver talking to hardware. config IIO_SIMPLE_DUMMY_BUFFER bool "Buffered capture support" select IIO_BUFFER select IIO_TRIGGER select IIO_KFIFO_BUF help Add buffered data capture to the simple dummy driver. Buffer handling elements of industrial I/O reference driver. Uses the kfifo buffer. endif # IIO_SIMPLE_DUMMY endmenu dummy/Makefile 0000644 00000000542 14722071307 0007343 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the IIO Dummy Driver # obj-$(CONFIG_IIO_SIMPLE_DUMMY) += iio_dummy.o iio_dummy-y := iio_simple_dummy.o iio_dummy-$(CONFIG_IIO_SIMPLE_DUMMY_EVENTS) += iio_simple_dummy_events.o iio_dummy-$(CONFIG_IIO_SIMPLE_DUMMY_BUFFER) += iio_simple_dummy_buffer.o obj-$(CONFIG_IIO_DUMMY_EVGEN) += iio_dummy_evgen.o imu/st_lsm6dsx/Kconfig 0000644 00000001633 14722071307 0010755 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only config IIO_ST_LSM6DSX tristate "ST_LSM6DSx driver for STM 6-axis IMU MEMS sensors" depends on (I2C || SPI || I3C) select IIO_BUFFER select IIO_KFIFO_BUF select IIO_ST_LSM6DSX_I2C if (I2C) select IIO_ST_LSM6DSX_SPI if (SPI_MASTER) select IIO_ST_LSM6DSX_I3C if (I3C) help Say yes here to build support for STMicroelectronics LSM6DSx imu sensor. Supported devices: lsm6ds3, lsm6ds3h, lsm6dsl, lsm6dsm, ism330dlc, lsm6dso, lsm6dsox, asm330lhh, lsm6dsr, lsm6ds3tr-c, ism330dhcx and the accelerometer/gyroscope of lsm9ds1. To compile this driver as a module, choose M here: the module will be called st_lsm6dsx. config IIO_ST_LSM6DSX_I2C tristate depends on IIO_ST_LSM6DSX select REGMAP_I2C config IIO_ST_LSM6DSX_SPI tristate depends on IIO_ST_LSM6DSX select REGMAP_SPI config IIO_ST_LSM6DSX_I3C tristate depends on IIO_ST_LSM6DSX select REGMAP_I3C imu/st_lsm6dsx/Makefile 0000644 00000000501 14722071307 0011103 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only st_lsm6dsx-y := st_lsm6dsx_core.o st_lsm6dsx_buffer.o \ st_lsm6dsx_shub.o obj-$(CONFIG_IIO_ST_LSM6DSX) += st_lsm6dsx.o obj-$(CONFIG_IIO_ST_LSM6DSX_I2C) += st_lsm6dsx_i2c.o obj-$(CONFIG_IIO_ST_LSM6DSX_SPI) += st_lsm6dsx_spi.o obj-$(CONFIG_IIO_ST_LSM6DSX_I3C) += st_lsm6dsx_i3c.o imu/Kconfig 0000644 00000003644 14722071307 0006653 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # IIO imu drivers configuration # # When adding new entries keep the list in alphabetical order menu "Inertial measurement units" config ADIS16400 tristate "Analog Devices ADIS16400 and similar IMU SPI driver" depends on SPI select IIO_ADIS_LIB select IIO_ADIS_LIB_BUFFER if IIO_BUFFER help Say yes here to build support for Analog Devices adis16300, adis16344, adis16350, adis16354, adis16355, adis16360, adis16362, adis16364, adis16365, adis16400 and adis16405 triaxial inertial sensors (adis16400 series also have magnetometers). config ADIS16460 tristate "Analog Devices ADIS16460 and similar IMU driver" depends on SPI select IIO_ADIS_LIB select IIO_ADIS_LIB_BUFFER if IIO_BUFFER help Say yes here to build support for Analog Devices ADIS16460 inertial sensor. To compile this driver as a module, choose M here: the module will be called adis16460. config ADIS16480 tristate "Analog Devices ADIS16480 and similar IMU driver" depends on SPI select IIO_ADIS_LIB select IIO_ADIS_LIB_BUFFER if IIO_BUFFER help Say yes here to build support for Analog Devices ADIS16375, ADIS16480, ADIS16485, ADIS16488 inertial sensors. source "drivers/iio/imu/bmi160/Kconfig" config KMX61 tristate "Kionix KMX61 6-axis accelerometer and magnetometer" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here if you want to build a driver for Kionix KMX61 6-axis accelerometer and magnetometer. To compile this driver as module, choose M here: the module will be called kmx61. source "drivers/iio/imu/inv_mpu6050/Kconfig" source "drivers/iio/imu/st_lsm6dsx/Kconfig" endmenu config IIO_ADIS_LIB tristate help A set of IO helper functions for the Analog Devices ADIS* device family. config IIO_ADIS_LIB_BUFFER bool select IIO_TRIGGERED_BUFFER help A set of buffer helper functions for the Analog Devices ADIS* device family. imu/bmi160/Kconfig 0000644 00000001445 14722071307 0007646 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # BMI160 IMU driver # config BMI160 tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config BMI160_I2C tristate "Bosch BMI160 I2C driver" depends on I2C select BMI160 select REGMAP_I2C help If you say yes here you get support for BMI160 IMU on I2C with accelerometer, gyroscope and external BMG160 magnetometer. This driver can also be built as a module. If so, the module will be called bmi160_i2c. config BMI160_SPI tristate "Bosch BMI160 SPI driver" depends on SPI select BMI160 select REGMAP_SPI help If you say yes here you get support for BMI160 IMU on SPI with accelerometer, gyroscope and external BMG160 magnetometer. This driver can also be built as a module. If so, the module will be called bmi160_spi. imu/bmi160/Makefile 0000644 00000000304 14722071307 0007774 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for Bosch BMI160 IMU # obj-$(CONFIG_BMI160) += bmi160_core.o obj-$(CONFIG_BMI160_I2C) += bmi160_i2c.o obj-$(CONFIG_BMI160_SPI) += bmi160_spi.o imu/inv_mpu6050/Kconfig 0000644 00000001627 14722071307 0010642 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # inv-mpu6050 drivers for Invensense MPU devices and combos # config INV_MPU6050_IIO tristate select IIO_BUFFER select IIO_TRIGGERED_BUFFER config INV_MPU6050_I2C tristate "Invensense MPU6050 devices (I2C)" depends on I2C_MUX select INV_MPU6050_IIO select REGMAP_I2C help This driver supports the Invensense MPU6000/6050/6500/6515, MPU9150/9250/9255 and ICM20608/20602 motion tracking devices over I2C. This driver can be built as a module. The module will be called inv-mpu6050-i2c. config INV_MPU6050_SPI tristate "Invensense MPU6050 devices (SPI)" depends on SPI_MASTER select INV_MPU6050_IIO select REGMAP_SPI help This driver supports the Invensense MPU6000/6050/6500/6515, MPU9150/9250/9255 and ICM20608/20602 motion tracking devices over SPI. This driver can be built as a module. The module will be called inv-mpu6050-spi. imu/inv_mpu6050/Makefile 0000644 00000000610 14722071307 0010766 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for Invensense MPU6050 device. # obj-$(CONFIG_INV_MPU6050_IIO) += inv-mpu6050.o inv-mpu6050-objs := inv_mpu_core.o inv_mpu_ring.o inv_mpu_trigger.o obj-$(CONFIG_INV_MPU6050_I2C) += inv-mpu6050-i2c.o inv-mpu6050-i2c-objs := inv_mpu_i2c.o inv_mpu_acpi.o obj-$(CONFIG_INV_MPU6050_SPI) += inv-mpu6050-spi.o inv-mpu6050-spi-objs := inv_mpu_spi.o imu/Makefile 0000644 00000001023 14722071307 0006775 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for Inertial Measurement Units # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_ADIS16400) += adis16400.o obj-$(CONFIG_ADIS16460) += adis16460.o obj-$(CONFIG_ADIS16480) += adis16480.o adis_lib-y += adis.o adis_lib-$(CONFIG_IIO_ADIS_LIB_BUFFER) += adis_trigger.o adis_lib-$(CONFIG_IIO_ADIS_LIB_BUFFER) += adis_buffer.o obj-$(CONFIG_IIO_ADIS_LIB) += adis_lib.o obj-y += bmi160/ obj-y += inv_mpu6050/ obj-$(CONFIG_KMX61) += kmx61.o obj-y += st_lsm6dsx/ proximity/Kconfig 0000644 00000006617 14722071307 0010130 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Proximity sensors # menu "Lightning sensors" config AS3935 tristate "AS3935 Franklin lightning sensor" select IIO_BUFFER select IIO_TRIGGERED_BUFFER depends on SPI help Say Y here to build SPI interface support for the Austrian Microsystems AS3935 lightning detection sensor. To compile this driver as a module, choose M here: the module will be called as3935 endmenu menu "Proximity and distance sensors" config ISL29501 tristate "Intersil ISL29501 Time Of Flight sensor" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER select IIO_KFIFO_BUF help Say Y here if you want to build a driver for the Intersil ISL29501 Time of Flight sensor. To compile this driver as a module, choose M here: the module will be called isl29501. config LIDAR_LITE_V2 tristate "PulsedLight LIDAR sensor" select IIO_BUFFER select IIO_TRIGGERED_BUFFER depends on I2C help Say Y to build a driver for PulsedLight LIDAR range finding sensor. To compile this driver as a module, choose M here: the module will be called pulsedlight-lite-v2 config MB1232 tristate "MaxSonar I2CXL family ultrasonic sensors" depends on I2C help Say Y to build a driver for the ultrasonic sensors I2CXL of MaxBotix which have an i2c interface. It can be used to measure the distance of objects. Supported types are mb1202, mb1212, mb1222, mb1232, mb1242, mb7040, mb7137 To compile this driver as a module, choose M here: the module will be called mb1232. config RFD77402 tristate "RFD77402 ToF sensor" depends on I2C help Say Y to build a driver for the RFD77402 Time-of-Flight (distance) sensor module with I2C interface. To compile this driver as a module, choose M here: the module will be called rfd77402. config SRF04 tristate "GPIO bitbanged ultrasonic ranger sensor (SRF04, MB1000)" depends on GPIOLIB help Say Y here to build a driver for GPIO bitbanged ultrasonic ranger sensor. This driver can be used to measure the distance of objects. It is using two GPIOs. Actually Supported types are: - Devantech SRF04 - Maxbotix mb1000 - Maxbotix mb1010 - Maxbotix mb1020 - Maxbotix mb1030 - Maxbotix mb1040 To compile this driver as a module, choose M here: the module will be called srf04. config SX9500 tristate "SX9500 Semtech proximity sensor" select IIO_BUFFER select IIO_TRIGGERED_BUFFER select REGMAP_I2C depends on I2C help Say Y here to build a driver for Semtech's SX9500 capacitive proximity/button sensor. To compile this driver as a module, choose M here: the module will be called sx9500. config SRF08 tristate "Devantech SRF02/SRF08/SRF10 ultrasonic ranger sensor" select IIO_BUFFER select IIO_TRIGGERED_BUFFER depends on I2C help Say Y here to build a driver for Devantech SRF02/SRF08/SRF10 ultrasonic ranger sensors with i2c interface. This driver can be used to measure the distance of objects. To compile this driver as a module, choose M here: the module will be called srf08. config VL53L0X_I2C tristate "STMicroelectronics VL53L0X ToF ranger sensor (I2C)" depends on I2C help Say Y here to build a driver for STMicroelectronics VL53L0X ToF ranger sensors with i2c interface. This driver can be used to measure the distance of objects. To compile this driver as a module, choose M here: the module will be called vl53l0x-i2c. endmenu proximity/Makefile 0000644 00000000744 14722071307 0010260 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for IIO proximity sensors # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_AS3935) += as3935.o obj-$(CONFIG_ISL29501) += isl29501.o obj-$(CONFIG_LIDAR_LITE_V2) += pulsedlight-lidar-lite-v2.o obj-$(CONFIG_MB1232) += mb1232.o obj-$(CONFIG_RFD77402) += rfd77402.o obj-$(CONFIG_SRF04) += srf04.o obj-$(CONFIG_SRF08) += srf08.o obj-$(CONFIG_SX9500) += sx9500.o obj-$(CONFIG_VL53L0X_I2C) += vl53l0x-i2c.o pressure/Kconfig 0000644 00000014727 14722071307 0007735 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Pressure drivers # # When adding new entries keep the list in alphabetical order menu "Pressure sensors" config ABP060MG tristate "Honeywell ABP pressure sensor driver" depends on I2C help Say yes here to build support for the Honeywell ABP pressure sensors. To compile this driver as a module, choose M here: the module will be called abp060mg. config BMP280 tristate "Bosch Sensortec BMP180/BMP280 pressure sensor I2C driver" depends on (I2C || SPI_MASTER) select REGMAP select BMP280_I2C if (I2C) select BMP280_SPI if (SPI_MASTER) help Say yes here to build support for Bosch Sensortec BMP180 and BMP280 pressure and temperature sensors. Also supports the BME280 with an additional humidity sensor channel. To compile this driver as a module, choose M here: the core module will be called bmp280 and you will also get bmp280-i2c for I2C and/or bmp280-spi for SPI support. config BMP280_I2C tristate depends on BMP280 depends on I2C select REGMAP_I2C config BMP280_SPI tristate depends on BMP280 depends on SPI_MASTER select REGMAP config IIO_CROS_EC_BARO tristate "ChromeOS EC Barometer Sensor" depends on IIO_CROS_EC_SENSORS_CORE help Say yes here to build support for the Barometer sensor when presented by the ChromeOS EC Sensor hub. To compile this driver as a module, choose M here: the module will be called cros_ec_baro. config DPS310 tristate "Infineon DPS310 pressure and temperature sensor" depends on I2C select REGMAP_I2C help Support for the Infineon DPS310 digital barometric pressure sensor. It can be accessed over I2C bus. This driver can also be built as a module. If so, the module will be called dps310. config HID_SENSOR_PRESS depends on HID_SENSOR_HUB select IIO_BUFFER select IIO_TRIGGERED_BUFFER select HID_SENSOR_IIO_COMMON select HID_SENSOR_IIO_TRIGGER tristate "HID PRESS" help Say yes here to build support for the HID SENSOR Pressure driver To compile this driver as a module, choose M here: the module will be called hid-sensor-press. config HP03 tristate "Hope RF HP03 temperature and pressure sensor driver" depends on I2C select REGMAP_I2C help Say yes here to build support for Hope RF HP03 pressure and temperature sensor. To compile this driver as a module, choose M here: the module will be called hp03. config MPL115 tristate config MPL115_I2C tristate "Freescale MPL115A2 pressure sensor driver" depends on I2C select MPL115 help Say yes here to build support for the Freescale MPL115A2 pressure sensor connected via I2C. To compile this driver as a module, choose M here: the module will be called mpl115_i2c. config MPL115_SPI tristate "Freescale MPL115A1 pressure sensor driver" depends on SPI_MASTER select MPL115 help Say yes here to build support for the Freescale MPL115A1 pressure sensor connected via SPI. To compile this driver as a module, choose M here: the module will be called mpl115_spi. config MPL3115 tristate "Freescale MPL3115A2 pressure sensor driver" depends on I2C select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say yes here to build support for the Freescale MPL3115A2 pressure sensor / altimeter. To compile this driver as a module, choose M here: the module will be called mpl3115. config MS5611 tristate "Measurement Specialties MS5611 pressure sensor driver" select IIO_BUFFER select IIO_TRIGGERED_BUFFER help Say Y here to build support for the Measurement Specialties MS5611, MS5607 pressure and temperature sensors. To compile this driver as a module, choose M here: the module will be called ms5611_core. config MS5611_I2C tristate "support I2C bus connection" depends on I2C && MS5611 help Say Y here to build I2C bus support for MS5611. To compile this driver as a module, choose M here: the module will be called ms5611_i2c. config MS5611_SPI tristate "support SPI bus connection" depends on SPI_MASTER && MS5611 help Say Y here to build SPI bus support for MS5611. To compile this driver as a module, choose M here: the module will be called ms5611_spi. config MS5637 tristate "Measurement Specialties MS5637 pressure & temperature sensor" depends on I2C select IIO_MS_SENSORS_I2C help If you say yes here you get support for the Measurement Specialties MS5637 pressure and temperature sensor. This driver is also used for MS8607 temperature, pressure & humidity sensor This driver can also be built as a module. If so, the module will be called ms5637. config IIO_ST_PRESS tristate "STMicroelectronics pressure sensor Driver" depends on (I2C || SPI_MASTER) && SYSFS select IIO_ST_SENSORS_CORE select IIO_ST_PRESS_I2C if (I2C) select IIO_ST_PRESS_SPI if (SPI_MASTER) select IIO_TRIGGERED_BUFFER if (IIO_BUFFER) help Say yes here to build support for STMicroelectronics pressure sensors: LPS001WP, LPS25H, LPS331AP, LPS22HB, LPS22HH. This driver can also be built as a module. If so, these modules will be created: - st_pressure (core functions for the driver [it is mandatory]); - st_pressure_i2c (necessary for the I2C devices [optional*]); - st_pressure_spi (necessary for the SPI devices [optional*]); (*) one of these is necessary to do something. config IIO_ST_PRESS_I2C tristate depends on IIO_ST_PRESS depends on IIO_ST_SENSORS_I2C config IIO_ST_PRESS_SPI tristate depends on IIO_ST_PRESS depends on IIO_ST_SENSORS_SPI config T5403 tristate "EPCOS T5403 digital barometric pressure sensor driver" depends on I2C help Say yes here to build support for the EPCOS T5403 pressure sensor connected via I2C. To compile this driver as a module, choose M here: the module will be called t5403. config HP206C tristate "HOPERF HP206C precision barometer and altimeter sensor" depends on I2C help Say yes here to build support for the HOPREF HP206C precision barometer and altimeter sensor. This driver can also be built as a module. If so, the module will be called hp206c. config ZPA2326 tristate "Murata ZPA2326 pressure sensor driver" select IIO_BUFFER select IIO_TRIGGERED_BUFFER select REGMAP select ZPA2326_I2C if I2C select ZPA2326_SPI if SPI_MASTER help Say Y here to build support for the Murata ZPA2326 pressure and temperature sensor. To compile this driver as a module, choose M here: the module will be called zpa2326. config ZPA2326_I2C tristate select REGMAP_I2C config ZPA2326_SPI tristate select REGMAP_SPI endmenu pressure/Makefile 0000644 00000002332 14722071307 0010057 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for industrial I/O pressure drivers # # When adding new entries keep the list in alphabetical order obj-$(CONFIG_ABP060MG) += abp060mg.o obj-$(CONFIG_BMP280) += bmp280.o bmp280-objs := bmp280-core.o bmp280-regmap.o obj-$(CONFIG_BMP280_I2C) += bmp280-i2c.o obj-$(CONFIG_BMP280_SPI) += bmp280-spi.o obj-$(CONFIG_DPS310) += dps310.o obj-$(CONFIG_IIO_CROS_EC_BARO) += cros_ec_baro.o obj-$(CONFIG_HID_SENSOR_PRESS) += hid-sensor-press.o obj-$(CONFIG_HP03) += hp03.o obj-$(CONFIG_MPL115) += mpl115.o obj-$(CONFIG_MPL115_I2C) += mpl115_i2c.o obj-$(CONFIG_MPL115_SPI) += mpl115_spi.o obj-$(CONFIG_MPL3115) += mpl3115.o obj-$(CONFIG_MS5611) += ms5611_core.o obj-$(CONFIG_MS5611_I2C) += ms5611_i2c.o obj-$(CONFIG_MS5611_SPI) += ms5611_spi.o obj-$(CONFIG_MS5637) += ms5637.o obj-$(CONFIG_IIO_ST_PRESS) += st_pressure.o st_pressure-y := st_pressure_core.o st_pressure-$(CONFIG_IIO_BUFFER) += st_pressure_buffer.o obj-$(CONFIG_T5403) += t5403.o obj-$(CONFIG_HP206C) += hp206c.o obj-$(CONFIG_ZPA2326) += zpa2326.o obj-$(CONFIG_ZPA2326_I2C) += zpa2326_i2c.o obj-$(CONFIG_ZPA2326_SPI) += zpa2326_spi.o obj-$(CONFIG_IIO_ST_PRESS_I2C) += st_pressure_i2c.o obj-$(CONFIG_IIO_ST_PRESS_SPI) += st_pressure_spi.o
| ver. 1.4 |
Github
|
.
| PHP 7.4.3-4ubuntu2.24 | Генерация страницы: 0.01 |
proxy
|
phpinfo
|
Настройка