hwmon: Add support for newer uGuru's

This patch adds a new driver for the hardware monitoring features of the
third revision of the Abit uGuru chip, found on recent Abit
motherboards. This is an entirely different beast then the first and
second revision (its again a winbond microcontroller, but the "protocol"
to talk to it and the bank addresses are very different.

Signed-off-by: Hans de Goede <j.w.r.degoede@hhs.nl>
Signed-off-by: Mark M. Hoffman <mhoffman@lightlink.com>
This commit is contained in:
Hans de Goede 2007-06-17 00:28:45 +02:00 committed by Mark M. Hoffman
parent aba5073d3f
commit 3faa1ffb4f
6 changed files with 1248 additions and 21 deletions

View file

@ -2,7 +2,7 @@ Kernel driver abituguru
======================= =======================
Supported chips: Supported chips:
* Abit uGuru revision 1-3 (Hardware Monitor part only) * Abit uGuru revision 1 & 2 (Hardware Monitor part only)
Prefix: 'abituguru' Prefix: 'abituguru'
Addresses scanned: ISA 0x0E0 Addresses scanned: ISA 0x0E0
Datasheet: Not available, this driver is based on reverse engineering. Datasheet: Not available, this driver is based on reverse engineering.
@ -20,8 +20,8 @@ Supported chips:
uGuru 2.1.0.0 ~ 2.1.2.8 (AS8, AV8, AA8, AG8, AA8XE, AX8) uGuru 2.1.0.0 ~ 2.1.2.8 (AS8, AV8, AA8, AG8, AA8XE, AX8)
uGuru 2.2.0.0 ~ 2.2.0.6 (AA8 Fatal1ty) uGuru 2.2.0.0 ~ 2.2.0.6 (AA8 Fatal1ty)
uGuru 2.3.0.0 ~ 2.3.0.9 (AN8) uGuru 2.3.0.0 ~ 2.3.0.9 (AN8)
uGuru 3.0.0.0 ~ 3.0.1.2 (AW8, AL8, NI8) uGuru 3.0.0.0 ~ 3.0.x.x (AW8, AL8, AT8, NI8 SLI, AT8 32X, AN8 32X,
uGuru 4.xxxxx? (AT8 32X) (2) AW9D-MAX) (2)
1) For revisions 2 and 3 uGuru's the driver can autodetect the 1) For revisions 2 and 3 uGuru's the driver can autodetect the
sensortype (Volt or Temp) for bank1 sensors, for revision 1 uGuru's sensortype (Volt or Temp) for bank1 sensors, for revision 1 uGuru's
this doesnot always work. For these uGuru's the autodection can this doesnot always work. For these uGuru's the autodection can
@ -30,8 +30,9 @@ Supported chips:
bank1_types=1,1,0,0,0,0,0,2,0,0,0,0,2,0,0,1 bank1_types=1,1,0,0,0,0,0,2,0,0,0,0,2,0,0,1
You may also need to specify the fan_sensors option for these boards You may also need to specify the fan_sensors option for these boards
fan_sensors=5 fan_sensors=5
2) The current version of the abituguru driver is known to NOT work 2) There is a seperate abituguru3 driver for these motherboards,
on these Motherboards the abituguru (without the 3 !) driver will not work on these
motherboards (and visa versa)!
Authors: Authors:
Hans de Goede <j.w.r.degoede@hhs.nl>, Hans de Goede <j.w.r.degoede@hhs.nl>,
@ -43,8 +44,10 @@ Module Parameters
----------------- -----------------
* force: bool Force detection. Note this parameter only causes the * force: bool Force detection. Note this parameter only causes the
detection to be skipped, if the uGuru can't be read detection to be skipped, and thus the insmod to
the module initialization (insmod) will still fail. succeed. If the uGuru can't be read the actual hwmon
driver will not load and thus no hwmon device will get
registered.
* bank1_types: int[] Bank1 sensortype autodetection override: * bank1_types: int[] Bank1 sensortype autodetection override:
-1 autodetect (default) -1 autodetect (default)
0 volt sensor 0 volt sensor
@ -69,13 +72,15 @@ dmesg | grep abituguru
Description Description
----------- -----------
This driver supports the hardware monitoring features of the Abit uGuru chip This driver supports the hardware monitoring features of the first and
found on Abit uGuru featuring motherboards (most modern Abit motherboards). second revision of the Abit uGuru chip found on Abit uGuru featuring
motherboards (most modern Abit motherboards).
The uGuru chip in reality is a Winbond W83L950D in disguise (despite Abit The first and second revision of the uGuru chip in reality is a Winbond
claiming it is "a new microprocessor designed by the ABIT Engineers"). W83L950D in disguise (despite Abit claiming it is "a new microprocessor
Unfortunatly this doesn't help since the W83L950D is a generic designed by the ABIT Engineers"). Unfortunatly this doesn't help since the
microcontroller with a custom Abit application running on it. W83L950D is a generic microcontroller with a custom Abit application running
on it.
Despite Abit not releasing any information regarding the uGuru, Olle Despite Abit not releasing any information regarding the uGuru, Olle
Sandberg <ollebull@gmail.com> has managed to reverse engineer the sensor part Sandberg <ollebull@gmail.com> has managed to reverse engineer the sensor part

View file

@ -0,0 +1,65 @@
Kernel driver abituguru3
========================
Supported chips:
* Abit uGuru revision 3 (Hardware Monitor part, reading only)
Prefix: 'abituguru3'
Addresses scanned: ISA 0x0E0
Datasheet: Not available, this driver is based on reverse engineering.
Note:
The uGuru is a microcontroller with onboard firmware which programs
it to behave as a hwmon IC. There are many different revisions of the
firmware and thus effectivly many different revisions of the uGuru.
Below is an incomplete list with which revisions are used for which
Motherboards:
uGuru 1.00 ~ 1.24 (AI7, KV8-MAX3, AN7)
uGuru 2.0.0.0 ~ 2.0.4.2 (KV8-PRO)
uGuru 2.1.0.0 ~ 2.1.2.8 (AS8, AV8, AA8, AG8, AA8XE, AX8)
uGuru 2.3.0.0 ~ 2.3.0.9 (AN8)
uGuru 3.0.0.0 ~ 3.0.x.x (AW8, AL8, AT8, NI8 SLI, AT8 32X, AN8 32X,
AW9D-MAX)
The abituguru3 driver is only for revison 3.0.x.x motherboards,
this driver will not work on older motherboards. For older
motherboards use the abituguru (without the 3 !) driver.
Authors:
Hans de Goede <j.w.r.degoede@hhs.nl>,
(Initial reverse engineering done by Louis Kruger)
Module Parameters
-----------------
* force: bool Force detection. Note this parameter only causes the
detection to be skipped, and thus the insmod to
succeed. If the uGuru can't be read the actual hwmon
driver will not load and thus no hwmon device will get
registered.
* verbose: bool Should the driver be verbose?
0/off/false normal output
1/on/true + verbose error reporting (default)
Default: 1 (the driver is still in the testing phase)
Description
-----------
This driver supports the hardware monitoring features of the third revision of
the Abit uGuru chip, found on recent Abit uGuru featuring motherboards.
The 3rd revision of the uGuru chip in reality is a Winbond W83L951G.
Unfortunatly this doesn't help since the W83L951G is a generic microcontroller
with a custom Abit application running on it.
Despite Abit not releasing any information regarding the uGuru revision 3,
Louis Kruger has managed to reverse engineer the sensor part of the uGuru.
Without his work this driver would not have been possible.
Known Issues
------------
The voltage and frequency control parts of the Abit uGuru are not supported,
neither is writing any of the sensor settings and writing / reading the
fanspeed control registers (FanEQ)
If you encounter any problems please mail me <j.w.r.degoede@hhs.nl> and
include the output of: "dmesg | grep abituguru"

View file

@ -29,17 +29,34 @@ config HWMON_VID
default n default n
config SENSORS_ABITUGURU config SENSORS_ABITUGURU
tristate "Abit uGuru" tristate "Abit uGuru (rev 1 & 2)"
depends on EXPERIMENTAL depends on EXPERIMENTAL
help help
If you say yes here you get support for the Abit uGuru chips If you say yes here you get support for the sensor part of the first
sensor part. The voltage and frequency control parts of the Abit and second revision of the Abit uGuru chip. The voltage and frequency
uGuru are not supported. The Abit uGuru chip can be found on Abit control parts of the Abit uGuru are not supported. The Abit uGuru
uGuru featuring motherboards (most modern Abit motherboards). chip can be found on Abit uGuru featuring motherboards (most modern
Abit motherboards from before end 2005). For more info and a list
of which motherboards have which revision see
Documentation/hwmon/abituguru
This driver can also be built as a module. If so, the module This driver can also be built as a module. If so, the module
will be called abituguru. will be called abituguru.
config SENSORS_ABITUGURU3
tristate "Abit uGuru (rev 3)"
depends on HWMON && EXPERIMENTAL
help
If you say yes here you get support for the sensor part of the
third revision of the Abit uGuru chip. Only reading the sensors
and their settings is supported. The third revision of the Abit
uGuru chip can be found on recent Abit motherboards (since end
2005). For more info and a list of which motherboards have which
revision see Documentation/hwmon/abituguru3
This driver can also be built as a module. If so, the module
will be called abituguru3.
config SENSORS_AD7418 config SENSORS_AD7418
tristate "Analog Devices AD7416, AD7417 and AD7418" tristate "Analog Devices AD7416, AD7417 and AD7418"
depends on I2C && EXPERIMENTAL depends on I2C && EXPERIMENTAL

View file

@ -14,6 +14,7 @@ obj-$(CONFIG_SENSORS_W83781D) += w83781d.o
obj-$(CONFIG_SENSORS_W83791D) += w83791d.o obj-$(CONFIG_SENSORS_W83791D) += w83791d.o
obj-$(CONFIG_SENSORS_ABITUGURU) += abituguru.o obj-$(CONFIG_SENSORS_ABITUGURU) += abituguru.o
obj-$(CONFIG_SENSORS_ABITUGURU3)+= abituguru3.o
obj-$(CONFIG_SENSORS_AD7418) += ad7418.o obj-$(CONFIG_SENSORS_AD7418) += ad7418.o
obj-$(CONFIG_SENSORS_ADM1021) += adm1021.o obj-$(CONFIG_SENSORS_ADM1021) += adm1021.o
obj-$(CONFIG_SENSORS_ADM1025) += adm1025.o obj-$(CONFIG_SENSORS_ADM1025) += adm1025.o

View file

@ -16,9 +16,9 @@
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/ */
/* /*
This driver supports the sensor part of the custom Abit uGuru chip found This driver supports the sensor part of the first and second revision of
on Abit uGuru motherboards. Note: because of lack of specs the CPU / RAM / the custom Abit uGuru chip found on Abit uGuru motherboards. Note: because
etc voltage & frequency control is not supported! of lack of specs the CPU/RAM voltage & frequency control is not supported!
*/ */
#include <linux/module.h> #include <linux/module.h>
#include <linux/sched.h> #include <linux/sched.h>

1139
drivers/hwmon/abituguru3.c Normal file

File diff suppressed because it is too large Load diff