diff options
author | Petr Vandrovec <vandrove@vc.cvut.cz> | 2005-10-07 23:11:03 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2005-10-28 14:02:09 -0700 |
commit | ada0c2f8fa087dc1dbc34e096c318739b1d6381a (patch) | |
tree | e7f80d1336e2190c138fd4226438195e2f67839d /drivers/i2c/busses/i2c-i801.c | |
parent | bf813b314a2271c3f3903eb3279ebf5e09b3d27a (diff) | |
download | kernel-crypto-ada0c2f8fa087dc1dbc34e096c318739b1d6381a.tar.gz kernel-crypto-ada0c2f8fa087dc1dbc34e096c318739b1d6381a.tar.xz kernel-crypto-ada0c2f8fa087dc1dbc34e096c318739b1d6381a.zip |
[PATCH] hwmon: Fix w83627ehf/hf vs PNPACPI conflict (bug #4014)
This patch changes w83627hf and w83627ehf drivers to reserve only ports
0x295-0x296, instead of full 0x290-0x297 range. While some other
sensors chips respond to all addresses in 0x290-0x297 range, Winbond
chips respond to 0x295-0x296 only (this behavior is implied by
documentation, and matches behavior observed on real systems). This is
not problem alone, as no BIOS was found to put something at these unused
addresses, and sensors chip itself provides nothing there as well.
But in addition to only respond to these two addresses, also BIOS
vendors report in their ACPI-PnP structures that there is some resource
at I/O address 0x295 of length 2. And when later this hwmon driver
attempts to request region with base 0x290/length 8, it fails as one
request_region cannot span more than one device.
Due to this we have to ask only for region this hardware really
occupies, otherwise driver cannot be loaded on systems with ACPI-PnP
enabled.
Signed-off-by: Petr Vandrovec <vandrove@vc.cvut.cz>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/i2c/busses/i2c-i801.c')
0 files changed, 0 insertions, 0 deletions