[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bf4e89bd11964f2e9f621f949adc338b@asem.it>
Date: Fri, 19 Feb 2021 14:01:56 +0000
From: Flavio Suligoi <f.suligoi@...m.it>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
CC: Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>,
"linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: R: [PATCH v1] watchdog: wdat: add param. to start wdog on module
insertion
Hi Mika,
> > const struct wdat_instruction *instr, u32 *value)
> > {
> > @@ -437,6 +443,8 @@ static int wdat_wdt_probe(struct platform_device
> *pdev)
> > }
> >
> > wdat_wdt_boot_status(wdat);
> > + if (start_enabled)
> > + wdat_wdt_start(&wdat->wdd);
>
> No objections to this if it is really needed. However, I think it is
> better start the watchdog after devm_watchdog_register_device() has been
> called so we have everything initialized.
Yes, it is needed. We need this feature to enable the watchdog
as soon as possible and this is essential for unmanned applications,
such as routers, water pumping stations, climate data collections,
etc.
Right, ok for the correct positioning of the wdat_wdt_start function
at the end of the watchdog device initialization. Thanks!
>
> > wdat_wdt_set_running(wdat);
> >
> > ret = wdat_wdt_enable_reboot(wdat);
> > --
> > 2.25.1
Regards,
Flavio
Powered by blists - more mailing lists