sis5595 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. Kernel driver sis5595
  2. =====================
  3. Supported chips:
  4. * Silicon Integrated Systems Corp. SiS5595 Southbridge Hardware Monitor
  5. Prefix: 'sis5595'
  6. Addresses scanned: ISA in PCI-space encoded address
  7. Datasheet: Publicly available at the Silicon Integrated Systems Corp. site.
  8. Authors:
  9. Kyösti Mälkki <kmalkki@cc.hut.fi>,
  10. Mark D. Studebaker <mdsxyz123@yahoo.com>,
  11. Aurelien Jarno <aurelien@aurel32.net> 2.6 port
  12. SiS southbridge has a LM78-like chip integrated on the same IC.
  13. This driver is a customized copy of lm78.c
  14. Supports following revisions:
  15. Version PCI ID PCI Revision
  16. 1 1039/0008 AF or less
  17. 2 1039/0008 B0 or greater
  18. Note: these chips contain a 0008 device which is incompatible with the
  19. 5595. We recognize these by the presence of the listed
  20. "blacklist" PCI ID and refuse to load.
  21. NOT SUPPORTED PCI ID BLACKLIST PCI ID
  22. 540 0008 0540
  23. 550 0008 0550
  24. 5513 0008 5511
  25. 5581 0008 5597
  26. 5582 0008 5597
  27. 5597 0008 5597
  28. 630 0008 0630
  29. 645 0008 0645
  30. 730 0008 0730
  31. 735 0008 0735
  32. Module Parameters
  33. -----------------
  34. force_addr=0xaddr Set the I/O base address. Useful for boards
  35. that don't set the address in the BIOS. Does not do a
  36. PCI force; the device must still be present in lspci.
  37. Don't use this unless the driver complains that the
  38. base address is not set.
  39. Example: 'modprobe sis5595 force_addr=0x290'
  40. Description
  41. -----------
  42. The SiS5595 southbridge has integrated hardware monitor functions. It also
  43. has an I2C bus, but this driver only supports the hardware monitor. For the
  44. I2C bus driver see i2c-sis5595.
  45. The SiS5595 implements zero or one temperature sensor, two fan speed
  46. sensors, four or five voltage sensors, and alarms.
  47. On the first version of the chip, there are four voltage sensors and one
  48. temperature sensor.
  49. On the second version of the chip, the temperature sensor (temp) and the
  50. fifth voltage sensor (in4) share a pin which is configurable, but not
  51. through the driver. Sorry. The driver senses the configuration of the pin,
  52. which was hopefully set by the BIOS.
  53. Temperatures are measured in degrees Celsius. An alarm is triggered once
  54. when the max is crossed; it is also triggered when it drops below the min
  55. value. Measurements are guaranteed between -55 and +125 degrees, with a
  56. resolution of 1 degree.
  57. Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
  58. triggered if the rotation speed has dropped below a programmable limit. Fan
  59. readings can be divided by a programmable divider (1, 2, 4 or 8) to give
  60. the readings more range or accuracy. Not all RPM values can accurately be
  61. represented, so some rounding is done. With a divider of 2, the lowest
  62. representable value is around 2600 RPM.
  63. Voltage sensors (also known as IN sensors) report their values in volts. An
  64. alarm is triggered if the voltage has crossed a programmable minimum or
  65. maximum limit. Note that minimum in this case always means 'closest to
  66. zero'; this is important for negative voltage measurements. All voltage
  67. inputs can measure voltages between 0 and 4.08 volts, with a resolution of
  68. 0.016 volt.
  69. In addition to the alarms described above, there is a BTI alarm, which gets
  70. triggered when an external chip has crossed its limits. Usually, this is
  71. connected to some LM75-like chip; if at least one crosses its limits, this
  72. bit gets set.
  73. If an alarm triggers, it will remain triggered until the hardware register
  74. is read at least once. This means that the cause for the alarm may already
  75. have disappeared! Note that in the current implementation, all hardware
  76. registers are read whenever any data is read (unless it is less than 1.5
  77. seconds since the last update). This means that you can easily miss
  78. once-only alarms.
  79. The SiS5595 only updates its values each 1.5 seconds; reading it more often
  80. will do no harm, but will return 'old' values.
  81. Problems
  82. --------
  83. Some chips refuse to be enabled. We don't know why.
  84. The driver will recognize this and print a message in dmesg.