On 8/18/26 10:43, Juuso Rinta wrote: > The wdt_start() function may be called with a timeout greater > than the hardware-supported maximum. This in turn can result > in a bogus print, for example, if the device clamps the timeout > to 10s but wdt_start() is called with a 60s timeout: > Started <watchdog@> with servicing every 1000ms (60s timeout) > > Add a max_timeout_ms field to uclass-plat data, so drivers can > set the hardware-limited max timeout value there during probing. > For drivers that support this feature, the wdt_start() function > clamps the timeout_ms value before calling ops->start() and the > startup print now shows both the actual and requested timeouts, e.g. > Started <watchdog@> with servicing every 1000ms (10s timeout, requested 60s) > > The timeout comparison is done in whole seconds to avoid noise > from sub-second rounding. > > The value defaults to 0. For drivers that do not support > this feature, the resulting print remains the same as before. > > Signed-off-by: Juuso Rinta <[email protected]>
Applied to u-boot-watchdog/next Thanks, Stefan
