-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'hwmon-for-linus' of git://jdelvare.pck.nerim.net/jdelva…
…re-2.6 * 'hwmon-for-linus' of git://jdelvare.pck.nerim.net/jdelvare-2.6: (32 commits) Use menuconfig objects - hwmon hwmon/smsc47b397: Use dynamic sysfs callbacks hwmon/smsc47b397: Convert to a platform driver hwmon/w83781d: Deprecate W83627HF support hwmon/w83781d: Use dynamic sysfs callbacks hwmon/w83781d: Be less i2c_client-centric hwmon/w83781d: Clean up conversion macros hwmon/w83781d: No longer use i2c-isa hwmon/ams: Do not print error on systems without apple motion sensor hwmon/ams: Fix I2C read retry logic hwmon: New AD7416, AD7417 and AD7418 driver hwmon/coretemp: Add documentation hwmon: New coretemp driver i386: Use functions from library in msr driver i386: Add safe variants of rdmsr_on_cpu and wrmsr_on_cpu hwmon/lm75: Use dynamic sysfs callbacks hwmon/lm78: Use dynamic sysfs callbacks hwmon/lm78: Be less i2c_client-centric hwmon/lm78: No longer use i2c-isa hwmon: New max6650 driver ...
- Loading branch information
Showing
29 changed files
with
3,777 additions
and
1,692 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
Kernel driver coretemp | ||
====================== | ||
|
||
Supported chips: | ||
* All Intel Core family | ||
Prefix: 'coretemp' | ||
CPUID: family 0x6, models 0xe, 0xf | ||
Datasheet: Intel 64 and IA-32 Architectures Software Developer's Manual | ||
Volume 3A: System Programming Guide | ||
|
||
Author: Rudolf Marek | ||
|
||
Description | ||
----------- | ||
|
||
This driver permits reading temperature sensor embedded inside Intel Core CPU. | ||
Temperature is measured in degrees Celsius and measurement resolution is | ||
1 degree C. Valid temperatures are from 0 to TjMax degrees C, because | ||
the actual value of temperature register is in fact a delta from TjMax. | ||
|
||
Temperature known as TjMax is the maximum junction temperature of processor. | ||
Intel defines this temperature as 85C or 100C. At this temperature, protection | ||
mechanism will perform actions to forcibly cool down the processor. Alarm | ||
may be raised, if the temperature grows enough (more than TjMax) to trigger | ||
the Out-Of-Spec bit. Following table summarizes the exported sysfs files: | ||
|
||
temp1_input - Core temperature (in millidegrees Celsius). | ||
temp1_crit - Maximum junction temperature (in millidegrees Celsius). | ||
temp1_crit_alarm - Set when Out-of-spec bit is set, never clears. | ||
Correct CPU operation is no longer guaranteed. | ||
temp1_label - Contains string "Core X", where X is processor | ||
number. | ||
|
||
The TjMax temperature is set to 85 degrees C if undocumented model specific | ||
register (UMSR) 0xee has bit 30 set. If not the TjMax is 100 degrees C as | ||
(sometimes) documented in processor datasheet. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
Kernel driver max6650 | ||
===================== | ||
|
||
Supported chips: | ||
* Maxim 6650 / 6651 | ||
Prefix: 'max6650' | ||
Addresses scanned: I2C 0x1b, 0x1f, 0x48, 0x4b | ||
Datasheet: http://pdfserv.maxim-ic.com/en/ds/MAX6650-MAX6651.pdf | ||
|
||
Authors: | ||
Hans J. Koch <hjk@linutronix.de> | ||
John Morris <john.morris@spirentcom.com> | ||
Claus Gindhart <claus.gindhart@kontron.com> | ||
|
||
Description | ||
----------- | ||
|
||
This driver implements support for the Maxim 6650/6651 | ||
|
||
The 2 devices are very similar, but the Maxim 6550 has a reduced feature | ||
set, e.g. only one fan-input, instead of 4 for the 6651. | ||
|
||
The driver is not able to distinguish between the 2 devices. | ||
|
||
The driver provides the following sensor accesses in sysfs: | ||
|
||
fan1_input ro fan tachometer speed in RPM | ||
fan2_input ro " | ||
fan3_input ro " | ||
fan4_input ro " | ||
fan1_target rw desired fan speed in RPM (closed loop mode only) | ||
pwm1_enable rw regulator mode, 0=full on, 1=open loop, 2=closed loop | ||
pwm1 rw relative speed (0-255), 255=max. speed. | ||
Used in open loop mode only. | ||
fan1_div rw sets the speed range the inputs can handle. Legal | ||
values are 1, 2, 4, and 8. Use lower values for | ||
faster fans. | ||
|
||
Module parameters | ||
----------------- | ||
|
||
If your board has a BIOS that initializes the MAX6650/6651 correctly, you can | ||
simply load your module without parameters. It won't touch the configuration | ||
registers then. If your board BIOS doesn't initialize the chip, or you want | ||
different settings, you can set the following parameters: | ||
|
||
voltage_12V: 5=5V fan, 12=12V fan, 0=don't change | ||
prescaler: Possible values are 1,2,4,8,16, or 0 for don't change | ||
clock: The clock frequency in Hz of the chip the driver should assume [254000] | ||
|
||
Please have a look at the MAX6650/6651 data sheet and make sure that you fully | ||
understand the meaning of these parameters before you attempt to change them. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.