* Tony Lindgren <tony@xxxxxxxxxxx> [121025 12:35]: > * Paul Walmsley <paul@xxxxxxxxx> [121025 12:32]: > > On Thu, 25 Oct 2012, Tony Lindgren wrote: > > > > > I wonder if we can now with multiple watchdogs supported to > > > have also PRM/CM implement omap_prcm_wdt_ioctl() that just > > > handles WDIOC_GETBOOTSTATUS and then just remove that handling > > > from the other omap watchdog drivers? > > > > The watchdog ioctl code needs access to internal watchdog state and > > functions, for example WDIOC_KEEPALIVE and WDIOC_SETTIMEOUT. How would > > the approach you're thinking of implement those operations? > > I have not looked how the watchdog subsystem handles multiple > watchdogs, but.. Can't we have the omap watchdog and twl watchdog > return -ENOTSUPP for WDIOC_GETBOOTSTATUS and have the watchdog > core fail over to the third wathcdog omap_prcm_wdt_ioctl() that > only implements WDIOC_GETBOOTSTATUS? Or something like that. After poking around a bit, probably the way to do this would be to have watchdog core bootstatus in addition to the bootstatus in struct watchdog_device? Then the omap_prcm watchdog could just initialize the watchdog core bootstatus, and the other omap watchdog drivers would just return the watchdog core bootstatus. Not that it's related to this patchset, just trying to figure out how it could be done in a generic way :) Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
