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

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

680 tristate "Maxim MAX1619 sensor chip"
681 depends on I2C
682 help
683 If you say yes here you get support for MAX1619 sensor chip.
684
685 This driver can also be built as a module. If so, the module
686 will be called max1619.
687
1#
2# Hardware monitoring chip drivers configuration
3#
4
5menuconfig HWMON
6 tristate "Hardware Monitoring support"
7 depends on HAS_IOMEM
8 default y

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

680 tristate "Maxim MAX1619 sensor chip"
681 depends on I2C
682 help
683 If you say yes here you get support for MAX1619 sensor chip.
684
685 This driver can also be built as a module. If so, the module
686 will be called max1619.
687
688config SENSORS_MAX6639
689 tristate "Maxim MAX6639 sensor chip"
690 depends on I2C && EXPERIMENTAL
691 help
692 If you say yes here you get support for the MAX6639
693 sensor chips.
694
695 This driver can also be built as a module. If so, the module
696 will be called max6639.
697
688config SENSORS_MAX6650
689 tristate "Maxim MAX6650 sensor chip"
690 depends on I2C && EXPERIMENTAL
691 help
692 If you say yes here you get support for the MAX6650 / MAX6651
693 sensor chips.
694
695 This driver can also be built as a module. If so, the module

--- 548 unchanged lines hidden --- 		698config SENSORS_MAX6650
699 tristate "Maxim MAX6650 sensor chip"
700 depends on I2C && EXPERIMENTAL
701 help
702 If you say yes here you get support for the MAX6650 / MAX6651
703 sensor chips.
704
705 This driver can also be built as a module. If so, the module

--- 548 unchanged lines hidden ---