Kconfig (83bffbce745795572d20f0109395cb61690c6dcf) Kconfig (f5bae2642e3df716d2bb7bcffdf51e7a286e885e)
1#
2# Hardware monitoring chip drivers configuration
3#
4
5menuconfig HWMON
6 tristate "Hardware Monitoring support"
7 depends on HAS_IOMEM
8 default y

--- 694 unchanged lines hidden (view full) ---

703 tristate "Maxim MAX1111 Multichannel, Serial 8-bit ADC chip"
704 depends on SPI_MASTER
705 help
706 Say y here to support Maxim's MAX1111 ADC chips.
707
708 This driver can also be built as a module. If so, the module
709 will be called max1111.
710
1#
2# Hardware monitoring chip drivers configuration
3#
4
5menuconfig HWMON
6 tristate "Hardware Monitoring support"
7 depends on HAS_IOMEM
8 default y

--- 694 unchanged lines hidden (view full) ---

703 tristate "Maxim MAX1111 Multichannel, Serial 8-bit ADC chip"
704 depends on SPI_MASTER
705 help
706 Say y here to support Maxim's MAX1111 ADC chips.
707
708 This driver can also be built as a module. If so, the module
709 will be called max1111.
710
711config SENSORS_MAX16065
712 tristate "Maxim MAX16065 System Manager and compatibles"
713 depends on I2C
714 help
715 If you say yes here you get support for hardware monitoring
716 capabilities of the following Maxim System Manager chips.
717 MAX16065
718 MAX16066
719 MAX16067
720 MAX16068
721 MAX16070
722 MAX16071
723
724 This driver can also be built as a module. If so, the module
725 will be called max16065.
726
711config SENSORS_MAX1619
712 tristate "Maxim MAX1619 sensor chip"
713 depends on I2C
714 help
715 If you say yes here you get support for MAX1619 sensor chip.
716
717 This driver can also be built as a module. If so, the module
718 will be called max1619.

--- 599 unchanged lines hidden --- 		727config SENSORS_MAX1619
728 tristate "Maxim MAX1619 sensor chip"
729 depends on I2C
730 help
731 If you say yes here you get support for MAX1619 sensor chip.
732
733 This driver can also be built as a module. If so, the module
734 will be called max1619.

--- 599 unchanged lines hidden ---