pm24.git/drivers/hwmon/abituguru3.c, branch v3.6

hwmon: (abituguru3) Use struct dev_pm_ops for power management

2012-07-22T04:48:44Z

Make the Abit uGuru rev. 3 driver define its PM callbacks through a struct dev_pm_ops object rather than by using legacy PM hooks in struct platform_driver. Signed-off-by: Rafael J. Wysocki [linux@roeck-us.net: CONFIG_PM->CONFIG_PM_SLEEP, and remove unnecessary ()] Signed-off-by: Guenter Roeck

hwmon: (abituguru3) Fix multi-line comments

2012-03-19T01:27:12Z

Cc: Hans de Goede Cc: Alistair John Strachan Signed-off-by: Guenter Roeck

hwmon: (abituguru3) Fix checkpatch issues

2012-03-19T01:26:45Z

Fixed: ERROR: do not use assignment in if condition ERROR: "foo* bar" should be "foo *bar" WARNING: line over 80 characters Not fixed: WARNING: msleep < 20ms can sleep for up to 20ms Cc: Hans de Goede Reviewed-by: Robert Coulson Signed-off-by: Guenter Roeck

module_param: make bool parameters really bool (drivers & misc)

2012-01-12T23:02:20Z

module_param(bool) used to counter-intuitively take an int. In fddd5201 (mid-2009) we allowed bool or int/unsigned int using a messy trick. It's time to remove the int/unsigned int option. For this version it'll simply give a warning, but it'll break next kernel version. Acked-by: Mauro Carvalho Chehab Signed-off-by: Rusty Russell

hwmon: (abituguru) Depend on DMI

2011-05-25T18:43:33Z

The abituguru drivers are only built on X86, where DMI support is now enabled by default. So let these drivers depend on DMI, for the following gains: * Robustness and safety. Detection of these devices is weak and uses non-standard methods, it should really be limited to Abit boards unless the user explicitly asks otherwise. * Code simplicity. The code is easier to read without ifdefs. * Better build testing coverage. Now there's only one way to build the drivers, so no risk of build failure on exotic systems. Signed-off-by: Jean Delvare Acked-by: Guenter Roeck Acked-by: Alistair John Strachan Acked-by: Hans de Goede

Fix common misspellings

2011-03-31T14:26:23Z

Fixes generated by 'codespell' and manually reviewed. Signed-off-by: Lucas De Marchi

hwmon: (abituguru*) Update my email address

2011-03-21T16:59:36Z

Signed-off-by: Hans de Goede Signed-off-by: Jean Delvare

hwmon: (abituguru3) Use pr_fmt and pr_

2011-01-08T18:55:01Z

Added #define pr_fmt KBUILD_MODNAME ": " fmt Converted printks to pr_ Coalesced any long formats Removed prefixes from formats Added a few static strings to standardize logging messages. Signed-off-by: Joe Perches Signed-off-by: Guenter Roeck

hwmon: Include instead of

2009-09-15T15:18:13Z

Drivers should be including instead of . Signed-off-by: H Hartley Sweeten Cc: Alistair John Strachan Cc: Nicolas Boichat Cc: Juerg Haefliger Cc: Frank Seidel Acked-by: Jim Cromie Cc: "Mark M. Hoffman" Cc: Roger Lucas Signed-off-by: Jean Delvare

hwmon: (abituguru3) Support multiple DMI strings per chip ID

2009-09-15T15:18:10Z

Most known Abit motherboards have unique uguru chip IDs. However, some "refresh" boards keep the same chip ID but have a different DMI string. As our DMI board string matching is (necessarily) strict, some boards were failing DMI detection, and as the old probe method was also failing, the driver would not load. The only known boards affected by this problem are the IP35 Pro XE (vs IP35 Pro) and the AB9 Pro (vs AB9). Is it not sufficient to relax the match criteria, as some boards (e.g. the AB9 Quad GT) have different uguru chip IDs. This patch replaces the dmi_name string with a NULL terminated array of strings to be matched per uguru chip ID. It has been compile and runtime tested (thanks Rune). References: https://bugs.launchpad.net/bugs/298798 Signed-off-by: Alistair John Strachan Tested-by: Rune Svendsen Acked-by: Hans de Goede Signed-off-by: Jean Delvare