Hi Stefan and Quentin, Thank you for the comments.
> Juuso, I would like to take v3 as it stands. It fixes a real bug, > drivers that don't set max_timeout_ms are unaffected, and the > effective-value work sits on top of it rather than replacing it. Sounds good. To clarify on the next steps: the follow-up will be a separate series on top of v3. It adds a get_timeout() operation that is called after ops->start(), and uses that value in the print when the driver implements it. Otherwise, keep the v3 behaviour. With the real timeout available, wdt-uclass can also warn when the effective timeout is shorter than the service interval. > No need to resend just for that. I can add them while applying if you > confirm that is what you meant. Yes, that's what was intended. Thank you, I must have missed the 'b4 trailers -u' step. Best, Juuso
