On 5/08/20 4:14 am, Guenter Roeck wrote:
> On 8/4/20 8:20 AM, Alexandre Belloni wrote:
>> Hi,
>>
>> The subject prefix is not correct, it should be rtc: ds1307:
>>
>> Also, shouldn't that kind of software timeout which doesn't actually
>> depend on the hardware better be handled in the watchdog
On 8/4/20 8:20 AM, Alexandre Belloni wrote:
> Hi,
>
> The subject prefix is not correct, it should be rtc: ds1307:
>
> Also, shouldn't that kind of software timeout which doesn't actually
> depend on the hardware better be handled in the watchdog core? Then this
> will benefit all the watchdog
Hi,
The subject prefix is not correct, it should be rtc: ds1307:
Also, shouldn't that kind of software timeout which doesn't actually
depend on the hardware better be handled in the watchdog core? Then this
will benefit all the watchdog and will certainly avoid a lot of code
duplication.
On
If the hardware watchdog in the clock chip simply pulls the reset line
of the CPU, then there is no chance to write a stack trace to help
determine what may have been blocking the CPU.
This patch adds a pretimeout to the watchdog, which, if enabled, sets
a timer to go off before the hardware
4 matches
Mail list logo
