[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170711155033.GB31924@spo001.leaseweb.nl>
Date: Tue, 11 Jul 2017 17:50:33 +0200
From: Wim Van Sebroeck <wim@...ana.be>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Rasmus Villemoes <rasmus.villemoes@...vas.dk>,
Jonathan Corbet <corbet@....net>,
Sebastian Reichel <sebastian.reichel@...labora.co.uk>,
esben.haabendal@...il.com, Alan Cox <gnomes@...rguk.ukuu.org.uk>,
linux-watchdog@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [v6,3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT
Hi Guenter,
> > This allows setting a default value for the watchdog.open_timeout
> > commandline parameter via Kconfig.
> >
> > Some BSPs allow remote updating of the kernel image and root file
> > system, but updating the bootloader requires physical access. Hence, if
> > one has a firmware update that requires relaxing the
> > watchdog.open_timeout a little, the value used must be baked into the
> > kernel image itself and cannot come from the u-boot environment via the
> > kernel command line.
> >
> > Being able to set the initial value in .config doesn't change the fact
> > that the value on the command line, if present, takes precedence, and is
> > of course immensely useful for development purposes while one has
> > console acccess, as well as usable in the cases where one can make a
> > permanent update of the kernel command line.
> >
> > Signed-off-by: Rasmus Villemoes <rasmus.villemoes@...vas.dk>
>
> Wim, any thoughts on making this configurable ? I used to be opposed to it,
> but it does seem to make some sense to me now after thinking about it.
I will look at it later this week.
Kind regards,
Wim.
Powered by blists - more mailing lists