Hi,
with the recent submission of an Intel MID watchdog driver, we now have
config INTEL_SCU_WATCHDOG
bool "Intel SCU Watchdog for Mobile Platforms"
depends on X86_INTEL_MID
---help---
Hardware driver for the watchdog time built into the Intel SCU
for Intel Mobile Platforms.
config INTEL_MID_WATCHDOG
tristate "Intel MID Watchdog Timer"
depends on X86_INTEL_MID
--help--
Watchdog timer driver built into the Intel SCU for Intel MID Platforms.
This driver currently supports only the watchdog evolution
implementation in SCU, available for Merrifield generation.
Furthermore, in the SCU watchdog driver initialization code, we have
...
* If it isn't an intel MID device then it doesn't have this watchdog
*/
if (!intel_mid_identify_cpu())
return -ENODEV;
I must admit I find this very confusing. Both watchdogs have the same
dependencies. The MID watchdog driver only instantiates for Tangier,
while the SCU watchdog driver instantiates for all MID CPUs (specfically
including Tangier, but also Penwell and Cloverview and, from earlier
commit logs, Moorsetown).
I understand I was told earlier that the supported devices would be
"sufficiently different" to warrant separate drivers, but this doesn't
really make sense to me, at least not without further explanation.
Can someone please clarify which driver is supposed to work on which device,
and why there are now two watchdog drivers for Tangier (or at least two
watchdog drivers which instantiate on Tangier) ? Does the SCU driver work
on Tangier, or does it not ? If not, why is there no code in the SCU driver
which would cause it to fail to instantiate on Tangier, and why is this
limitation not mentioned in Kconfig ? If yes, why do we need separate drivers
in the first place ?
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
