Hi Sergey,
> Actually the situation is worse. This driver pokes at SuperIO
> configuration registers, which are shared by all logical devices of the
> SuperIO chip. There are other drivers which touch these registers -
> e.g., drivers/hwmon/w83627hf.c handles the hardware monitor part of this
> chip; many other hwmon drivers handle other SuperIO devices. Hardware
> monitor drivers access the SuperIO config during initialization and do
> not request that port region, therefore loading hwmon drivers when
> w83697hf_wdt is loaded can lead to conflicts.
My opinion: a watchdog device is a special "harware monitoring" device and
thus we should combine the existing hwmon and watchdog code in one driver
where possible.
This will definitely not solve all SuperIO alike problems but it is a first
step towards having a single device driver for every autonomous piece of
electronics.
We can start with the Winbond SuperIO chipsets (Rudolf allready started
this (see his initial mail about Watchdog device classes)).
We should also change/convert the /dev/temperature setup in the watchdog
drivers to a hwmon-alike setup. I will definitely do this for the pcwd
drivers. And secondly we should define how we handle "temperature panic's"
because there we still have differences between the watchdog drivers.
Greetings,
Wim.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
