| 1 | Kernel driver `vt1211.o' |
|---|
| 2 | ========================= |
|---|
| 3 | |
|---|
| 4 | Status: Beta. |
|---|
| 5 | |
|---|
| 6 | Supported chips: |
|---|
| 7 | * Via VT1211 Super I/O Controller |
|---|
| 8 | Addresses scanned: none, address read from Super I/O config space |
|---|
| 9 | |
|---|
| 10 | Authors: Mark D. Studebaker <mdsxyz123@yahoo.com> |
|---|
| 11 | |
|---|
| 12 | |
|---|
| 13 | Module Parameters |
|---|
| 14 | ----------------- |
|---|
| 15 | |
|---|
| 16 | force_addr=0xaddr Set the I/O base address. Useful for boards |
|---|
| 17 | that don't set the address in the BIOS. |
|---|
| 18 | Don't use this unless the driver complains that the |
|---|
| 19 | base address is not set. |
|---|
| 20 | Example: 'modprobe vt1211 force_addr=0x680' |
|---|
| 21 | |
|---|
| 22 | |
|---|
| 23 | Description |
|---|
| 24 | ----------- |
|---|
| 25 | |
|---|
| 26 | The Via VT1211 Super I/O chip |
|---|
| 27 | contains voltage/temperature monitoring and |
|---|
| 28 | PWM control circuitry for two fans. |
|---|
| 29 | |
|---|
| 30 | We define the sensors as follows. Somewhat convoluted to minimize |
|---|
| 31 | changes from via686a. |
|---|
| 32 | |
|---|
| 33 | Sensor Voltage Mode Temp Mode uch_config bit |
|---|
| 34 | -------- ------------ --------- -------------- |
|---|
| 35 | Reading 1 temp3 |
|---|
| 36 | Reading 3 temp1 |
|---|
| 37 | UCH1/Reading2 in0 temp2 0x04 (4) |
|---|
| 38 | UCH2 in1 temp4 0x08 (8) |
|---|
| 39 | UCH3 in2 temp5 0x10 (16) |
|---|
| 40 | UCH4 in3 temp6 0x20 (32) |
|---|
| 41 | UCH5 in4 temp7 0x40 (64) |
|---|
| 42 | 3.3V in5 |
|---|
| 43 | |
|---|
| 44 | As noted above, 5 of the sensors are "universal channels" and can |
|---|
| 45 | be set for either voltage or temperature. |
|---|
| 46 | Set the uch_config bit (in /proc) to 0 for voltage and 1 for temperature. |
|---|
| 47 | Voltages will read 0 if set for temperature. |
|---|
| 48 | Temperatures will read a really low number if set for voltage. |
|---|
| 49 | |
|---|
| 50 | Fan rotation speeds are reported in RPM (rotations per minute). An alarm is |
|---|
| 51 | triggered if the rotation speed has dropped below a programmable limit. Fan |
|---|
| 52 | readings can be divided by a programmable divider (1, 2, 4 or 8) to give |
|---|
| 53 | the readings more range or accuracy. Not all RPM values can accurately be |
|---|
| 54 | represented, so some rounding is done. With a divider of 2, the lowest |
|---|
| 55 | representable value is around 2600 RPM. |
|---|
| 56 | |
|---|
| 57 | PWM values are from 0 to 255. The first value in the /proc entry is |
|---|
| 58 | the pwm value; the second is the enable (0 or 1). |
|---|
| 59 | |
|---|
| 60 | If an alarm triggers, it will remain triggered until the hardware register |
|---|
| 61 | is read at least once. This means that the cause for the alarm may |
|---|
| 62 | already have disappeared! Note that in the current implementation, all |
|---|
| 63 | hardware registers are read whenever any data is read (unless it is less |
|---|
| 64 | than 1.5 seconds since the last update). This means that you can easily |
|---|
| 65 | miss once-only alarms. |
|---|
| 66 | |
|---|
| 67 | |
|---|
| 68 | ********************** |
|---|
| 69 | The lm_sensors project gratefully acknowledges the support of |
|---|
| 70 | Via in the development of this driver. |
|---|
