Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Doug Anderson
Guenter, On Tue, Nov 26, 2013 at 4:10 PM, Guenter Roeck wrote: > On 11/26/2013 01:34 PM, Doug Anderson wrote: >> >> Guenter, >> >> On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck >> wrote: >>> >>> On 11/26/2013 10:30 AM, Doug Anderson wrote: The existing watchdog timeout worked

Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Guenter Roeck
On 11/26/2013 01:34 PM, Doug Anderson wrote: Guenter, On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck wrote: On 11/26/2013 10:30 AM, Doug Anderson wrote: The existing watchdog timeout worked OK but didn't deal with rounding in an ideal way when dividing out all of its clocks. Specifically

Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Doug Anderson
Guenter, On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck wrote: > On 11/26/2013 10:30 AM, Doug Anderson wrote: >> >> The existing watchdog timeout worked OK but didn't deal with >> rounding in an ideal way when dividing out all of its clocks. >> >> Specifically if you had a timeout of 32 seconds

Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Guenter Roeck
On 11/26/2013 10:30 AM, Doug Anderson wrote: The existing watchdog timeout worked OK but didn't deal with rounding in an ideal way when dividing out all of its clocks. Specifically if you had a timeout of 32 seconds and an input clock of , you'd end up setting a timeout of 31.9998

[PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Doug Anderson
The existing watchdog timeout worked OK but didn't deal with rounding in an ideal way when dividing out all of its clocks. Specifically if you had a timeout of 32 seconds and an input clock of , you'd end up setting a timeout of 31.9998 seconds and reporting a timeout of 31 seconds.

[PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Doug Anderson
The existing watchdog timeout worked OK but didn't deal with rounding in an ideal way when dividing out all of its clocks. Specifically if you had a timeout of 32 seconds and an input clock of , you'd end up setting a timeout of 31.9998 seconds and reporting a timeout of 31 seconds.

Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Guenter Roeck
On 11/26/2013 10:30 AM, Doug Anderson wrote: The existing watchdog timeout worked OK but didn't deal with rounding in an ideal way when dividing out all of its clocks. Specifically if you had a timeout of 32 seconds and an input clock of , you'd end up setting a timeout of 31.9998

Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Doug Anderson
Guenter, On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck li...@roeck-us.net wrote: On 11/26/2013 10:30 AM, Doug Anderson wrote: The existing watchdog timeout worked OK but didn't deal with rounding in an ideal way when dividing out all of its clocks. Specifically if you had a timeout of 32

Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Guenter Roeck
On 11/26/2013 01:34 PM, Doug Anderson wrote: Guenter, On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck li...@roeck-us.net wrote: On 11/26/2013 10:30 AM, Doug Anderson wrote: The existing watchdog timeout worked OK but didn't deal with rounding in an ideal way when dividing out all of its

Re: [PATCH] watchdog: s3c2410_wdt: Handle rounding a little better for timeout

2013-11-26 Thread Doug Anderson
Guenter, On Tue, Nov 26, 2013 at 4:10 PM, Guenter Roeck li...@roeck-us.net wrote: On 11/26/2013 01:34 PM, Doug Anderson wrote: Guenter, On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck li...@roeck-us.net wrote: On 11/26/2013 10:30 AM, Doug Anderson wrote: The existing watchdog timeout