diff options
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/feature-removal-schedule.txt | 7 | ||||
| -rw-r--r-- | Documentation/hwmon/adt7473 | 2 | ||||
| -rw-r--r-- | Documentation/hwmon/adt7475 | 204 | ||||
| -rw-r--r-- | Documentation/hwmon/f71882fg | 10 | ||||
| -rw-r--r-- | Documentation/hwmon/it87 | 1 | ||||
| -rw-r--r-- | Documentation/hwmon/mc13783-adc | 50 | ||||
| -rw-r--r-- | Documentation/hwmon/sysfs-interface | 11 | ||||
| -rw-r--r-- | Documentation/hwmon/w83627hf | 29 |
8 files changed, 222 insertions, 92 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt index 591e94448e63..2a4d77946c7d 100644 --- a/Documentation/feature-removal-schedule.txt +++ b/Documentation/feature-removal-schedule.txt | |||
| @@ -483,3 +483,10 @@ Why: With the recent innovations in CPU hardware acceleration technologies | |||
| 483 | Who: Alok N Kataria <akataria@vmware.com> | 483 | Who: Alok N Kataria <akataria@vmware.com> |
| 484 | 484 | ||
| 485 | ---------------------------- | 485 | ---------------------------- |
| 486 | |||
| 487 | What: adt7473 hardware monitoring driver | ||
| 488 | When: February 2010 | ||
| 489 | Why: Obsoleted by the adt7475 driver. | ||
| 490 | Who: Jean Delvare <khali@linux-fr.org> | ||
| 491 | |||
| 492 | --------------------------- | ||
diff --git a/Documentation/hwmon/adt7473 b/Documentation/hwmon/adt7473 index 1cbf671822e2..446612bd1fb9 100644 --- a/Documentation/hwmon/adt7473 +++ b/Documentation/hwmon/adt7473 | |||
| @@ -9,6 +9,8 @@ Supported chips: | |||
| 9 | 9 | ||
| 10 | Author: Darrick J. Wong | 10 | Author: Darrick J. Wong |
| 11 | 11 | ||
| 12 | This driver is depreacted, please use the adt7475 driver instead. | ||
| 13 | |||
| 12 | Description | 14 | Description |
| 13 | ----------- | 15 | ----------- |
| 14 | 16 | ||
diff --git a/Documentation/hwmon/adt7475 b/Documentation/hwmon/adt7475 index a2b1abec850e..0502f2b464e1 100644 --- a/Documentation/hwmon/adt7475 +++ b/Documentation/hwmon/adt7475 | |||
| @@ -1,87 +1,117 @@ | |||
| 1 | This describes the interface for the ADT7475 driver: | 1 | Kernel driver adt7475 |
| 2 | 2 | ===================== | |
| 3 | (there are 4 fans, numbered fan1 to fan4): | 3 | |
| 4 | 4 | Supported chips: | |
| 5 | fanX_input Read the current speed of the fan (in RPMs) | 5 | * Analog Devices ADT7473 |
| 6 | fanX_min Read/write the minimum speed of the fan. Dropping | 6 | Prefix: 'adt7473' |
| 7 | below this sets an alarm. | 7 | Addresses scanned: I2C 0x2C, 0x2D, 0x2E |
| 8 | 8 | Datasheet: Publicly available at the On Semiconductors website | |
| 9 | (there are three PWMs, numbered pwm1 to pwm3): | 9 | * Analog Devices ADT7475 |
| 10 | 10 | Prefix: 'adt7475' | |
| 11 | pwmX Read/write the current duty cycle of the PWM. Writes | 11 | Addresses scanned: I2C 0x2E |
| 12 | only have effect when auto mode is turned off (see | 12 | Datasheet: Publicly available at the On Semiconductors website |
| 13 | below). Range is 0 - 255. | 13 | * Analog Devices ADT7476 |
| 14 | 14 | Prefix: 'adt7476' | |
| 15 | pwmX_enable Fan speed control method: | 15 | Addresses scanned: I2C 0x2C, 0x2D, 0x2E |
| 16 | 16 | Datasheet: Publicly available at the On Semiconductors website | |
| 17 | 0 - No control (fan at full speed) | 17 | * Analog Devices ADT7490 |
| 18 | 1 - Manual fan speed control (using pwm[1-*]) | 18 | Prefix: 'adt7490' |
| 19 | 2 - Automatic fan speed control | 19 | Addresses scanned: I2C 0x2C, 0x2D, 0x2E |
| 20 | 20 | Datasheet: Publicly available at the On Semiconductors website | |
| 21 | pwmX_auto_channels_temp Select which channels affect this PWM | 21 | |
| 22 | 22 | Authors: | |
| 23 | 1 - TEMP1 controls PWM | 23 | Jordan Crouse |
| 24 | 2 - TEMP2 controls PWM | 24 | Hans de Goede |
| 25 | 4 - TEMP3 controls PWM | 25 | Darrick J. Wong (documentation) |
| 26 | 6 - TEMP2 and TEMP3 control PWM | 26 | Jean Delvare |
| 27 | 7 - All three inputs control PWM | 27 | |
| 28 | 28 | ||
| 29 | pwmX_freq Read/write the PWM frequency in Hz. The number | 29 | Description |
| 30 | should be one of the following: | 30 | ----------- |
| 31 | 31 | ||
| 32 | 11 Hz | 32 | This driver implements support for the Analog Devices ADT7473, ADT7475, |
| 33 | 14 Hz | 33 | ADT7476 and ADT7490 chip family. The ADT7473 and ADT7475 differ only in |
| 34 | 22 Hz | 34 | minor details. The ADT7476 has additional features, including extra voltage |
| 35 | 29 Hz | 35 | measurement inputs and VID support. The ADT7490 also has additional |
| 36 | 35 Hz | 36 | features, including extra voltage measurement inputs and PECI support. All |
| 37 | 44 Hz | 37 | the supported chips will be collectively designed by the name "ADT747x" in |
| 38 | 58 Hz | 38 | the rest of this document. |
| 39 | 88 Hz | 39 | |
| 40 | 40 | The ADT747x uses the 2-wire interface compatible with the SMBus 2.0 | |
| 41 | pwmX_auto_point1_pwm Read/write the minimum PWM duty cycle in automatic mode | 41 | specification. Using an analog to digital converter it measures three (3) |
| 42 | 42 | temperatures and two (2) or more voltages. It has four (4) 16-bit counters | |
| 43 | pwmX_auto_point2_pwm Read/write the maximum PWM duty cycle in automatic mode | 43 | for measuring fan speed. There are three (3) PWM outputs that can be used |
| 44 | 44 | to control fan speed. | |
| 45 | (there are three temperature settings numbered temp1 to temp3): | 45 | |
| 46 | 46 | A sophisticated control system for the PWM outputs is designed into the | |
| 47 | tempX_input Read the current temperature. The value is in milli | 47 | ADT747x that allows fan speed to be adjusted automatically based on any of the |
| 48 | degrees of Celsius. | 48 | three temperature sensors. Each PWM output is individually adjustable and |
| 49 | 49 | programmable. Once configured, the ADT747x will adjust the PWM outputs in | |
| 50 | tempX_max Read/write the upper temperature limit - exceeding this | 50 | response to the measured temperatures without further host intervention. |
| 51 | will cause an alarm. | 51 | This feature can also be disabled for manual control of the PWM's. |
| 52 | 52 | ||
| 53 | tempX_min Read/write the lower temperature limit - exceeding this | 53 | Each of the measured inputs (voltage, temperature, fan speed) has |
| 54 | will cause an alarm. | 54 | corresponding high/low limit values. The ADT747x will signal an ALARM if |
| 55 | 55 | any measured value exceeds either limit. | |
| 56 | tempX_offset Read/write the temperature adjustment offset | 56 | |
| 57 | 57 | The ADT747x samples all inputs continuously. The driver will not read | |
| 58 | tempX_crit Read/write the THERM limit for remote1. | 58 | the registers more often than once every other second. Further, |
| 59 | 59 | configuration data is only read once per minute. | |
| 60 | tempX_crit_hyst Set the temperature value below crit where the | 60 | |
| 61 | fans will stay on - this helps drive the temperature | 61 | Chip Differences Summary |
| 62 | low enough so it doesn't stay near the edge and | 62 | ------------------------ |
| 63 | cause THERM to keep tripping. | 63 | |
| 64 | 64 | ADT7473: | |
| 65 | tempX_auto_point1_temp Read/write the minimum temperature where the fans will | 65 | * 2 voltage inputs |
| 66 | turn on in automatic mode. | 66 | * system acoustics optimizations (not implemented) |
| 67 | 67 | ||
| 68 | tempX_auto_point2_temp Read/write the maximum temperature over which the fans | 68 | ADT7475: |
| 69 | will run in automatic mode. tempX_auto_point1_temp | 69 | * 2 voltage inputs |
| 70 | and tempX_auto_point2_temp together define the | 70 | |
| 71 | range of automatic control. | 71 | ADT7476: |
| 72 | 72 | * 5 voltage inputs | |
| 73 | tempX_alarm Read a 1 if the max/min alarm is set | 73 | * VID support |
| 74 | tempX_fault Read a 1 if either temp1 or temp3 diode has a fault | 74 | |
| 75 | 75 | ADT7490: | |
| 76 | (There are two voltage settings, in1 and in2): | 76 | * 6 voltage inputs |
| 77 | 77 | * 1 Imon input (not implemented) | |
| 78 | inX_input Read the current voltage on VCC. Value is in | 78 | * PECI support (not implemented) |
| 79 | millivolts. | 79 | * 2 GPIO pins (not implemented) |
| 80 | 80 | * system acoustics optimizations (not implemented) | |
| 81 | inX_min read/write the minimum voltage limit. | 81 | |
| 82 | Dropping below this causes an alarm. | 82 | Special Features |
| 83 | 83 | ---------------- | |
| 84 | inX_max read/write the maximum voltage limit. | 84 | |
| 85 | Exceeding this causes an alarm. | 85 | The ADT747x has a 10-bit ADC and can therefore measure temperatures |
| 86 | 86 | with a resolution of 0.25 degree Celsius. Temperature readings can be | |
| 87 | inX_alarm Read a 1 if the max/min alarm is set. | 87 | configured either for two's complement format or "Offset 64" format, |
| 88 | wherein 64 is subtracted from the raw value to get the temperature value. | ||
| 89 | |||
| 90 | The datasheet is very detailed and describes a procedure for determining | ||
| 91 | an optimal configuration for the automatic PWM control. | ||
| 92 | |||
| 93 | Fan Speed Control | ||
| 94 | ----------------- | ||
| 95 | |||
| 96 | The driver exposes two trip points per PWM channel. | ||
| 97 | |||
| 98 | point1: Set the PWM speed at the lower temperature bound | ||
| 99 | point2: Set the PWM speed at the higher temperature bound | ||
| 100 | |||
| 101 | The ADT747x will scale the PWM linearly between the lower and higher PWM | ||
| 102 | speed when the temperature is between the two temperature boundaries. | ||
| 103 | Temperature boundaries are associated to temperature channels rather than | ||
| 104 | PWM outputs, and a given PWM output can be controlled by several temperature | ||
| 105 | channels. As a result, the ADT747x may compute more than one PWM value | ||
| 106 | for a channel at a given time, in which case the maximum value (fastest | ||
| 107 | fan speed) is applied. PWM values range from 0 (off) to 255 (full speed). | ||
| 108 | |||
| 109 | Fan speed may be set to maximum when the temperature sensor associated with | ||
| 110 | the PWM control exceeds temp#_max. | ||
| 111 | |||
| 112 | Notes | ||
| 113 | ----- | ||
| 114 | |||
| 115 | The nVidia binary driver presents an ADT7473 chip via an on-card i2c bus. | ||
| 116 | Unfortunately, they fail to set the i2c adapter class, so this driver may | ||
| 117 | fail to find the chip until the nvidia driver is patched. | ||
diff --git a/Documentation/hwmon/f71882fg b/Documentation/hwmon/f71882fg index bee4c30bc1e2..a7952c2bd959 100644 --- a/Documentation/hwmon/f71882fg +++ b/Documentation/hwmon/f71882fg | |||
| @@ -14,6 +14,10 @@ Supported chips: | |||
| 14 | Prefix: 'f71882fg' | 14 | Prefix: 'f71882fg' |
| 15 | Addresses scanned: none, address read from Super I/O config space | 15 | Addresses scanned: none, address read from Super I/O config space |
| 16 | Datasheet: Available from the Fintek website | 16 | Datasheet: Available from the Fintek website |
| 17 | * Fintek F71889FG | ||
| 18 | Prefix: 'f71889fg' | ||
| 19 | Addresses scanned: none, address read from Super I/O config space | ||
| 20 | Datasheet: Should become available on the Fintek website soon | ||
| 17 | * Fintek F8000 | 21 | * Fintek F8000 |
| 18 | Prefix: 'f8000' | 22 | Prefix: 'f8000' |
| 19 | Addresses scanned: none, address read from Super I/O config space | 23 | Addresses scanned: none, address read from Super I/O config space |
| @@ -51,6 +55,12 @@ supported. The right one to use depends on external circuitry on the | |||
| 51 | motherboard, so the driver assumes that the BIOS set the method | 55 | motherboard, so the driver assumes that the BIOS set the method |
| 52 | properly. | 56 | properly. |
| 53 | 57 | ||
| 58 | Note that the lowest numbered temperature zone trip point corresponds to | ||
| 59 | to the border between the highest and one but highest temperature zones, and | ||
| 60 | vica versa. So the temperature zone trip points 1-4 (or 1-2) go from high temp | ||
| 61 | to low temp! This is how things are implemented in the IC, and the driver | ||
| 62 | mimicks this. | ||
| 63 | |||
| 54 | There are 2 modes to specify the speed of the fan, PWM duty cycle (or DC | 64 | There are 2 modes to specify the speed of the fan, PWM duty cycle (or DC |
| 55 | voltage) mode, where 0-100% duty cycle (0-100% of 12V) is specified. And RPM | 65 | voltage) mode, where 0-100% duty cycle (0-100% of 12V) is specified. And RPM |
| 56 | mode where the actual RPM of the fan (as measured) is controlled and the speed | 66 | mode where the actual RPM of the fan (as measured) is controlled and the speed |
diff --git a/Documentation/hwmon/it87 b/Documentation/hwmon/it87 index 659315d98e00..f9ba96c0ac4a 100644 --- a/Documentation/hwmon/it87 +++ b/Documentation/hwmon/it87 | |||
| @@ -86,7 +86,6 @@ The IT8712F and IT8716F additionally feature VID inputs, used to report | |||
| 86 | the Vcore voltage of the processor. The early IT8712F have 5 VID pins, | 86 | the Vcore voltage of the processor. The early IT8712F have 5 VID pins, |
| 87 | the IT8716F and late IT8712F have 6. They are shared with other functions | 87 | the IT8716F and late IT8712F have 6. They are shared with other functions |
| 88 | though, so the functionality may not be available on a given system. | 88 | though, so the functionality may not be available on a given system. |
| 89 | The driver dumbly assume it is there. | ||
| 90 | 89 | ||
| 91 | The IT8718F and IT8720F also features VID inputs (up to 8 pins) but the value | 90 | The IT8718F and IT8720F also features VID inputs (up to 8 pins) but the value |
| 92 | is stored in the Super-I/O configuration space. Due to technical limitations, | 91 | is stored in the Super-I/O configuration space. Due to technical limitations, |
diff --git a/Documentation/hwmon/mc13783-adc b/Documentation/hwmon/mc13783-adc new file mode 100644 index 000000000000..044531a86405 --- /dev/null +++ b/Documentation/hwmon/mc13783-adc | |||
| @@ -0,0 +1,50 @@ | |||
| 1 | Kernel driver mc13783-adc | ||
| 2 | ========================= | ||
| 3 | |||
| 4 | Supported chips: | ||
| 5 | * Freescale Atlas MC13783 | ||
| 6 | Prefix: 'mc13783_adc' | ||
| 7 | Datasheet: http://www.freescale.com/files/rf_if/doc/data_sheet/MC13783.pdf?fsrch=1 | ||
| 8 | |||
| 9 | Authors: | ||
| 10 | Sascha Hauer <s.hauer@pengutronix.de> | ||
| 11 | Luotao Fu <l.fu@pengutronix.de> | ||
| 12 | |||
| 13 | Description | ||
| 14 | ----------- | ||
| 15 | |||
| 16 | The Freescale MC13783 is a Power Management and Audio Circuit. Among | ||
| 17 | other things it contains a 10-bit A/D converter. The converter has 16 | ||
| 18 | channels which can be used in different modes. | ||
| 19 | The A/D converter has a resolution of 2.25mV. Channels 0-4 have | ||
| 20 | a dedicated meaning with chip internal scaling applied. Channels 5-7 | ||
| 21 | can be used as general purpose inputs or alternatively in a dedicated | ||
| 22 | mode. Channels 12-15 are occupied by the touchscreen if it's active. | ||
| 23 | |||
| 24 | Currently the driver only supports channels 2 and 5-15 with no alternative | ||
| 25 | modes for channels 5-7. | ||
| 26 | |||
| 27 | See this table for the meaning of the different channels and their chip | ||
| 28 | internal scaling: | ||
| 29 | |||
| 30 | Channel Signal Input Range Scaling | ||
| 31 | ------------------------------------------------------------------------------- | ||
| 32 | 0 Battery Voltage (BATT) 2.50 - 4.65V -2.40V | ||
| 33 | 1 Battery Current (BATT - BATTISNS) -50 - 50 mV x20 | ||
| 34 | 2 Application Supply (BP) 2.50 - 4.65V -2.40V | ||
| 35 | 3 Charger Voltage (CHRGRAW) 0 - 10V / /5 | ||
| 36 | 0 - 20V /10 | ||
| 37 | 4 Charger Current (CHRGISNSP-CHRGISNSN) -0.25V - 0.25V x4 | ||
| 38 | 5 General Purpose ADIN5 / Battery Pack Thermistor 0 - 2.30V No | ||
| 39 | 6 General Purpose ADIN6 / Backup Voltage (LICELL) 0 - 2.30V / No / | ||
| 40 | 1.50 - 3.50V -1.20V | ||
| 41 | 7 General Purpose ADIN7 / UID / Die Temperature 0 - 2.30V / No / | ||
| 42 | 0 - 2.55V / x0.9 / No | ||
| 43 | 8 General Purpose ADIN8 0 - 2.30V No | ||
| 44 | 9 General Purpose ADIN9 0 - 2.30V No | ||
| 45 | 10 General Purpose ADIN10 0 - 2.30V No | ||
| 46 | 11 General Purpose ADIN11 0 - 2.30V No | ||
| 47 | 12 General Purpose TSX1 / Touchscreen X-plate 1 0 - 2.30V No | ||
| 48 | 13 General Purpose TSX2 / Touchscreen X-plate 2 0 - 2.30V No | ||
| 49 | 14 General Purpose TSY1 / Touchscreen Y-plate 1 0 - 2.30V No | ||
| 50 | 15 General Purpose TSY2 / Touchscreen Y-plate 2 0 - 2.30V No | ||
diff --git a/Documentation/hwmon/sysfs-interface b/Documentation/hwmon/sysfs-interface index 82def883361b..3de6b0bcb147 100644 --- a/Documentation/hwmon/sysfs-interface +++ b/Documentation/hwmon/sysfs-interface | |||
| @@ -225,8 +225,6 @@ pwm[1-*]_auto_point[1-*]_temp_hyst | |||
| 225 | to PWM output channels. | 225 | to PWM output channels. |
| 226 | RW | 226 | RW |
| 227 | 227 | ||
| 228 | OR | ||
| 229 | |||
| 230 | temp[1-*]_auto_point[1-*]_pwm | 228 | temp[1-*]_auto_point[1-*]_pwm |
| 231 | temp[1-*]_auto_point[1-*]_temp | 229 | temp[1-*]_auto_point[1-*]_temp |
| 232 | temp[1-*]_auto_point[1-*]_temp_hyst | 230 | temp[1-*]_auto_point[1-*]_temp_hyst |
| @@ -235,6 +233,15 @@ temp[1-*]_auto_point[1-*]_temp_hyst | |||
| 235 | to temperature channels. | 233 | to temperature channels. |
| 236 | RW | 234 | RW |
| 237 | 235 | ||
| 236 | There is a third case where trip points are associated to both PWM output | ||
| 237 | channels and temperature channels: the PWM values are associated to PWM | ||
| 238 | output channels while the temperature values are associated to temperature | ||
| 239 | channels. In that case, the result is determined by the mapping between | ||
| 240 | temperature inputs and PWM outputs. When several temperature inputs are | ||
| 241 | mapped to a given PWM output, this leads to several candidate PWM values. | ||
| 242 | The actual result is up to the chip, but in general the highest candidate | ||
| 243 | value (fastest fan speed) wins. | ||
| 244 | |||
| 238 | 245 | ||
| 239 | **************** | 246 | **************** |
| 240 | * Temperatures * | 247 | * Temperatures * |
diff --git a/Documentation/hwmon/w83627hf b/Documentation/hwmon/w83627hf index 6ee36dbafd64..44dd2bcc72bd 100644 --- a/Documentation/hwmon/w83627hf +++ b/Documentation/hwmon/w83627hf | |||
| @@ -32,8 +32,6 @@ Authors: | |||
| 32 | Module Parameters | 32 | Module Parameters |
| 33 | ----------------- | 33 | ----------------- |
| 34 | 34 | ||
| 35 | * force_addr: int | ||
| 36 | Initialize the ISA address of the sensors | ||
| 37 | * force_i2c: int | 35 | * force_i2c: int |
| 38 | Initialize the I2C address of the sensors | 36 | Initialize the I2C address of the sensors |
| 39 | * init: int | 37 | * init: int |
| @@ -70,3 +68,30 @@ doesn't help, you may just ignore the bogus VID reading with no harm done. | |||
| 70 | For further information on this driver see the w83781d driver documentation. | 68 | For further information on this driver see the w83781d driver documentation. |
| 71 | 69 | ||
| 72 | [1] http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/vid | 70 | [1] http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/vid |
| 71 | |||
| 72 | Forcing the address | ||
| 73 | ------------------- | ||
| 74 | |||
| 75 | The driver used to have a module parameter named force_addr, which could | ||
| 76 | be used to force the base I/O address of the hardware monitoring block. | ||
| 77 | This was meant as a workaround for mainboards with a broken BIOS. This | ||
| 78 | module parameter is gone for technical reasons. If you need this feature, | ||
| 79 | you can obtain the same result by using the isaset tool (part of | ||
| 80 | lm-sensors) before loading the driver: | ||
| 81 | |||
| 82 | # Enter the Super I/O config space | ||
| 83 | isaset -y -f 0x2e 0x87 | ||
| 84 | isaset -y -f 0x2e 0x87 | ||
| 85 | |||
| 86 | # Select the hwmon logical device | ||
| 87 | isaset -y 0x2e 0x2f 0x07 0x0b | ||
| 88 | |||
| 89 | # Set the base I/O address (to 0x290 in this example) | ||
| 90 | isaset -y 0x2e 0x2f 0x60 0x02 | ||
| 91 | isaset -y 0x2e 0x2f 0x61 0x90 | ||
| 92 | |||
| 93 | # Exit the Super-I/O config space | ||
| 94 | isaset -y -f 0x2e 0xaa | ||
| 95 | |||
| 96 | The above sequence assumes a Super-I/O config space at 0x2e/0x2f, but | ||
| 97 | 0x4e/0x4f is also possible. | ||
