From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] startup: inhibit watchdogs on non-interactive autoboot abort
Date: Tue, 23 Jun 2020 11:39:15 +0200 [thread overview]
Message-ID: <20200623093915.GX11869@pengutronix.de> (raw)
In-Reply-To: <510a3c4d-7c1d-751e-0cb4-be40507f98d4@pengutronix.de>
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-06-23 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 15:15 Ahmad Fatoum
2020-06-23 8:23 ` Sascha Hauer
2020-06-23 8:34 ` Ahmad Fatoum
2020-06-23 9:39 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200623093915.GX11869@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox