Re: [U-Boot] [PATCH] aspeed/watchdog: Correct timeout value

2019-06-20 Thread Tom Rini
On Thu, Jun 06, 2019 at 05:08:45PM +0930, Joel Stanley wrote: > The driver was using milliseconds and programming it into a register > which takes ticks of the watchdog clock, which runs at 1MHz. This meant > we were off by 1000 with the desired value. > > When 06985289d452 ("watchdog: Implement

Re: [U-Boot] [PATCH] aspeed/watchdog: Correct timeout value

2019-06-16 Thread Joel Stanley
On Fri, 7 Jun 2019 at 14:57, Tom Rini wrote: > > On Thu, Jun 06, 2019 at 05:08:45PM +0930, Joel Stanley wrote: > > > The driver was using milliseconds and programming it into a register > > which takes ticks of the watchdog clock, which runs at 1MHz. This meant > > we were off by 1000 with the des

Re: [U-Boot] [PATCH] aspeed/watchdog: Correct timeout value

2019-06-07 Thread Tom Rini
On Thu, Jun 06, 2019 at 05:08:45PM +0930, Joel Stanley wrote: > The driver was using milliseconds and programming it into a register > which takes ticks of the watchdog clock, which runs at 1MHz. This meant > we were off by 1000 with the desired value. > > When 06985289d452 ("watchdog: Implement

[U-Boot] [PATCH] aspeed/watchdog: Correct timeout value

2019-06-06 Thread Joel Stanley
The driver was using milliseconds and programming it into a register which takes ticks of the watchdog clock, which runs at 1MHz. This meant we were off by 1000 with the desired value. When 06985289d452 ("watchdog: Implement generic watchdog_reset() version") was added the aspeed board would leave