18 Feb
2019
18 Feb
'19
9:18 a.m.
On 17.02.19 22:30, Chris Packham wrote:
The generic wdt_start API expects to be called with the timeout in milliseconds. Update the orion_wdt driver to accept a timeout in milliseconds and use the clock rate specified in the dts to convert the timeout to an appropriate value for the timer reload register.
Signed-off-by: Chris Packham judge.packham@gmail.com
It turned out to be easy enough to make orion_wdt conform to the expected wdt APIs. It looks like the turris_mox already assumed a timeout in ms, so only the turris_omnia needed updating.
Changes in v4:
- use DIV_ROUND_UP to avoid setting the timeout to 0.
Changes in v3:
- new
Changes in v2: None
Reviewed-by: Stefan Roese sr@denx.de
Thanks, Stefan