summaryrefslogtreecommitdiffstats
path: root/Documentation/futex-requeue-pi.txt
diff options
context:
space:
mode:
authorRasmus Villemoes2019-06-05 16:06:43 +0200
committerWim Van Sebroeck2019-07-08 20:04:13 +0200
commit487e4e08221debb1ccf9cb2c249fac379b74cbb2 (patch)
treef3d6d4c22f5debc716a315572b127bcf4835b6f9 /Documentation/futex-requeue-pi.txt
parentwatchdog: introduce watchdog.open_timeout commandline parameter (diff)
downloadkernel-qcow2-linux-487e4e08221debb1ccf9cb2c249fac379b74cbb2.tar.gz
kernel-qcow2-linux-487e4e08221debb1ccf9cb2c249fac379b74cbb2.tar.xz
kernel-qcow2-linux-487e4e08221debb1ccf9cb2c249fac379b74cbb2.zip
watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT
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@prevas.dk> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
Diffstat (limited to 'Documentation/futex-requeue-pi.txt')
0 files changed, 0 insertions, 0 deletions