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 OK
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 i
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
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 second
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.
Speci