diff options
author | Jean Delvare <khali@linux-fr.org> | 2007-12-07 01:13:42 +0300 |
---|---|---|
committer | Mark M. Hoffman <mhoffman@lightlink.com> | 2008-02-08 04:39:42 +0300 |
commit | 67b671bceb4a8340a30929e9642620d99ed5ad76 (patch) | |
tree | d302333633bdbd752151933366aaaabfdc60e719 /drivers/connector | |
parent | b20ff13a6ad64f07ce78c75e6a335c185270d73c (diff) | |
download | linux-67b671bceb4a8340a30929e9642620d99ed5ad76.tar.xz |
hwmon: Let the user override the detected Super-I/O device ID
While it is possible to force SMBus-based hardware monitoring chip
drivers to drive a not officially supported device, we do not have this
possibility for Super-I/O-based drivers. That's unfortunate because
sometimes newer chips are fully compatible and just forcing the driver
to load would work. Instead of that we have to tell the users to
recompile the kernel driver, which isn't an easy task for everyone.
So, I propose that we add a module parameter to all Super-I/O based
hardware monitoring drivers, letting advanced users force the driver
to load on their machine. The user has to provide the device ID of a
supposedly compatible device. This requires looking at the source code or
a datasheet, so I am confident that users can't randomly force a driver
without knowing what they are doing. Thus this should be relatively safe.
As you can see from the code, the implementation is pretty simple and
unintrusive.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Hans de Goede <j.w.r.degoede@hhs.nl>
Signed-off-by: Mark M. Hoffman <mhoffman@lightlink.com>
Diffstat (limited to 'drivers/connector')
0 files changed, 0 insertions, 0 deletions