lm93 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302
  1. Kernel driver lm93
  2. ==================
  3. Supported chips:
  4. * National Semiconductor LM93
  5. Prefix 'lm93'
  6. Addresses scanned: I2C 0x2c-0x2e
  7. Datasheet: http://www.national.com/ds.cgi/LM/LM93.pdf
  8. Authors:
  9. Mark M. Hoffman <mhoffman@lightlink.com>
  10. Ported to 2.6 by Eric J. Bowersox <ericb@aspsys.com>
  11. Adapted to 2.6.20 by Carsten Emde <ce@osadl.org>
  12. Modified for mainline integration by Hans J. Koch <hjk@linutronix.de>
  13. Module Parameters
  14. -----------------
  15. * init: integer
  16. Set to non-zero to force some initializations (default is 0).
  17. * disable_block: integer
  18. A "0" allows SMBus block data transactions if the host supports them. A "1"
  19. disables SMBus block data transactions. The default is 0.
  20. * vccp_limit_type: integer array (2)
  21. Configures in7 and in8 limit type, where 0 means absolute and non-zero
  22. means relative. "Relative" here refers to "Dynamic Vccp Monitoring using
  23. VID" from the datasheet. It greatly simplifies the interface to allow
  24. only one set of limits (absolute or relative) to be in operation at a
  25. time (even though the hardware is capable of enabling both). There's
  26. not a compelling use case for enabling both at once, anyway. The default
  27. is "0,0".
  28. * vid_agtl: integer
  29. A "0" configures the VID pins for V(ih) = 2.1V min, V(il) = 0.8V max.
  30. A "1" configures the VID pins for V(ih) = 0.8V min, V(il) = 0.4V max.
  31. (The latter setting is referred to as AGTL+ Compatible in the datasheet.)
  32. I.e. this parameter controls the VID pin input thresholds; if your VID
  33. inputs are not working, try changing this. The default value is "0".
  34. Hardware Description
  35. --------------------
  36. (from the datasheet)
  37. The LM93 hardware monitor has a two wire digital interface compatible with
  38. SMBus 2.0. Using an 8-bit ADC, the LM93 measures the temperature of two remote
  39. diode connected transistors as well as its own die and 16 power supply
  40. voltages. To set fan speed, the LM93 has two PWM outputs that are each
  41. controlled by up to four temperature zones. The fancontrol algorithm is lookup
  42. table based. The LM93 includes a digital filter that can be invoked to smooth
  43. temperature readings for better control of fan speed. The LM93 has four
  44. tachometer inputs to measure fan speed. Limit and status registers for all
  45. measured values are included. The LM93 builds upon the functionality of
  46. previous motherboard management ASICs and uses some of the LM85's features
  47. (i.e. smart tachometer mode). It also adds measurement and control support
  48. for dynamic Vccp monitoring and PROCHOT. It is designed to monitor a dual
  49. processor Xeon class motherboard with a minimum of external components.
  50. User Interface
  51. --------------
  52. #PROCHOT:
  53. The LM93 can monitor two #PROCHOT signals. The results are found in the
  54. sysfs files prochot1, prochot2, prochot1_avg, prochot2_avg, prochot1_max,
  55. and prochot2_max. prochot1_max and prochot2_max contain the user limits
  56. for #PROCHOT1 and #PROCHOT2, respectively. prochot1 and prochot2 contain
  57. the current readings for the most recent complete time interval. The
  58. value of prochot1_avg and prochot2_avg is something like a 2 period
  59. exponential moving average (but not quite - check the datasheet). Note
  60. that this third value is calculated by the chip itself. All values range
  61. from 0-255 where 0 indicates no throttling, and 255 indicates > 99.6%.
  62. The monitoring intervals for the two #PROCHOT signals is also configurable.
  63. These intervals can be found in the sysfs files prochot1_interval and
  64. prochot2_interval. The values in these files specify the intervals for
  65. #P1_PROCHOT and #P2_PROCHOT, respectively. Selecting a value not in this
  66. list will cause the driver to use the next largest interval. The available
  67. intervals are (in seconds):
  68. #PROCHOT intervals: 0.73, 1.46, 2.9, 5.8, 11.7, 23.3, 46.6, 93.2, 186, 372
  69. It is possible to configure the LM93 to logically short the two #PROCHOT
  70. signals. I.e. when #P1_PROCHOT is asserted, the LM93 will automatically
  71. assert #P2_PROCHOT, and vice-versa. This mode is enabled by writing a
  72. non-zero integer to the sysfs file prochot_short.
  73. The LM93 can also override the #PROCHOT pins by driving a PWM signal onto
  74. one or both of them. When overridden, the signal has a period of 3.56 ms,
  75. a minimum pulse width of 5 clocks (at 22.5kHz => 6.25% duty cycle), and
  76. a maximum pulse width of 80 clocks (at 22.5kHz => 99.88% duty cycle).
  77. The sysfs files prochot1_override and prochot2_override contain boolean
  78. integers which enable or disable the override function for #P1_PROCHOT and
  79. #P2_PROCHOT, respectively. The sysfs file prochot_override_duty_cycle
  80. contains a value controlling the duty cycle for the PWM signal used when
  81. the override function is enabled. This value ranges from 0 to 15, with 0
  82. indicating minimum duty cycle and 15 indicating maximum.
  83. #VRD_HOT:
  84. The LM93 can monitor two #VRD_HOT signals. The results are found in the
  85. sysfs files vrdhot1 and vrdhot2. There is one value per file: a boolean for
  86. which 1 indicates #VRD_HOT is asserted and 0 indicates it is negated. These
  87. files are read-only.
  88. Smart Tach Mode:
  89. (from the datasheet)
  90. If a fan is driven using a low-side drive PWM, the tachometer
  91. output of the fan is corrupted. The LM93 includes smart tachometer
  92. circuitry that allows an accurate tachometer reading to be
  93. achieved despite the signal corruption. In smart tach mode all
  94. four signals are measured within 4 seconds.
  95. Smart tach mode is enabled by the driver by writing 1 or 2 (associating the
  96. the fan tachometer with a pwm) to the sysfs file fan<n>_smart_tach. A zero
  97. will disable the function for that fan. Note that Smart tach mode cannot be
  98. enabled if the PWM output frequency is 22500 Hz (see below).
  99. Manual PWM:
  100. The LM93 has a fixed or override mode for the two PWM outputs (although, there
  101. are still some conditions that will override even this mode - see section
  102. 15.10.6 of the datasheet for details.) The sysfs files pwm1_override
  103. and pwm2_override are used to enable this mode; each is a boolean integer
  104. where 0 disables and 1 enables the manual control mode. The sysfs files pwm1
  105. and pwm2 are used to set the manual duty cycle; each is an integer (0-255)
  106. where 0 is 0% duty cycle, and 255 is 100%. Note that the duty cycle values
  107. are constrained by the hardware. Selecting a value which is not available
  108. will cause the driver to use the next largest value. Also note: when manual
  109. PWM mode is disabled, the value of pwm1 and pwm2 indicates the current duty
  110. cycle chosen by the h/w.
  111. PWM Output Frequency:
  112. The LM93 supports several different frequencies for the PWM output channels.
  113. The sysfs files pwm1_freq and pwm2_freq are used to select the frequency. The
  114. frequency values are constrained by the hardware. Selecting a value which is
  115. not available will cause the driver to use the next largest value. Also note
  116. that this parameter has implications for the Smart Tach Mode (see above).
  117. PWM Output Frequencies (in Hz): 12, 36, 48, 60, 72, 84, 96, 22500 (default)
  118. Automatic PWM:
  119. The LM93 is capable of complex automatic fan control, with many different
  120. points of configuration. To start, each PWM output can be bound to any
  121. combination of eight control sources. The final PWM is the largest of all
  122. individual control sources to which the PWM output is bound.
  123. The eight control sources are: temp1-temp4 (aka "zones" in the datasheet),
  124. #PROCHOT 1 & 2, and #VRDHOT 1 & 2. The bindings are expressed as a bitmask
  125. in the sysfs files pwm<n>_auto_channels, where a "1" enables the binding, and
  126. a "0" disables it. The h/w default is 0x0f (all temperatures bound).
  127. 0x01 - Temp 1
  128. 0x02 - Temp 2
  129. 0x04 - Temp 3
  130. 0x08 - Temp 4
  131. 0x10 - #PROCHOT 1
  132. 0x20 - #PROCHOT 2
  133. 0x40 - #VRDHOT 1
  134. 0x80 - #VRDHOT 2
  135. The function y = f(x) takes a source temperature x to a PWM output y. This
  136. function of the LM93 is derived from a base temperature and a table of 12
  137. temperature offsets. The base temperature is expressed in degrees C in the
  138. sysfs files temp<n>_auto_base. The offsets are expressed in cumulative
  139. degrees C, with the value of offset <i> for temperature value <n> being
  140. contained in the file temp<n>_auto_offset<i>. E.g. if the base temperature
  141. is 40C:
  142. offset # temp<n>_auto_offset<i> range pwm
  143. 1 0 - 25.00%
  144. 2 0 - 28.57%
  145. 3 1 40C - 41C 32.14%
  146. 4 1 41C - 42C 35.71%
  147. 5 2 42C - 44C 39.29%
  148. 6 2 44C - 46C 42.86%
  149. 7 2 48C - 50C 46.43%
  150. 8 2 50C - 52C 50.00%
  151. 9 2 52C - 54C 53.57%
  152. 10 2 54C - 56C 57.14%
  153. 11 2 56C - 58C 71.43%
  154. 12 2 58C - 60C 85.71%
  155. > 60C 100.00%
  156. Valid offsets are in the range 0C <= x <= 7.5C in 0.5C increments.
  157. There is an independent base temperature for each temperature channel. Note,
  158. however, there are only two tables of offsets: one each for temp[12] and
  159. temp[34]. Therefore, any change to e.g. temp1_auto_offset<i> will also
  160. affect temp2_auto_offset<i>.
  161. The LM93 can also apply hysteresis to the offset table, to prevent unwanted
  162. oscillation between two steps in the offsets table. These values are found in
  163. the sysfs files temp<n>_auto_offset_hyst. The value in this file has the
  164. same representation as in temp<n>_auto_offset<i>.
  165. If a temperature reading falls below the base value for that channel, the LM93
  166. will use the minimum PWM value. These values are found in the sysfs files
  167. temp<n>_auto_pwm_min. Note, there are only two minimums: one each for temp[12]
  168. and temp[34]. Therefore, any change to e.g. temp1_auto_pwm_min will also
  169. affect temp2_auto_pwm_min.
  170. PWM Spin-Up Cycle:
  171. A spin-up cycle occurs when a PWM output is commanded from 0% duty cycle to
  172. some value > 0%. The LM93 supports a minimum duty cycle during spin-up. These
  173. values are found in the sysfs files pwm<n>_auto_spinup_min. The value in this
  174. file has the same representation as other PWM duty cycle values. The
  175. duration of the spin-up cycle is also configurable. These values are found in
  176. the sysfs files pwm<n>_auto_spinup_time. The value in this file is
  177. the spin-up time in seconds. The available spin-up times are constrained by
  178. the hardware. Selecting a value which is not available will cause the driver
  179. to use the next largest value.
  180. Spin-up Durations: 0 (disabled, h/w default), 0.1, 0.25, 0.4, 0.7, 1.0,
  181. 2.0, 4.0
  182. #PROCHOT and #VRDHOT PWM Ramping:
  183. If the #PROCHOT or #VRDHOT signals are asserted while bound to a PWM output
  184. channel, the LM93 will ramp the PWM output up to 100% duty cycle in discrete
  185. steps. The duration of each step is configurable. There are two files, with
  186. one value each in seconds: pwm_auto_prochot_ramp and pwm_auto_vrdhot_ramp.
  187. The available ramp times are constrained by the hardware. Selecting a value
  188. which is not available will cause the driver to use the next largest value.
  189. Ramp Times: 0 (disabled, h/w default) to 0.75 in 0.05 second intervals
  190. Fan Boost:
  191. For each temperature channel, there is a boost temperature: if the channel
  192. exceeds this limit, the LM93 will immediately drive both PWM outputs to 100%.
  193. This limit is expressed in degrees C in the sysfs files temp<n>_auto_boost.
  194. There is also a hysteresis temperature for this function: after the boost
  195. limit is reached, the temperature channel must drop below this value before
  196. the boost function is disabled. This temperature is also expressed in degrees
  197. C in the sysfs files temp<n>_auto_boost_hyst.
  198. GPIO Pins:
  199. The LM93 can monitor the logic level of four dedicated GPIO pins as well as the
  200. four tach input pins. GPIO0-GPIO3 correspond to (fan) tach 1-4, respectively.
  201. All eight GPIOs are read by reading the bitmask in the sysfs file gpio. The
  202. LSB is GPIO0, and the MSB is GPIO7.
  203. LM93 Unique sysfs Files
  204. -----------------------
  205. file description
  206. -------------------------------------------------------------
  207. prochot<n> current #PROCHOT %
  208. prochot<n>_avg moving average #PROCHOT %
  209. prochot<n>_max limit #PROCHOT %
  210. prochot_short enable or disable logical #PROCHOT pin short
  211. prochot<n>_override force #PROCHOT assertion as PWM
  212. prochot_override_duty_cycle
  213. duty cycle for the PWM signal used when
  214. #PROCHOT is overridden
  215. prochot<n>_interval #PROCHOT PWM sampling interval
  216. vrdhot<n> 0 means negated, 1 means asserted
  217. fan<n>_smart_tach enable or disable smart tach mode
  218. pwm<n>_auto_channels select control sources for PWM outputs
  219. pwm<n>_auto_spinup_min minimum duty cycle during spin-up
  220. pwm<n>_auto_spinup_time duration of spin-up
  221. pwm_auto_prochot_ramp ramp time per step when #PROCHOT asserted
  222. pwm_auto_vrdhot_ramp ramp time per step when #VRDHOT asserted
  223. temp<n>_auto_base temperature channel base
  224. temp<n>_auto_offset[1-12]
  225. temperature channel offsets
  226. temp<n>_auto_offset_hyst
  227. temperature channel offset hysteresis
  228. temp<n>_auto_boost temperature channel boost (PWMs to 100%) limit
  229. temp<n>_auto_boost_hyst temperature channel boost hysteresis
  230. gpio input state of 8 GPIO pins; read-only