linux-toradex.git/drivers/hwmon, branch v3.1

hwmon: (w83627ehf) Fix negative 8-bit temperature values

2011-10-20T14:17:08+00:00

Since 8-bit temperature values are now handled in 16-bit struct
members, values have to be cast to s8 for negative temperatures to be
properly handled. This is broken since kernel version 2.6.39
(commit bce26c58df86599c9570cee83eac58bdaae760e4.)

Signed-off-by: Jean Delvare 
Cc: Guenter Roeck 
Cc: stable@kernel.org	# 2.6.39+
Signed-off-by: Guenter Roeck

hwmon: (w83627ehf) Properly report thermal diode sensors

2011-10-13T23:51:29+00:00

The w83627ehf driver is improperly reporting thermal diode sensors as
type 2, instead of 3. This caused "sensors" and possibly other
monitoring tools to report these sensors as "transistor" instead of
"thermal diode".

Furthermore, diode subtype selection (CPU vs. external) is only
supported by the original W83627EHF/EHG. All later models only support
CPU diode type, and some (NCT6776F) don't even have the register in
question so we should avoid reading from it.

Signed-off-by: Jean Delvare 
Cc: stable@kernel.org
Signed-off-by: Guenter Roeck

hwmon: (coretemp) Avoid leaving around dangling pointer

2011-09-28T15:19:21+00:00

Storing the struct temp_data pointer allocated from create_core_data()
when returning an error has the potential of leaving around a pointer
to freed memory. Reset it to NULL for error returns.

Reported-by: Jan Beulich 
Signed-off-by: Guenter Roeck 
Acked-by: Jean Delvare

hwmon: (coretemp) Fixup platform device ID change

2011-09-28T15:19:20+00:00

With recent change "hwmon: (coretemp) don't use kernel assigned CPU
number as platform device ID", the microcode check is now running on
random CPU. Fix that by checking the microcode before creating the
platform device rather than at probe time.

Also avoid calling TO_PHYS_ID(cpu) twice in the same function, it's
expensive.

Signed-off-by: Jean Delvare 
Cc: Jan Beulich 
Cc: Guenter Roeck 
Signed-off-by: Guenter Roeck

hwmon: (coretemp) remove struct platform_data * parameter from create_core_data()

2011-09-23T17:39:11+00:00

The only caller of the function obtained the pointer solely for the
purpose of passing it to this function, while it can be easily
determined from the struct platform_device * parameter also passed.

Signed-off-by: Jan Beulich 
Signed-off-by: Guenter Roeck

hwmon: (coretemp) constify static data

2011-09-23T17:39:10+00:00

These arrays won't ever be written to, so protect them from
unintentional modification.

Signed-off-by: Jan Beulich 
Signed-off-by: Guenter Roeck

hwmon: (coretemp) don't use kernel assigned CPU number as platform device ID

2011-09-23T17:38:09+00:00

... as that has the potential to conflict with (particularly soft) CPU
hot removal and re-adding.

Signed-off-by: Jan Beulich 
[guenter.roeck@ericsson.com: use platform device ID as physical CPU id]
Signed-off-by: Guenter Roeck

hwmon: (ds620) Fix handling of negative temperatures

2011-09-22T00:25:18+00:00

Signed (negative) temperatures were not handled correctly.

Signed-off-by: Roland Stigge 
Signed-off-by: Guenter Roeck 
Cc: stable@kernel.org # v2.6.38+

hwmon: (w83791d) rename prototype parameter from 'register' to 'reg'

2011-09-22T00:25:18+00:00

gcc -Wextra warns "register is not at beginning of declaration" because the
compiler thinks the parameter has been marked as a 'register' variable, but
the function prototype intended to name the parameter "register" (which is a
reserved keyword).

Signed-off-by: Chris Peterson 
Acked-by: Marc Hulsman 
Signed-off-by: Guenter Roeck

hwmon: (coretemp) Don't use threshold registers for tempX_max

2011-09-22T00:25:18+00:00

With commit c814a4c7c4aad795835583344353963a0a673eb0, the meaning of tempX_max
was changed. It no longer returns the value of bits 8:15 of
MSR_IA32_TEMPERATURE_TARGET, but instead returns the value of CPU threshold
register T1. tempX_max_hyst was added to reflect the value of temperature
threshold register T0.

As it turns out, T0 and T1 are used on some systems, presumably by the BIOS.
Also, T0 and T1 don't have a well defined meaning. The thresholds may be used
as upper or lower limits, and it is not guaranteed that T0 <= T1. Thus, the new
attribute mapping does not reflect the actual usage of the threshold registers.
Also, register contents are changed during runtime by an entity other than the
hwmon driver, meaning the values cached by the driver do not reflect actual
register contents.

Revert most of c814a4c7c4aad795835583344353963a0a673eb0 to address the problem.
Support for T0 and T1 will be added back in with a separate commit, using new
attribute names.

Signed-off-by: Guenter Roeck 
Cc: Fenghua Yu 
Cc: Durgadoss R 
Acked-by: Jean Delvare