[PATCH v2] startup: inhibit watchdogs on non-interactive autoboot abort

Sascha Hauer s.hauer at pengutronix.de
Tue Jun 23 05:39:15 EDT 2020


On Tue, Jun 23, 2020 at 10:34:26AM +0200, Ahmad Fatoum wrote:
> Hello Sascha,
> 
> On 6/23/20 10:23 AM, Sascha Hauer wrote:
> > On Mon, Jun 22, 2020 at 05:15:25PM +0200, Ahmad Fatoum wrote:
> >> nv.autoboot=abort has been added as development aid to have barebox stop
> >> at the shell prompt automatically. It makes sense to inhibit all watchdogs
> >> in this mode, so the user can later use the shell in peace.
> > 
> > As a person who is frequently annoyed by watchdogs I really like this
> > change.
> 
> :]
> 
> > We could add a new option to the wd command to call
> > watchdog_inhibit_all() for the case when the autoboot timeout has been
> > interrupted by the user.
> > 
> > Anyway, this could be done as a separate patch.
> 
> I thought about having $global.autoboot_watchdog_inhibit_abort={nv,all},
> but didn't go through with it because I couldn't find a name I like.
> 
> Is this what you are suggesting, but with wd setting an internal parameter
> instead?

I thought about a "wd -i" command that disables watchdogs or
automatically pings them. I would use this in case I want to do
something with barebox, but don't want to change nv.autoboot to "abort"

Sascha


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



More information about the barebox mailing list