<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/hwmon, branch linux-2.6.23.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-2.6.23.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-2.6.23.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2008-01-09T17:14:03Z</updated>
<entry>
<title>hwmon: (w83627ehf) Be more careful when changing VID input level</title>
<updated>2008-01-09T17:14:03Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2008-01-06T13:18:44Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ca7a9bb95016d9233a04117c00bf460d86c3881c'/>
<id>urn:sha1:ca7a9bb95016d9233a04117c00bf460d86c3881c</id>
<content type='text'>
Already in Linus' tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=58e6e78119da2bdade9f6f588155f0320072b76b

Fix for:
http://bugzilla.kernel.org/show_bug.cgi?id=9634

The VID input level change has been reported to cause trouble. Be more
careful in this respect:
* Only change the level on the W83627EHF/EHG. The W83627DHG is more
  complex in this respect.
* Don't change the level if the VID pins are in output mode.
* Only set the level to TTL if VRM 9.x is used.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>hwmon/lm87: Disable VID when it should be</title>
<updated>2007-11-16T17:30:20Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-10-15T12:02:36Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=813476de234d567b55404d45a568abb95d1e05c6'/>
<id>urn:sha1:813476de234d567b55404d45a568abb95d1e05c6</id>
<content type='text'>
Already in Linus' tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=889af3d5d9586db795a06c619e416b4baee11da8

A stupid bit shifting bug caused the VID value to be always exported
even when the hardware is configured for something different.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>hwmon/lm87: Fix a division by zero</title>
<updated>2007-11-16T17:30:20Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-10-15T11:49:50Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f0eca992d6b690bc7b15c977ff8bb3e3bb42b827'/>
<id>urn:sha1:f0eca992d6b690bc7b15c977ff8bb3e3bb42b827</id>
<content type='text'>
Already in Linus' tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b965d4b7f614522170af6a7e450be0333792ccd2

Missing parentheses in the definition of FAN_FROM_REG cause a
division by zero for a specific register value.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Acked-by: Hans de Goede &lt;j.w.r.degoede@hhs.nl&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>hwmon/w83627hf: Don't assume bank 0</title>
<updated>2007-11-16T17:30:20Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-10-15T13:02:42Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=03c2cbb3ea89f121a6b67b008338f46b80df917c'/>
<id>urn:sha1:03c2cbb3ea89f121a6b67b008338f46b80df917c</id>
<content type='text'>
Already in Linus' tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d58df9cd788e6fb4962e1c8d5ba7b8b95d639a44

The bank switching code assumes that the bank selector is set to 0
when the driver is loaded. This might not be the case. This is exactly
the same bug as was fixed in the w83627ehf driver two months ago:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0956895aa6f8dc6a33210967252fd7787652537d

In practice, this bug was causing the sensor thermal types to be
improperly reported for my W83627THF the first time I was loading the
w83627hf driver. From the driver history, I'd say that it has been
broken since September 2005 (when we stopped resetting the chip by
default at driver load.)

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>hwmon/w83627hf: Fix setting fan min right after driver load</title>
<updated>2007-11-16T17:30:19Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-10-15T12:32:27Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a228ddd51bdfb5e22a33459cadd5f0e68ee433f6'/>
<id>urn:sha1:a228ddd51bdfb5e22a33459cadd5f0e68ee433f6</id>
<content type='text'>
Already in Linus' tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c09c5184a26158da32801e89d5849d774605f0dd

We need to read the fan clock dividers at initialization time,
otherwise the code in store_fan_min() may use uninitialized values.
That's pretty much the same bug and same fix as for the w83627ehf
driver last month.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>hwmon: End of I/O region off-by-one</title>
<updated>2007-09-09T14:38:37Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-08-29T08:39:57Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=15bde2f1a8e819213f54314505a5a0509673109b'/>
<id>urn:sha1:15bde2f1a8e819213f54314505a5a0509673109b</id>
<content type='text'>
Fix an off-by-one error in the I/O region declaration of two
hardware monitoring drivers (lm78 and w83781d.) We were requesting
one extra port at the end of the region.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
</content>
</entry>
<entry>
<title>hwmon: (smsc47m1) restore missing name attribute</title>
<updated>2007-08-12T18:39:44Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-08-12T11:58:50Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=68a50b567895ea677645ca3cebc484674123532d'/>
<id>urn:sha1:68a50b567895ea677645ca3cebc484674123532d</id>
<content type='text'>
The smsc47m1 driver no longer creates the name attribute used by
libsensors to identify chip types. It was lost during the conversion
to a platform driver. I was fooled by the fact that we do have a
group with all attributes, but only to delete them all at once. The
group is not used to create the attributes, so we have to explicitly
create the name attribute.

This fixes lm-sensors ticket #2236:
http://lm-sensors.org/ticket/2236

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
</content>
</entry>
<entry>
<title>hwmon: (w83627ehf) don't assume bank 0</title>
<updated>2007-08-12T18:38:31Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-08-11T11:57:05Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=0956895aa6f8dc6a33210967252fd7787652537d'/>
<id>urn:sha1:0956895aa6f8dc6a33210967252fd7787652537d</id>
<content type='text'>
Don't assume that the default bank is 0. For one thing, we don't even
set it to 0 when the driver is loaded, so the initial state might be
different. For another, something (say, the BIOS) might access the chip
and leave with the bank set to something different, so assuming that
the bank value is 0 is not safe.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
</content>
</entry>
<entry>
<title>hwmon: (w83627ehf) read fan_div values during probe</title>
<updated>2007-08-12T18:37:19Z</updated>
<author>
<name>Mark M. Hoffman</name>
<email>mhoffman@lightlink.com</email>
</author>
<published>2007-08-05T16:19:01Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ea7be66c44e56b6b7f1d61befc300871e855d43a'/>
<id>urn:sha1:ea7be66c44e56b6b7f1d61befc300871e855d43a</id>
<content type='text'>
This patch forces the driver to read the fan divider values during early init.
Otherwise, a call to store_fan_min() could access uninitialized variables.

Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>hwmon: fix w83781d temp sensor type setting</title>
<updated>2007-08-11T18:22:57Z</updated>
<author>
<name>Mark M. Hoffman</name>
<email>mhoffman@lightlink.com</email>
</author>
<published>2007-08-09T12:12:46Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=393cdad6267bc2abf75973d15310168ff3e15441'/>
<id>urn:sha1:393cdad6267bc2abf75973d15310168ff3e15441</id>
<content type='text'>
Commit 348753379a7704087603dad403603e825422fd9a introduced a regression that
caused temp2 and temp3 sensor type settings to be written to temp1 instead.
The result is that temp sensor readings could be way off.

Signed-off-by: Mark M. Hoffman &lt;mhoffman@lightlink.com&gt;
</content>
</entry>
</feed>
