4 # When adding new entries keep the list in alphabetical order
6 menu "Analog to digital converters"
11 select IIO_TRIGGERED_BUFFER
14 tristate "Analog Devices AD7265/AD7266 ADC driver"
18 select IIO_TRIGGERED_BUFFER
20 Say yes here to build support for Analog Devices AD7265 and AD7266
24 tristate "Analog Devices AD7291 ADC driver"
27 Say yes here to build support for Analog Devices AD7291
28 8 Channel ADC with temperature sensor.
30 To compile this driver as a module, choose M here: the
31 module will be called ad7291.
34 tristate "Analog Devices AD7298 ADC driver"
37 select IIO_TRIGGERED_BUFFER
39 Say yes here to build support for Analog Devices AD7298
40 8 Channel ADC with temperature sensor.
42 To compile this driver as a module, choose M here: the
43 module will be called ad7298.
46 tristate "Analog Devices AD7476 and similar 1-channel ADCs driver"
49 select IIO_TRIGGERED_BUFFER
51 Say yes here to build support for Analog Devices AD7273, AD7274, AD7276,
52 AD7277, AD7278, AD7475, AD7476, AD7477, AD7478, AD7466, AD7467, AD7468,
53 AD7495, AD7910, AD7920, AD7920 SPI analog to digital converters (ADC).
55 If unsure, say N (but it's safe to say "Y").
57 To compile this driver as a module, choose M here: the
58 module will be called ad7476.
61 tristate "Analog Devices AD7791 ADC driver"
65 Say yes here to build support for Analog Devices AD7787, AD7788, AD7789,
66 AD7790 and AD7791 SPI analog to digital converters (ADC). If unsure, say
67 N (but it is safe to say "Y").
69 To compile this driver as a module, choose M here: the module will be
73 tristate "Analog Devices AD7793 and similar ADCs driver"
77 Say yes here to build support for Analog Devices AD7785, AD7792, AD7793,
78 AD7794 and AD7795 SPI analog to digital converters (ADC).
79 If unsure, say N (but it's safe to say "Y").
81 To compile this driver as a module, choose M here: the
82 module will be called AD7793.
85 tristate "Analog Devices AD7887 ADC driver"
88 select IIO_TRIGGERED_BUFFER
90 Say yes here to build support for Analog Devices
91 AD7887 SPI analog to digital converter (ADC).
92 If unsure, say N (but it's safe to say "Y").
94 To compile this driver as a module, choose M here: the
95 module will be called ad7887.
98 tristate "Analog Devices AD7923 and similar ADCs driver"
101 select IIO_TRIGGERED_BUFFER
103 Say yes here to build support for Analog Devices
104 AD7904, AD7914, AD7923, AD7924 4 Channel ADCs.
106 To compile this driver as a module, choose M here: the
107 module will be called ad7923.
110 tristate "Analog Devices AD799x ADC driver"
113 select IIO_TRIGGERED_BUFFER
115 Say yes here to build support for Analog Devices:
116 ad7991, ad7995, ad7999, ad7992, ad7993, ad7994, ad7997, ad7998
117 i2c analog to digital converters (ADC). Provides direct access
121 tristate "Atmel AT91 ADC"
125 select IIO_TRIGGERED_BUFFER
128 Say yes here to build support for Atmel AT91 ADC.
131 tristate "X-Powers AXP288 ADC driver"
132 depends on MFD_AXP20X
134 Say yes here to have support for X-Powers power management IC (PMIC) ADC
135 device. Depending on platform configuration, this general purpose ADC can
136 be used for sampling sensors such as thermal resistors.
139 tristate "Exynos ADC driver support"
140 depends on ARCH_EXYNOS || ARCH_S3C24XX || ARCH_S3C64XX || (OF && COMPILE_TEST)
142 Core support for the ADC block found in the Samsung EXYNOS series
143 of SoCs for drivers such as the touchscreen and hwmon to use to share
147 tristate "LP8788 ADC driver"
148 depends on MFD_LP8788
150 Say yes here to build support for TI LP8788 ADC.
153 tristate "Maxim max1027 ADC driver"
156 select IIO_TRIGGERED_BUFFER
158 Say yes here to build support for Maxim SPI ADC models
159 max1027, max1029 and max1031.
162 tristate "Maxim max1363 ADC driver"
165 select IIO_TRIGGERED_BUFFER
167 Say yes here to build support for many Maxim i2c analog to digital
168 converters (ADC). (max1361, max1362, max1363, max1364, max1036,
169 max1037, max1038, max1039, max1136, max1136, max1137, max1138,
170 max1139, max1236, max1237, max11238, max1239, max11600, max11601,
171 max11602, max11603, max11604, max11605, max11606, max11607,
172 max11608, max11609, max11610, max11611, max11612, max11613,
173 max11614, max11615, max11616, max11617, max11644, max11645,
174 max11646, max11647) Provides direct access via sysfs and buffered
175 data via the iio dev interface.
178 tristate "Microchip Technology MCP3204/08"
181 Say yes here to build support for Microchip Technology's MCP3204 or
182 MCP3208 analog to digital converter.
184 This driver can also be built as a module. If so, the module will be
188 tristate "Microchip Technology MCP3422/3/4/6/7/8 driver"
191 Say yes here to build support for Microchip Technology's
192 MCP3422, MCP3423, MCP3424, MCP3426, MCP3427 or MCP3428
193 analog to digital converters.
195 This driver can also be built as a module. If so, the module will be
199 tristate "MEN 16z188 ADC IP Core support"
202 Say yes here to enable support for the MEN 16z188 ADC IP-Core on a MCB
205 This driver can also be built as a module. If so, the module will be
209 tristate "Nuvoton NAU7802 ADC driver"
212 Say yes here to build support for Nuvoton NAU7802 ADC.
214 To compile this driver as a module, choose M here: the
215 module will be called nau7802.
217 config ROCKCHIP_SARADC
218 tristate "Rockchip SARADC driver"
219 depends on ARCH_ROCKCHIP || (ARM && COMPILE_TEST)
221 Say yes here to build support for the SARADC found in SoCs from
224 To compile this driver as a module, choose M here: the
225 module will be called rockchip_saradc.
228 tristate "Texas Instruments ADC081C021/027"
231 If you say yes here you get support for Texas Instruments ADC081C021
232 and ADC081C027 ADC chips.
234 This driver can also be built as a module. If so, the module will be
238 tristate "Texas Instruments ADC128S052"
241 If you say yes here you get support for Texas Instruments ADC128S052
244 This driver can also be built as a module. If so, the module will be
245 called ti-adc128s052.
248 tristate "TI's AM335X ADC driver"
249 depends on MFD_TI_AM335X_TSCADC
253 Say yes here to build support for Texas Instruments ADC
254 driver which is also a MFD client.
257 tristate "TWL4030 MADC (Monitoring A/D Converter)"
258 depends on TWL4030_CORE
260 This driver provides support for Triton TWL4030-MADC. The
261 driver supports both RT and SW conversion methods.
263 This driver can also be built as a module. If so, the module will be
267 tristate "TWL6030 GPADC (General Purpose A/D Converter) Support"
268 depends on TWL4030_CORE
271 Say yes here if you want support for the TWL6030/TWL6032 General
272 Purpose A/D Converter. This will add support for battery type
273 detection, battery voltage and temperature measurement, die
274 temperature measurement, system supply voltage, audio accessory,
277 This driver can also be built as a module. If so, the module will be
278 called twl6030-gpadc.
281 tristate "Freescale vf610 ADC driver"
284 Say yes here to support for Vybrid board analog-to-digital converter.
285 Since the IP is used for i.MX6SLX, the driver also support i.MX6SLX.
287 This driver can also be built as a module. If so, the module will be
290 config VIPERBOARD_ADC
291 tristate "Viperboard ADC support"
292 depends on MFD_VIPERBOARD && USB
294 Say yes here to access the ADC part of the Nano River
295 Technologies Viperboard.
298 tristate "Xilinx XADC driver"
299 depends on ARCH_ZYNQ || MICROBLAZE || COMPILE_TEST
302 select IIO_TRIGGERED_BUFFER
304 Say yes here to have support for the Xilinx XADC. The driver does support
305 both the ZYNQ interface to the XADC as well as the AXI-XADC interface.
307 The driver can also be build as a module. If so, the module will be called