Use the driver data structure as the main device reference, instead of
the i2c client. It makes the driver a bit smaller, and makes more sense
as this is an hybrid driver, supporting both I2C and ISA devices.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

* Fix voltage rounding
* Drop useless macros
* Drop useless casts
* Turn macros evaluating their parameters more than once into inline
  functions
* Use signed variables for temperatures
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Reimplement the ISA device support as a platform driver, so that we no
longer rely on i2c-isa.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

It is not an error if a system has no ams hardware.  Do not clutter dmesg
in this case.
Signed-off-by: NOlaf Hering <olaf@aepfle.de>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Acked-by: NMichael Hanselmann <linux-kernel@hansmi.ch>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Fix sleep and retry logic in ams-i2c.
Signed-off-by: NStelian Pop <stelian@popies.net>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

A driver for the Analog Devices AD7416, AD7417 and AD7418 chips.
Signed-off-by: NAlessandro Zummo <a.zummo@towertech.it>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Add the support for the digital temperature sensor found in recent
Intel Core CPUs.
Signed-off-by: NRudolf Marek <r.marek@assembler.cz>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

This lets us get rid of macro-generated functions and shrinks the
driver size by about 8%.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

This lets us get rid of macro-generated functions and shrinks the
driver size significantly (about 10%).
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Use the driver data structure as the main device reference, instead of
the i2c client. It makes the driver a bit smaller, and makes more sense
as this is an hybrid driver, supporting both I2C and ISA devices.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Reimplement the ISA device support as a platform driver, so that we no
longer rely on i2c-isa.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

This driver supports the Maxim MAX6650 and MAX6651 fan speed
monitoring and control chips.
Signed-off-by: NHans J. Koch <hjk@linutronix.de>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

This lets us get rid of macro-generated functions and shrinks the
driver size by about 7%.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Also use pr_info instead of printk.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Convert the smsc47m1 driver from the nonsensical i2c-isa hack to a
regular platform driver.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Convert the w83627hf driver from the nonsensical i2c-isa hack to a
regular platform driver.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Some preliminary cleanups to the w83627hf hardware monitoring driver,
to make its conversion to a platform driver easier:

* Add missing include ioport.h
* Drop unused enum value any_chip
* Group module parameters
* Define and use DRVNAME
* Drop unused struct member lm75
* Move the handling of force_addr and device activation to
  w83627hf_find
* Consistently use local type in w83627hf_init_client
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Update the VID type for certain VIA processors and remove
the Itanium entries.
Signed-off-by: NRudolf Marek <r.marek@assembler.cz>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Some hardware monitoring drivers create the VID/VRM interface files
conditionally depending on the chip model or configuration. We should
only call vid_which_vrm() when we are actually going to create the
files. Not only it is more logical and efficient that way, but it also
prevents printing unnecessary warnings such as the one reported here:
http://lists.lm-sensors.org/pipermail/lm-sensors/2007-February/018954.htmlSigned-off-by: NJean Delvare <khali@linux-fr.org>

The smsc47m1 driver uses a mutex to protect the accesses to the
hardware registers. It really doesn't need any protection, as the
register space is flat. Get rid of that mutex for a smaller and
faster driver.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

The new SMSC LPC47M292 Super-I/O chip is a bit different from the
previous ones, it supports a 3rd fan, but unfortunately the pin
configuration registers are different.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

My understanding of the resource management in the Linux 2.6 device
driver model is that the devices should declare their resources, and
then when a driver attaches to a device, it should request the
resources it will be using, so as to mark them busy. This is how the
PCI and PNP subsystems work, you can clearly see the two levels of
resources (declaration and request) in /proc/ioports for these
devices.

So I believe that our platform hardware monitoring drivers should
follow the same logic. At the moment, we only declare the resources
but we do not request them. This patch adds the I/O region request
and release calls.
Signed-off-by: NJean Delvare <khali@linux-fr.org>
Acked-by: NJuerg Haefliger <juergh@gmail.com>

