7 Addresses scanned: from Super I/O config space (8 I/O ports)
8 Datasheet: Not publicly available
11 Addresses scanned: from Super I/O config space (8 I/O ports)
12 Datasheet: Not publicly available
15 Addresses scanned: from Super I/O config space (8 I/O ports)
18 Addresses scanned: from Super I/O config space (8 I/O ports)
19 Datasheet: Not publicly available
22 Addresses scanned: from Super I/O config space (8 I/O ports)
23 Datasheet: Not publicly available
26 Addresses scanned: from Super I/O config space (8 I/O ports)
27 Datasheet: Not publicly available
30 Addresses scanned: from Super I/O config space (8 I/O ports)
31 Datasheet: Once publicly available at the ITE website, but no longer
34 Addresses scanned: from Super I/O config space (8 I/O ports)
35 Datasheet: Once publicly available at the ITE website, but no longer
38 Addresses scanned: from Super I/O config space (8 I/O ports)
39 Datasheet: Once publicly available at the ITE website, but no longer
42 Addresses scanned: from Super I/O config space (8 I/O ports)
43 Datasheet: Once publicly available at the ITE website, but no longer
46 Addresses scanned: from Super I/O config space (8 I/O ports)
47 Datasheet: Not publicly available
50 Addresses scanned: from Super I/O config space (8 I/O ports)
51 Datasheet: Not publicly available
54 Addresses scanned: from Super I/O config space (8 I/O ports)
55 Datasheet: Not publicly available
58 Addresses scanned: from Super I/O config space (8 I/O ports)
59 Datasheet: Not publicly available
62 Addresses scanned: from Super I/O config space (8 I/O ports)
63 Datasheet: Not publicly available
66 Addresses scanned: from Super I/O config space (8 I/O ports)
67 Datasheet: Not publicly available
70 Addresses scanned: from Super I/O config space (8 I/O ports)
71 Datasheet: Not publicly available
74 Addresses scanned: from Super I/O config space (8 I/O ports)
75 Datasheet: Not publicly available
78 Addresses scanned: from Super I/O config space (8 I/O ports)
79 Datasheet: Not publicly available
82 Addresses scanned: from Super I/O config space (8 I/O ports)
83 Datasheet: Not publicly available
86 Addresses scanned: from Super I/O config space (8 I/O ports)
87 Datasheet: Not publicly available
88 * SiS950 [clone of IT8705F]
90 Addresses scanned: from Super I/O config space (8 I/O ports)
91 Datasheet: No longer be available
95 Jean Delvare <jdelvare@suse.de>
96 Guenter Roeck <linux@roeck-us.net>
100 ---------------------
116 * sudo make dkms_clean
120 * The module does not provide a real version number, so `git describe --long`
121 is used to create one. This means that anything that changes the git state
122 will change the version. `make dkms_clean` should be run before making a
123 commit or an update with `git pull` as the Makefile is currently unable to
124 track the last installed version to replace it. If this doesn't happen, the
125 old version will need to be manually removed from dkms, before installing
127 Something like `dkms remove -m it87 -v <old version> --all`, followed by
128 `rm -rf /usr/src/it87-<old version>`, should do.
129 `dkms status it87` can be used to list the installed versions.
137 0 if vbat should report power on value, 1 if vbat should be updated after
138 each read. Default is 0. On some boards the battery voltage is provided
139 by either the battery or the onboard power supply. Only the first reading
140 at power on will be the actual battery voltage (which the chip does
141 automatically). On other boards the battery voltage is always fed to
142 the chip so can be read at any time. Excessive reading may decrease
143 battery life but no information is given in the datasheet.
145 * fix_pwm_polarity int
147 Force PWM polarity to active high (DANGEROUS). Some chips are
148 misconfigured by BIOS - PWM values would be inverted. This option tries
149 to fix this. Please contact your BIOS manufacturer and ask him for fix.
153 Force chip ID to specified value. Should only be used for testing.
155 * ignore_resource_conflict
157 Similar to acpi_enforce_resources=lax, but only affects this driver.
158 ACPI resource conflicts are ignored if this parameter is provided and
160 Provided since there are reports that system-wide acpi_enfore_resources=lax
161 can result in boot failures on some systems.
162 Note: This is inherently risky since it means that both ACPI and this driver
163 may access the chip at the same time. This can result in race conditions and,
164 worst case, result in unexpected system reboots.
168 If set to 1, the driver uses MMIO to access the chip if supported. This is
169 faster and less risky (untested!).
175 All the chips supported by this driver are LPC Super-I/O chips, accessed
176 through the LPC bus (ISA-like I/O ports). The IT8712F additionally has an
177 SMBus interface to the hardware monitoring functions. This driver no
178 longer supports this interface though, as it is slower and less reliable
179 than the ISA access, and was only available on a small number of
186 This driver implements support for the IT8603E, IT8620E, IT8622E, IT8623E,
187 IT8628E, IT8705F, IT8712F, IT8716F, IT8718F, IT8720F, IT8721F, IT8726F, IT8728F,
188 IT8732F, IT8758E, IT8771E, IT8772E, IT8781F, IT8782F, IT8783E/F, IT8786E,
189 IT8790E, and SiS950 chips.
191 These chips are 'Super I/O chips', supporting floppy disks, infrared ports,
192 joysticks and other miscellaneous stuff. For hardware monitoring, they
193 include an 'environment controller' with 3 temperature sensors, 3 fan
194 rotation speed sensors, 8 voltage sensors, associated alarms, and chassis
197 The IT8712F and IT8716F additionally feature VID inputs, used to report
198 the Vcore voltage of the processor. The early IT8712F have 5 VID pins,
199 the IT8716F and late IT8712F have 6. They are shared with other functions
200 though, so the functionality may not be available on a given system.
202 The IT8718F and IT8720F also features VID inputs (up to 8 pins) but the value
203 is stored in the Super-I/O configuration space. Due to technical limitations,
204 this value can currently only be read once at initialization time, so
205 the driver won't notice and report changes in the VID value. The two
206 upper VID bits share their pins with voltage inputs (in5 and in6) so you
207 can't have both on a given board.
209 The IT8716F, IT8718F, IT8720F, IT8721F/IT8758E and later IT8712F revisions
210 have support for 2 additional fans. The additional fans are supported by the
213 The IT8716F, IT8718F, IT8720F, IT8721F/IT8758E, IT8732F, IT8781F, IT8782F,
214 IT8783E/F, and late IT8712F and IT8705F also have optional 16-bit tachometer
215 counters for fans 1 to 3. This is better (no more fan clock divider mess) but
216 not compatible with the older chips and revisions. The 16-bit tachometer mode
217 is enabled by the driver when one of the above chips is detected.
219 The IT8726F is just bit enhanced IT8716F with additional hardware
220 for AMD power sequencing. Therefore the chip will appear as IT8716F
221 to userspace applications.
223 The IT8728F, IT8771E, and IT8772E are considered compatible with the IT8721F,
224 until a datasheet becomes available (hopefully.)
226 The IT8603E/IT8623E is a custom design, hardware monitoring part is similar to
227 IT8728F. It only supports 3 fans, 16-bit fan mode, and the full speed mode
228 of the fan is not supported (value 0 of pwmX_enable).
230 The IT8620E and IT8628E are custom designs, hardware monitoring part is similar
231 to IT8728F. It only supports 16-bit fan mode. Both chips support up to 6 fans.
233 The IT8790E supports up to 3 fans. 16-bit fan mode is always enabled.
235 The IT8732F supports a closed-loop mode for fan control, but this is not
236 currently implemented by the driver.
238 Temperatures are measured in degrees Celsius. An alarm is triggered once
239 when the Overtemperature Shutdown limit is crossed.
241 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
242 triggered if the rotation speed has dropped below a programmable limit. When
243 16-bit tachometer counters aren't used, fan readings can be divided by
244 a programmable divider (1, 2, 4 or 8) to give the readings more range or
245 accuracy. With a divider of 2, the lowest representable value is around
246 2600 RPM. Not all RPM values can accurately be represented, so some rounding
249 Voltage sensors (also known as IN sensors) report their values in volts. An
250 alarm is triggered if the voltage has crossed a programmable minimum or
251 maximum limit. Note that minimum in this case always means 'closest to
252 zero'; this is important for negative voltage measurements. On most chips, all
253 voltage inputs can measure voltages between 0 and 4.08 volts, with a resolution
254 of 0.016 volt. IT8603E, IT8721F/IT8758E and IT8728F can measure between 0 and
255 3.06 volts, with a resolution of 0.012 volt. IT8732F can measure between 0 and
256 2.8 volts with a resolution of 0.0109 volt. The battery voltage in8 does not
257 have limit registers.
259 On the IT8603E, IT8620E, IT8628E, IT8721F/IT8758E, IT8732F, IT8781F, IT8782F,
260 and IT8783E/F, some voltage inputs are internal and scaled inside the chip:
262 * in7 (optional for IT8781F, IT8782F, and IT8783E/F)
264 * in9 (relevant for IT8603E only)
265 The driver handles this transparently so user-space doesn't have to care.
267 The VID lines (IT8712F/IT8716F/IT8718F/IT8720F) encode the core voltage value:
268 the voltage level your processor should work with. This is hardcoded by
269 the mainboard and/or processor itself. It is a value in volts.
271 If an alarm triggers, it will remain triggered until the hardware register
272 is read at least once. This means that the cause for the alarm may already
273 have disappeared! Note that in the current implementation, all hardware
274 registers are read whenever any data is read (unless it is less than 1.5
275 seconds since the last update). This means that you can easily miss
278 Out-of-limit readings can also result in beeping, if the chip is properly
279 wired and configured. Beeping can be enabled or disabled per sensor type
280 (temperatures, voltages and fans.)
282 The IT87xx only updates its values each 1.5 seconds; reading it more often
283 will do no harm, but will return 'old' values.
285 To change sensor N to a thermistor, 'echo 4 > tempN_type' where N is 1, 2,
286 or 3. To change sensor N to a thermal diode, 'echo 3 > tempN_type'.
287 Give 0 for unused sensor. Any other value is invalid. To configure this at
288 startup, consult lm_sensors's /etc/sensors.conf. (4 = thermistor;
295 The fan speed control features are limited to manual PWM mode. Automatic
296 "Smart Guardian" mode control handling is only implemented for older chips
297 (see below.) However if you want to go for "manual mode" just write 1 to
300 If you are only able to control the fan speed with very small PWM values,
301 try lowering the PWM base frequency (pwm1_freq). Depending on the fan,
302 it may give you a somewhat greater control range. The same frequency is
303 used to drive all fan outputs, which is why pwm2_freq and pwm3_freq are
307 Automatic fan speed control (old interface)
308 -------------------------------------------
310 The driver supports the old interface to automatic fan speed control
311 which is implemented by IT8705F chips up to revision F and IT8712F
312 chips up to revision G.
314 This interface implements 4 temperature vs. PWM output trip points.
315 The PWM output of trip point 4 is always the maximum value (fan running
316 at full speed) while the PWM output of the other 3 trip points can be
317 freely chosen. The temperature of all 4 trip points can be freely chosen.
318 Additionally, trip point 1 has an hysteresis temperature attached, to
319 prevent fast switching between fan on and off.
321 The chip automatically computes the PWM output value based on the input
322 temperature, based on this simple rule: if the temperature value is
323 between trip point N and trip point N+1 then the PWM output value is
324 the one of trip point N. The automatic control mode is less flexible
325 than the manual control mode, but it reacts faster, is more robust and
326 doesn't use CPU cycles.
328 Trip points must be set properly before switching to automatic fan speed
329 control mode. The driver will perform basic integrity checks before
330 actually switching to automatic control mode.
333 Temperature offset attributes
334 -----------------------------
336 The driver supports temp[1-3]_offset sysfs attributes to adjust the reported
337 temperature for thermal diodes or diode-connected thermal transistors.
338 If a temperature sensor is configured for thermistors, the attribute values
339 are ignored. If the thermal sensor type is Intel PECI, the temperature offset
340 must be programmed to the critical CPU temperature.
345 Support for IT8607E is preliminary. Voltage readings, temperature readings,
346 fan control, and fan speed measurements may be wrong and/or missing.
347 Fan control and fan speed may be enabled and reported for non-existing
348 fans. Please report any problems and inconsistencies.
350 Reporting information for unsupported chips
351 -------------------------------------------
353 If the chip in your system is not yet supported by the driver, please provide
354 the following information.
356 First, run sensors-detect. It will tell you something like
358 Probing for Super-I/O at 0x2e/0x2f
360 Trying family `ITE'... Yes
361 Found unknown chip with ID 0x8665
362 (logical device 4 has address 0x290, could be sensors)
364 With this information, run the following commands.
366 sudo isadump -k 0x87,0x01,0x55,0x55 0x2e 0x2f 7
367 sudo isadump 0x295 0x296
369 and report the results.
371 The addresses in the first command are from "Probing for Super-I/O at
372 0x2e/0x2f". Use those addresses in the first command.
373 sudo isadump -k 0x87,0x01,0x55,0x55 0x2e 0x2f 7
375 The addresses in the second command are from "has address 0x290".
376 Add 5 and 6 to this address for the next command.
377 sudo isadump 0x295 0x296
379 Next, force-install the driver by providing one of the already supported chips
380 as forced ID. Useful IDs to test are 0x8622, 0x8628, 0x8728, and 0x8732, though
381 feel free to test more IDs. For each ID, instantiate the driver as follows
382 (this example is instantiating driver with ID 0x8622).
383 sudo modprobe it87 force_id=0x8622
384 After entering this command, run the "sensors" command and provide the output.
385 Then unload the driver with
386 sudo modprobe -r it87
387 Repeat with different chip IDs, and report each result.
389 Please also report your board type as well as voltages and fan settings from
390 the BIOS. If possible, connect fans to different fan headers and let us know
391 if all fans are detected and reported.
393 This information _might_ give us enough information to add experimental support
394 for the chip in question. No guarantees, though - unless a datasheet is
395 available, something is likely to be wrong.
397 A note on sensors-detect
398 ========================
400 There is a persistent perception that changes in this driver would have impact
401 on the output of sensors-detect. This is not the case. sensors-detect is an
402 independent application. Changes in this driver do not affect sensors-detect,
403 and changes in sensors-detect do not affect this driver.