<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/drivers/hwmon, branch v3.3-rc7</title>
<subtitle>Linux kernel source tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/'/>
<entry>
<title>hwmon: (jc42) Add support for AT30TS00, TS3000GB2, TSE2002GB2, and MCP9804</title>
<updated>2012-03-07T17:48:44+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2012-03-05T19:13:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=1bd612a25855f4cc9345052b53d7da697dba6358'/>
<id>1bd612a25855f4cc9345052b53d7da697dba6358</id>
<content type='text'>
Also update IDT datasheet locations.

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Cc: stable@vger.kernel.org # 3.0+
Acked-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Also update IDT datasheet locations.

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Cc: stable@vger.kernel.org # 3.0+
Acked-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (zl6100) Maintain delay parameter in driver instance data</title>
<updated>2012-03-07T17:48:43+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2012-03-07T11:58:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=7ad6307ad6968ce25cecf209d4822d4c722be030'/>
<id>7ad6307ad6968ce25cecf209d4822d4c722be030</id>
<content type='text'>
A global delay parameter has the side effect of being overwritten with 0 if a
single ZL2004 or ZL6105 is instantiated. If other chips supported by the same
driver are in the system, this will result in access errors for those chips.

To solve the problem, keep a per-instance copy of the delay parameter, and do
not change the original parameter.

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Cc: stable@vger.kernel.org # 3.1+
Acked-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A global delay parameter has the side effect of being overwritten with 0 if a
single ZL2004 or ZL6105 is instantiated. If other chips supported by the same
driver are in the system, this will result in access errors for those chips.

To solve the problem, keep a per-instance copy of the delay parameter, and do
not change the original parameter.

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Cc: stable@vger.kernel.org # 3.1+
Acked-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (pmbus_core) Fix maximum number of POUT alarm attributes</title>
<updated>2012-03-07T17:48:42+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2012-03-04T16:10:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=7cb3c44fb1f7999e4c53b6a52de6bc25da6de079'/>
<id>7cb3c44fb1f7999e4c53b6a52de6bc25da6de079</id>
<content type='text'>
There are up to three POUT alarm attributes, not two, since cap_alarm was added.

Reported-by: Michele Petracca &lt;mi.petracca@gmail.com&gt;
Cc: stable@vger.kernel.org # 3.0+ [3.0 will need backport]
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There are up to three POUT alarm attributes, not two, since cap_alarm was added.

Reported-by: Michele Petracca &lt;mi.petracca@gmail.com&gt;
Cc: stable@vger.kernel.org # 3.0+ [3.0 will need backport]
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (jc42) Add support for ST Microelectronics STTS2002 and STTS3000</title>
<updated>2012-03-07T17:48:21+00:00</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2012-03-05T13:32:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=4de86126a712ba83fa038d277c8282f7ed466a4b'/>
<id>4de86126a712ba83fa038d277c8282f7ed466a4b</id>
<content type='text'>
These are fully compatible with Jedec JC 42.4 as far as I can see.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Cc: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
Cc: stable@vger.kernel.org # 3.0+
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
These are fully compatible with Jedec JC 42.4 as far as I can see.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Cc: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
Cc: stable@vger.kernel.org # 3.0+
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (f75375s) Catch some attempts to write to r/o registers</title>
<updated>2012-03-02T20:02:23+00:00</updated>
<author>
<name>Nikolaus Schulz</name>
<email>mail@microschulz.de</email>
</author>
<published>2012-02-28T21:15:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=15d1ad0cc9d2d3f549afddbcdbc9c3637f0d1331'/>
<id>15d1ad0cc9d2d3f549afddbcdbc9c3637f0d1331</id>
<content type='text'>
It makes no sense to attempt to manually configure the fan in auto mode,
or set the duty cycle directly in closed loop mode.  The corresponding
registers are then read-only.  If the user tries it nonetheless, error out
with EINVAL instead of silently doing nothing.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
[guenter.roeck@ericsson.com: Minor formatting cleanup]
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It makes no sense to attempt to manually configure the fan in auto mode,
or set the duty cycle directly in closed loop mode.  The corresponding
registers are then read-only.  If the user tries it nonetheless, error out
with EINVAL instead of silently doing nothing.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
[guenter.roeck@ericsson.com: Minor formatting cleanup]
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (f75375s) Properly map the F75387 automatic modes to pwm_enable</title>
<updated>2012-03-02T19:56:43+00:00</updated>
<author>
<name>Nikolaus Schulz</name>
<email>schulz@macnetix.de</email>
</author>
<published>2012-02-28T21:15:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=b17d6561acc16265b65b1e0d27b649829b61a7e3'/>
<id>b17d6561acc16265b65b1e0d27b649829b61a7e3</id>
<content type='text'>
The F75387 supports automatic fan control using either PWM duty cycle or
RPM speed values.  Make the driver detect the latter mode, and expose the
different modes in sysfs as per pwm_enable, so that the user can switch
between them.

