Review of documentation update for 2.6 kernel

Aurelien Jarno aurelien at
Sun Feb 13 21:38:19 CET 2005

Hi Rudolf!

I have reviewed you i2c documentation patch for 2.6 kernel with 
available on

Due to the size of the patch, I should admit that my concentration was 
not the same during all the time I reviewed it, so I surely missed some

First of all some general remarks that apply to most of the 
documentation files:
- When you underline (== or --) some words, it would be better to have 
  the underlining the same length as the words.
- Some lines are longer than 80 characters, and some are only half used. 
  Would be nice to fix that.

Then when I read all the documentation files, I remarked that some parts
are the same, and it may be a good idea to "factorize" that in a common 
file. I think of:
- Update rate. I mean the fact that if the values are read more often 
  than 1, 1.5, 2 or 5 seconds (that's the values I collected for the 
  different chips), old data are return instead.
- The fact that alarms are alarms from the chip and are not computed.
- The way to clear the alarms by reading values.
- The principle of how fan dividers work and the consequence on values 
- The minimum and maximum values for negative inputs. It is often 
  written "that minimum in this case always means 'closest to zero'".
  Is it still true? If I remember correctly the way negative limits are
  handled has changed some times ago.
- The way the /sys file system is designed for i2c, ie the fact that
  values for a device are accessible at /sys/bus/i2c/devices/<0>-<1>/

Last, please find below some things I have found in the individual 
files. I hope I have kept enough context lines.


diff -Naur a/Documentation/i2c/busses/i2c-ali15x3 b/Documentation/i2c/busses/i2c-ali15x3
--- a/Documentation/i2c/busses/i2c-ali15x3	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-ali15x3	2005-02-08 15:43:07.000000000 +0100
+The M1533/M1543C devices appear as FOUR separate devices
+on the PCI bus. An output of lspci will show something similar
+to the following:
+  00:02.0 USB Controller: Acer Laboratories Inc. M5237 (rev 03)
+  00:03.0 Bridge: Acer Laboratories Inc. M7101      <= THIS IS THE ONE WE NEED
+  00:07.0 ISA bridge: Acer Laboratories Inc. M1533 (rev c3)
+  00:0f.0 IDE interface: Acer Laboratories Inc. M5229 (rev c1)
+** If you have a 1533 or 1543C on the board and you get
Would be better to write M1533 and M1543C so that users can't confused with
PCI ids. And it's only one letter more.

+** "ali15x3.o: Error: Can't detect ali15x3!"
+** then run lspci.
+** If you see the 1533 and 5229 devices but NOT the 7101 device,
idem there
+** then you must enable ACPI, the PMU, SMB, or something similar
+** in the BIOS. 
+** The driver won't work if it can't find the 7101 device.
+The SMB controller is part of the 7101 device, which is an
+ACPI-compliant Power Management Unit (PMU).
+The whole 7101 device has to be enabled for the SMB to work.
diff -Naur a/Documentation/i2c/busses/i2c-ali1535 b/Documentation/i2c/busses/i2c-ali1535
--- a/Documentation/i2c/busses/i2c-ali1535	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-ali1535	2005-02-08 15:42:37.000000000 +0100
+The SMB controller is part of the 7101 device, which is an
again M7101
+ACPI-compliant Power Management Unit (PMU).
+The whole 7101 device has to be enabled for the SMB to work.
+You can't just enable the SMB alone.
diff -Naur a/Documentation/i2c/busses/i2c-ali1563 b/Documentation/i2c/busses/i2c-ali1563
--- a/Documentation/i2c/busses/i2c-ali1563	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-ali1563	2005-02-08 15:42:54.000000000 +0100
+For an overview of these chips see
What about adding the same note as for the M1533 about the password?
+The 1563 southbridge is deceptively similar to the 1533, with a 
again M1563 and M1533
+few notable exceptions. One of those happens to be the fact they 
+upgraded the i2c core to be 2.0 compliant, and happens to be almost 
+identical to the i2c controller found in the Intel 801 south bridges. 
Is it really i2c there or rather SMBus. AFAIK, there is no version 2.0 of the 
i2c standard, but a version 2.0 of the SMBus standard exists.
diff -Naur a/Documentation/i2c/busses/i2c-i810 b/Documentation/i2c/busses/i2c-i810
--- a/Documentation/i2c/busses/i2c-i810	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-i810	2005-02-08 15:45:30.000000000 +0100
+WARNING: If you have an '810' or '815' motherboard, your standard I2C
+temperature sensors are most likely on the 801's I2C bus.
+You want the i2c-i810 driver for those, not this driver.
Something is stranger there as the currently described driver is the
i2c-i810. I think it is rather i2c-i801.
diff -Naur a/Documentation/i2c/busses/i2c-nforce2 b/Documentation/i2c/busses/i2c-nforce2
--- a/Documentation/i2c/busses/i2c-nforce2	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-nforce2	2005-02-08 15:49:03.000000000 +0100
+i2c-nforce2 is a driver for the SMBuses included in the nVidia nForce2 MCP.
and also nForce3

