diff options
author | Jean Delvare <khali@linux-fr.org> | 2009-09-15 11:18:13 -0400 |
---|---|---|
committer | Jean Delvare <khali@linux-fr.org> | 2009-09-15 11:18:13 -0400 |
commit | 61cba5c244bd52e91c01e9f79abba30e54f68dd8 (patch) | |
tree | d48447931151df466aaf8ddb71de485711bea581 /drivers/hwmon/Kconfig | |
parent | 86855b0c1fd75338c67cabbf85d64d033612c47b (diff) |
hwmon: Clearly mark ACPI drivers as such
Now that we have ACPI-based hardware monitoring drivers, and we will
start telling users to use them instead of native drivers when I/O
resources conflict, I think it would be good to clearly mark ACPI
drivers as such in Kconfig.
Also, in the case of monolithic kernels, I think the ACPI drivers
should take precedence over native drivers, so they should be listed
first in Makefile.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Luca Tettamanti <kronos.it@gmail.com>
Diffstat (limited to 'drivers/hwmon/Kconfig')
-rw-r--r-- | drivers/hwmon/Kconfig | 100 |
1 files changed, 54 insertions, 46 deletions
diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig index ee57a4a2cd72..461abb1e273a 100644 --- a/drivers/hwmon/Kconfig +++ b/drivers/hwmon/Kconfig | |||
@@ -28,6 +28,17 @@ config HWMON_VID | |||
28 | tristate | 28 | tristate |
29 | default n | 29 | default n |
30 | 30 | ||
31 | config HWMON_DEBUG_CHIP | ||
32 | bool "Hardware Monitoring Chip debugging messages" | ||
33 | default n | ||
34 | help | ||
35 | Say Y here if you want the I2C chip drivers to produce a bunch of | ||
36 | debug messages to the system log. Select this if you are having | ||
37 | a problem with I2C support and want to see more of what is going | ||
38 | on. | ||
39 | |||
40 | comment "Native drivers" | ||
41 | |||
31 | config SENSORS_ABITUGURU | 42 | config SENSORS_ABITUGURU |
32 | tristate "Abit uGuru (rev 1 & 2)" | 43 | tristate "Abit uGuru (rev 1 & 2)" |
33 | depends on X86 && EXPERIMENTAL | 44 | depends on X86 && EXPERIMENTAL |
@@ -248,18 +259,6 @@ config SENSORS_ASB100 | |||
248 | This driver can also be built as a module. If so, the module | 259 | This driver can also be built as a module. If so, the module |
249 | will be called asb100. | 260 | will be called asb100. |
250 | 261 | ||
251 | config SENSORS_ATK0110 | ||
252 | tristate "ASUS ATK0110 ACPI hwmon" | ||
253 | depends on X86 && ACPI && EXPERIMENTAL | ||
254 | help | ||
255 | If you say yes here you get support for the ACPI hardware | ||
256 | monitoring interface found in many ASUS motherboards. This | ||
257 | driver will provide readings of fans, voltages and temperatures | ||
258 | through the system firmware. | ||
259 | |||
260 | This driver can also be built as a module. If so, the module | ||
261 | will be called asus_atk0110. | ||
262 | |||
263 | config SENSORS_ATXP1 | 262 | config SENSORS_ATXP1 |
264 | tristate "Attansic ATXP1 VID controller" | 263 | tristate "Attansic ATXP1 VID controller" |
265 | depends on I2C && EXPERIMENTAL | 264 | depends on I2C && EXPERIMENTAL |
@@ -974,34 +973,6 @@ config SENSORS_HDAPS | |||
974 | Say Y here if you have an applicable laptop and want to experience | 973 | Say Y here if you have an applicable laptop and want to experience |
975 | the awesome power of hdaps. | 974 | the awesome power of hdaps. |
976 | 975 | ||
977 | config SENSORS_LIS3LV02D | ||
978 | tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer" | ||
979 | depends on ACPI && INPUT | ||
980 | select INPUT_POLLDEV | ||
981 | select NEW_LEDS | ||
982 | select LEDS_CLASS | ||
983 | default n | ||
984 | help | ||
985 | This driver provides support for the LIS3LV02Dx accelerometer. In | ||
986 | particular, it can be found in a number of HP laptops, which have the | ||
987 | "Mobile Data Protection System 3D" or "3D DriveGuard" feature. On such | ||
988 | systems the driver should load automatically (via ACPI). The | ||
989 | accelerometer might also be found in other systems, connected via SPI | ||
990 | or I2C. The accelerometer data is readable via | ||
991 | /sys/devices/platform/lis3lv02d. | ||
992 | |||
993 | This driver also provides an absolute input class device, allowing | ||
994 | the laptop to act as a pinball machine-esque joystick. On HP laptops, | ||
995 | if the led infrastructure is activated, support for a led indicating | ||
996 | disk protection will be provided as hp:red:hddprotection. | ||
997 | |||
998 | This driver can also be built as modules. If so, the core module | ||
999 | will be called lis3lv02d and a specific module for HP laptops will be | ||
1000 | called hp_accel. | ||
1001 | |||
1002 | Say Y here if you have an applicable laptop and want to experience | ||
1003 | the awesome power of lis3lv02d. | ||
1004 | |||
1005 | config SENSORS_LIS3_SPI | 976 | config SENSORS_LIS3_SPI |
1006 | tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer (SPI)" | 977 | tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer (SPI)" |
1007 | depends on !ACPI && SPI_MASTER && INPUT | 978 | depends on !ACPI && SPI_MASTER && INPUT |
@@ -1044,13 +1015,50 @@ config SENSORS_APPLESMC | |||
1044 | Say Y here if you have an applicable laptop and want to experience | 1015 | Say Y here if you have an applicable laptop and want to experience |
1045 | the awesome power of applesmc. | 1016 | the awesome power of applesmc. |
1046 | 1017 | ||
1047 | config HWMON_DEBUG_CHIP | 1018 | if ACPI |
1048 | bool "Hardware Monitoring Chip debugging messages" | 1019 | |
1020 | comment "ACPI drivers" | ||
1021 | |||
1022 | config SENSORS_ATK0110 | ||
1023 | tristate "ASUS ATK0110" | ||
1024 | depends on X86 && EXPERIMENTAL | ||
1025 | help | ||
1026 | If you say yes here you get support for the ACPI hardware | ||
1027 | monitoring interface found in many ASUS motherboards. This | ||
1028 | driver will provide readings of fans, voltages and temperatures | ||
1029 | through the system firmware. | ||
1030 | |||
1031 | This driver can also be built as a module. If so, the module | ||
1032 | will be called asus_atk0110. | ||
1033 | |||
1034 | config SENSORS_LIS3LV02D | ||
1035 | tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer" | ||
1036 | depends on INPUT | ||
1037 | select INPUT_POLLDEV | ||
1038 | select NEW_LEDS | ||
1039 | select LEDS_CLASS | ||
1049 | default n | 1040 | default n |
1050 | help | 1041 | help |
1051 | Say Y here if you want the I2C chip drivers to produce a bunch of | 1042 | This driver provides support for the LIS3LV02Dx accelerometer. In |
1052 | debug messages to the system log. Select this if you are having | 1043 | particular, it can be found in a number of HP laptops, which have the |
1053 | a problem with I2C support and want to see more of what is going | 1044 | "Mobile Data Protection System 3D" or "3D DriveGuard" feature. On such |
1054 | on. | 1045 | systems the driver should load automatically (via ACPI). The |
1046 | accelerometer might also be found in other systems, connected via SPI | ||
1047 | or I2C. The accelerometer data is readable via | ||
1048 | /sys/devices/platform/lis3lv02d. | ||
1049 | |||
1050 | This driver also provides an absolute input class device, allowing | ||
1051 | the laptop to act as a pinball machine-esque joystick. On HP laptops, | ||
1052 | if the led infrastructure is activated, support for a led indicating | ||
1053 | disk protection will be provided as hp:red:hddprotection. | ||
1054 | |||
1055 | This driver can also be built as modules. If so, the core module | ||
1056 | will be called lis3lv02d and a specific module for HP laptops will be | ||
1057 | called hp_accel. | ||
1058 | |||
1059 | Say Y here if you have an applicable laptop and want to experience | ||
1060 | the awesome power of lis3lv02d. | ||
1061 | |||
1062 | endif # ACPI | ||
1055 | 1063 | ||
1056 | endif # HWMON | 1064 | endif # HWMON |