The interpretation of the pwm_enable attribute for the F75387 is adjusted
to be a superset of those values used for similar Fintek chips which do
not support automatic duty mode, with 2 mapping to automatic speed mode,
and moving automatic duty mode to the new value 4.

Toggling the duty mode via pwm_enable is currently denied for the F75387,
as the chip then simply reinterprets the fan configuration register values
according to the new mode, switching between RPM and PWM units, which
makes this a dangerous operation.

This patch introduces a new pwm mode into the driver. This is necessary
because the new mode (automatic pwm mode, 4) may already be enabled by the
BIOS, and the driver should not break existing functionality. This was seen
on at least one board.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The F75387 supports automatic fan control using either PWM duty cycle or
RPM speed values.  Make the driver detect the latter mode, and expose the
different modes in sysfs as per pwm_enable, so that the user can switch
between them.

The interpretation of the pwm_enable attribute for the F75387 is adjusted
to be a superset of those values used for similar Fintek chips which do
not support automatic duty mode, with 2 mapping to automatic speed mode,
and moving automatic duty mode to the new value 4.

Toggling the duty mode via pwm_enable is currently denied for the F75387,
as the chip then simply reinterprets the fan configuration register values
according to the new mode, switching between RPM and PWM units, which
makes this a dangerous operation.

This patch introduces a new pwm mode into the driver. This is necessary
because the new mode (automatic pwm mode, 4) may already be enabled by the
BIOS, and the driver should not break existing functionality. This was seen
on at least one board.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (f75375s) Make pwm*_mode writable for the F75387</title>
<updated>2012-02-28T22:44:02+00:00</updated>
<author>
<name>Nikolaus Schulz</name>
<email>mail@microschulz.de</email>
</author>
<published>2012-02-28T21:15:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=edeea102857e33b5e9b17a3a2640da390732a693'/>
<id>edeea102857e33b5e9b17a3a2640da390732a693</id>
<content type='text'>
Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (f75375s) Fix writes to the pwm* attribute for the F75387</title>
<updated>2012-02-28T22:39:47+00:00</updated>
<author>
<name>Nikolaus Schulz</name>
<email>mail@microschulz.de</email>
</author>
<published>2012-02-28T21:15:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=331255d35d6f517020485aee38dbb8b8dfaa1642'/>
<id>331255d35d6f517020485aee38dbb8b8dfaa1642</id>
<content type='text'>
For the F75387, the register holding the current PWM duty cycle value is
r/o; changing it requires writing to the fan expect register instead.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
[guenter.roeck@ericsson.com: Simplified function parameters]
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
For the F75387, the register holding the current PWM duty cycle value is
r/o; changing it requires writing to the fan expect register instead.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
[guenter.roeck@ericsson.com: Simplified function parameters]
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (max34440) Fix resetting temperature history</title>
<updated>2012-02-24T16:06:15+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2012-02-24T11:44:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=dc91ad8e84593eb49c65cca70537088782b21e08'/>
<id>dc91ad8e84593eb49c65cca70537088782b21e08</id>
<content type='text'>
Temperature history is reset by writing 0x8000 into the peak temperature
register, not 0xffff.

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Acked-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Temperature history is reset by writing 0x8000 into the peak temperature
register, not 0xffff.

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Acked-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (f75375s) Fix register write order when setting fans to full speed</title>
<updated>2012-02-23T14:47:47+00:00</updated>
<author>
<name>Nikolaus Schulz</name>
<email>schulz@macnetix.de</email>
</author>
<published>2012-02-22T22:18:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=c1c1a3d012fe5e82a9a025fb4b5a4f8ee67a53f6'/>
<id>c1c1a3d012fe5e82a9a025fb4b5a4f8ee67a53f6</id>
<content type='text'>
By hwmon sysfs interface convention, setting pwm_enable to zero sets a fan
to full speed.  In the f75375s driver, this need be done by enabling
manual fan control, plus duty mode for the F875387 chip, and then setting
the maximum duty cycle.  Fix a bug where the two necessary register writes
were swapped, effectively discarding the setting to full-speed.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
Cc: Riku Voipio &lt;riku.voipio@iki.fi&gt;
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
By hwmon sysfs interface convention, setting pwm_enable to zero sets a fan
to full speed.  In the f75375s driver, this need be done by enabling
manual fan control, plus duty mode for the F875387 chip, and then setting
the maximum duty cycle.  Fix a bug where the two necessary register writes
were swapped, effectively discarding the setting to full-speed.

Signed-off-by: Nikolaus Schulz &lt;mail@microschulz.de&gt;
Cc: Riku Voipio &lt;riku.voipio@iki.fi&gt;
Signed-off-by: Guenter Roeck &lt;guenter.roeck@ericsson.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