diff -Naur a/Documentation/i2c/busses/i2c-sis5595 b/Documentation/i2c/busses/i2c-sis5595
--- a/Documentation/i2c/busses/i2c-sis5595	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-sis5595	2005-02-08 15:55:08.000000000 +0100
+WARNING: If you are trying to access the integrated sensors on the 
+SiS5595 chip, you want the sis5595.o driver for those, not this driver.
should be either sis5595 or sis5595.ko
diff -Naur a/Documentation/i2c/busses/i2c-sis630 b/Documentation/i2c/busses/i2c-sis630
--- a/Documentation/i2c/busses/i2c-sis630       1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-sis630       2005-02-08 15:55:37.000000000 +0100
+Thank Yous
Thank You?
diff -Naur a/Documentation/i2c/busses/i2c-sis69x b/Documentation/i2c/busses/i2c-sis69x
--- a/Documentation/i2c/busses/i2c-sis69x	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/busses/i2c-sis69x	2005-02-05 12:26:00.000000000 +0100
+ - patch for Sis655
diff -Naur a/Documentation/i2c/chips/ds1621 b/Documentation/i2c/chips/ds1621
--- a/Documentation/i2c/chips/ds1621	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/ds1621	2005-02-04 23:14:00.000000000 +0100
+Temperature readings are internally converted into a 9bit value to be
+read straight via the i2c-bus, but higher resolutions may be obtained
+with little effort via 'precise_temp' access or using a simple algorithm.
What is precise_temp? Maybe something that has existed but which does not exists
+As for alarms, you can read the alarm status of the DS1621 via the
+'alarms' proc file interface. The result consits mainly of bit 6 and 5
For 2.6 kernels this should be changed into sysfs.

+Higher accuracy of the temperature reading can be achieved using the
AFAIK, the accuracy is still the same with this method, only the 
resolution is increased.
diff -Naur a/Documentation/i2c/chips/gl518sm b/Documentation/i2c/chips/gl518sm
--- a/Documentation/i2c/chips/gl518sm	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/gl518sm	2005-02-04 23:20:00.000000000 +0100
+	Frodo Looijaard <frodol at>,
+        Kyösti Mälkki <kmalkki at>
+	Hong-Gunn Chew <hglinux at>
+	Jean Delvare <khali at>
Identation problem

+IMPORTANT: For the revision 0x00 chip, the
+           in0, in1, and in2 values (+5, +3, and +12) CANNOT be read
Would be better as (+5V, +3V, and +12V)
diff -Naur a/Documentation/i2c/chips/it87 b/Documentation/i2c/chips/it87
--- a/Documentation/i2c/chips/it87	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/it87	2005-02-05 12:41:00.000000000 +0100
+The sensor type can be set at runtime as of release 2.8.2.
This should be removed or if it also applies to the 2.6 kernel driver, should
be converted to a kernel version number.
diff -Naur a/Documentation/i2c/chips/lm85 b/Documentation/i2c/chips/lm85
--- a/Documentation/i2c/chips/lm85	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/lm85	2005-02-05 21:03:00.000000000 +0100
+To smooth the response of fans to changes in temperature, the LM85 has
+an optional filter for smoothing temperatures.  The ADM1027 has the
+same config option but uses it to rate limit the changes to fan speed
+instead.  In libsensors, we associate the smoothing feature with a
Is it really done in the library part or in the driver part?
+zone in the LM85 and with a PWM in the ADM1027.
+      0    PWM alwasy 0%  (off)
diff -Naur a/Documentation/i2c/chips/pcf8574 b/Documentation/i2c/chips/pcf8574
--- a/Documentation/i2c/chips/pcf8574	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/pcf8574	2005-02-05 11:55:00.000000000 +0100
+	 Aurelien Jarno <aurel32 at>,
Would it be possible to change my email address to aurelien at so that 
it is coherent through all the docs?
diff -Naur a/Documentation/i2c/chips/pcf8591 b/Documentation/i2c/chips/pcf8591
--- a/Documentation/i2c/chips/pcf8591	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/pcf8591	2005-02-05 12:01:00.000000000 +0100
+For more informations see the datasheet.
I think it is to close from French. Maybe "See the datasheet for details." 
would be better.
diff -Naur a/Documentation/i2c/chips/w83627hf b/Documentation/i2c/chips/w83627hf
--- a/Documentation/i2c/chips/w83627hf	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/w83627hf	2005-02-05 11:07:00.000000000 +0100
+initialization that were required in the w83781d driver
+(lm_sensors releases 2.7.0 and earlier).
This should be removed or if it also applies to the 2.6 kernel driver, should
be converted to a kernel version number.
+For further information on this driver, /proc values, etc.
+see the w83781d driver documentation.
This is now /sys
diff -Naur a/Documentation/i2c/chips/w83781d b/Documentation/i2c/chips/w83781d
--- a/Documentation/i2c/chips/w83781d	1970-01-01 01:00:00.000000000 +0100
+++ b/Documentation/i2c/chips/w83781d	2005-02-05 11:01:00.000000000 +0100
+W8783S, and W83627HF chips, and the Asus AS99127F chips.
+AS9917F looks more like a w83782d).

  .''`.  Aurelien Jarno	              GPG: 1024D/F1BCDB73
 : :' :  Debian GNU/Linux developer | Electrical Engineer
 `. `'   aurel32 at         | aurelien at
   `- |

More information about the lm-sensors mailing list