The new SMSC LPC47M292 Super-I/O chip includes a hardware monitoring
block which is compatible with those of the LPC47M192.
Signed-off-by: NJean Delvare <khali@linux-fr.org>
Cc: Hartmut Rick <linux@rick.claranet.de>

This reverts commit d05c7a80,
which included changes which should go via other subsystem
maintainers.

On ia64, kernel headers define REGION_OFFSET so we can't use that.
Reported by Andrew Morton.
Signed-off-by: NJean Delvare <khali@linux-fr.org>
Acked-by: NDavid Hubbard <david.c.hubbard@gmail.com>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

Users have been complaining about the w83627ehf driver flooding their logs
with debug messages like:

w83627ehf 9191-0a10: Increasing fan 4 clock divider from 64 to 128

or:

w83627ehf 9191-0290: Increasing fan 4 clock divider from 4 to 8

The reason is that we failed to actually write the LSB of the encoded clock
divider value for that fan, causing the next read to report the same old value
again and again.

Additionally, the fan number was improperly reported, making the bug harder to
find.
Signed-off-by: NJean Delvare <khali@linux-fr.org>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

Signed-off-by: NStephen Rothwell <sfr@canb.auug.org.au>
Acked-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: NPaul Mackerras <paulus@samba.org>

This just tidies up some of the remains.
Signed-off-by: NStephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: NPaul Mackerras <paulus@samba.org>

We need vid_which_vrm and vid_from_reg in the w83793 module.
Signed-off-by: NStefano Brivio <stefano.brivio@polimi.it>
Signed-off-by: NJean Delvare <khali@linux-fr.org>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

The configuration index port of the vt1211 can be accessed at two
different addresses 0x2e or 0x4e, depending on pin strappings. This
patch adds support to scan both addresses during module
initialization.
Signed-off-by: NJuerg Haefliger <juergh@gmail.com>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

I think I introduced a potential race condition bug with commit
51c997d8. I didn't realize it
back then, but platform_device_put and platform_device_release
both appear to free the platform data associated with the device.
This makes an explicit kfree redundant at best, and maybe even
racy, as it might occur while someone still holds a reference
to the platform device.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Fix an unused return value warning for the abituguru driver.
Also make sure the sysfs files are created before we register with
the hwmon class, and delete the sysfs files on driver removal.
Signed-off-by: NHans de Goede <j.w.r.degoede@hhs.nl>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Signed-off-by: NCorentin Labbe <corentin.labbe@geomatys.fr>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Signed-off-by: NDavid Hubbard <david.c.hubbard@gmail.com>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Subsystem infrastructure should normally register with "subsys_initcall",
so that it's available to drivers that may need to initialize early.

This patch updates "hwmon" to do so.  It's common for embedded systems to
have multifunction chips with hardware monitoring interfaces, and to have
those chips be used during system bringup ... before a normal "module_init"
would kick, or maybe just linked so they'd init before hwmon.
Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

This fixes a potential broken reference.
Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Cleanup a bogus legacy comment that has been replicated to many
hardware monitoring drivers.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Many hardware monitoring drivers use two different mutexes, one to
protect their per-device data structure, and one to protect the
access to the device registers. These mutexes are essentially
redundant, as the drivers are transfering values between the device
registers and the data cache, so they almost always end up holding
both mutexes at the same time. Using a single mutex will make the
code more simple and faster.

I am changing only two of the affected drivers here, the authors
of the other affected drivers are welcome to submit similar patches
if they want.
Signed-off-by: NJean Delvare <khali@linux-fr.org>

Signed-off-by: NJean Delvare <khali@linux-fr.org>

Let the user select the base PWM frequency when using the it87
hardware monitoring driver. Different frequencies can give better
control on some fans.

Also update the documentation to mention the PWM frequency control
files, with misc cleanups to the PWM section.
Signed-off-by: NJean Delvare <khali@linux-fr.org>