* watchdog: octeon: missing FROZEN hot plug notifier actions @ 2016-03-16 20:51 rcochran 2016-03-17 3:18 ` Guenter Roeck 0 siblings, 1 reply; 5+ messages in thread From: rcochran @ 2016-03-16 20:51 UTC (permalink / raw) To: Wim Van Sebroeck; +Cc: Guenter Roeck, linux-watchdog, rt In drivers/watchdog/octeon-wdt-main.c, the hot plug notifier callback, octeon_wdt_cpu_callback, does not handle events with CPU_TASKS_FROZEN set in the action code. Is this on purpose? If so, then why is it done that way? Thanks, Richard ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: watchdog: octeon: missing FROZEN hot plug notifier actions 2016-03-16 20:51 watchdog: octeon: missing FROZEN hot plug notifier actions rcochran @ 2016-03-17 3:18 ` Guenter Roeck 2016-03-17 8:08 ` rcochran 0 siblings, 1 reply; 5+ messages in thread From: Guenter Roeck @ 2016-03-17 3:18 UTC (permalink / raw) To: rcochran, Wim Van Sebroeck; +Cc: linux-watchdog, rt On 03/16/2016 01:51 PM, rcochran@linutronix.de wrote: > > In drivers/watchdog/octeon-wdt-main.c, the hot plug notifier callback, > octeon_wdt_cpu_callback, does not handle events with CPU_TASKS_FROZEN > set in the action code. > > Is this on purpose? If so, then why is it done that way? > What do you expect it to do ? My understanding is that CPU_TASKS_FROZEN is related to suspend/resume operations, which are not really common for typical applications using Octeon CPUs. If they now are, it might be worthwhile thinking about adding suspend/resume support to the driver. Thanks, Guenter ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: watchdog: octeon: missing FROZEN hot plug notifier actions 2016-03-17 3:18 ` Guenter Roeck @ 2016-03-17 8:08 ` rcochran 2016-03-17 13:04 ` Guenter Roeck 0 siblings, 1 reply; 5+ messages in thread From: rcochran @ 2016-03-17 8:08 UTC (permalink / raw) To: Guenter Roeck; +Cc: Wim Van Sebroeck, linux-watchdog, rt On Wed, Mar 16, 2016 at 08:18:22PM -0700, Guenter Roeck wrote: > On 03/16/2016 01:51 PM, rcochran@linutronix.de wrote: > > > >In drivers/watchdog/octeon-wdt-main.c, the hot plug notifier callback, > >octeon_wdt_cpu_callback, does not handle events with CPU_TASKS_FROZEN > >set in the action code. > > > >Is this on purpose? If so, then why is it done that way? > > > > What do you expect it to do ? I would expect that the driver handles FROZEN in the same way, enabling and disabling the watchdog interrupt on the hot plugged CPU. It looks like an oversight that FROZEN actions are ignored, but I wanted to be sure. > My understanding is that CPU_TASKS_FROZEN is related to suspend/resume operations, > which are not really common for typical applications using Octeon CPUs. If they now > are, it might be worthwhile thinking about adding suspend/resume support to the driver. Are they merely not common, or is suspend impossible on this machine? Even if the use case is uncommon, still the driver should be correct. Thanks, Richard ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: watchdog: octeon: missing FROZEN hot plug notifier actions 2016-03-17 8:08 ` rcochran @ 2016-03-17 13:04 ` Guenter Roeck 2016-03-17 13:51 ` rcochran 0 siblings, 1 reply; 5+ messages in thread From: Guenter Roeck @ 2016-03-17 13:04 UTC (permalink / raw) To: rcochran; +Cc: Wim Van Sebroeck, linux-watchdog, rt On 03/17/2016 01:08 AM, rcochran@linutronix.de wrote: > On Wed, Mar 16, 2016 at 08:18:22PM -0700, Guenter Roeck wrote: >> On 03/16/2016 01:51 PM, rcochran@linutronix.de wrote: >>> >>> In drivers/watchdog/octeon-wdt-main.c, the hot plug notifier callback, >>> octeon_wdt_cpu_callback, does not handle events with CPU_TASKS_FROZEN >>> set in the action code. >>> >>> Is this on purpose? If so, then why is it done that way? >>> >> >> What do you expect it to do ? > > I would expect that the driver handles FROZEN in the same way, > enabling and disabling the watchdog interrupt on the hot plugged CPU. > It looks like an oversight that FROZEN actions are ignored, but I > wanted to be sure. > >> My understanding is that CPU_TASKS_FROZEN is related to suspend/resume operations, >> which are not really common for typical applications using Octeon CPUs. If they now >> are, it might be worthwhile thinking about adding suspend/resume support to the driver. > > Are they merely not common, or is suspend impossible on this machine? > Even if the use case is uncommon, still the driver should be correct. > The default Octeon configuration at least enables CONFIG_PM and CONFIG_PM_SLEEP, so one can argue that it should be supported. If you submit a patch, would you be able to test your changes ? Thanks, Guenter ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: watchdog: octeon: missing FROZEN hot plug notifier actions 2016-03-17 13:04 ` Guenter Roeck @ 2016-03-17 13:51 ` rcochran 0 siblings, 0 replies; 5+ messages in thread From: rcochran @ 2016-03-17 13:51 UTC (permalink / raw) To: Guenter Roeck; +Cc: Wim Van Sebroeck, linux-watchdog, rt On Thu, Mar 17, 2016 at 06:04:30AM -0700, Guenter Roeck wrote: > The default Octeon configuration at least enables CONFIG_PM and CONFIG_PM_SLEEP, > so one can argue that it should be supported. If you submit a patch, would you > be able to test your changes ? No, due to -ENODEV. Sorry, Richard ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-03-17 13:51 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2016-03-16 20:51 watchdog: octeon: missing FROZEN hot plug notifier actions rcochran 2016-03-17 3:18 ` Guenter Roeck 2016-03-17 8:08 ` rcochran 2016-03-17 13:04 ` Guenter Roeck 2016-03-17 13:51 ` rcochran
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).