[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <APgAqgAuDm48oWX*tq6AkKqd.3.1620265890239.Hmail.wangqing@vivo.com>
Date: Thu, 6 May 2021 09:51:30 +0800 (GMT+08:00)
From: 王擎 <wangqing@...o.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Wim Van Sebroeck <wim@...ux-watchdog.org>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re:Re: [PATCH V9 1/2] watchdog: mtk: support pre-timeout when the bark irq is available
>On 4/24/21 6:52 PM, Wang Qing wrote:
>> Use the bark interrupt as the pretimeout notifier if available.
>>
>> When the watchdog timer expires in dual mode, an interrupt will be
>> triggered first, then the timing restarts. The reset signal will be
>> initiated when the timer expires again.
>>
>> The pretimeout notification shall occur at timeout-sec/2.
>>
>> V2:
>> - panic() by default if WATCHDOG_PRETIMEOUT_GOV is not enabled.
>>
>> V3:
>> - Modify the pretimeout behavior, manually reset after the pretimeout
>> - is processed and wait until timeout.
>>
>> V4:
>> - Remove pretimeout related processing.
>> - Add dual mode control separately.
>>
>> V5:
>> - Fix some formatting and printing problems.
>>
>> V6:
>> - Realize pretimeout processing through dualmode.
>>
>> V7:
>> - Add set_pretimeout().
>>
>> V8/V9:
>> - Fix some formatting problems.
>>
>> Signed-off-by: Wang Qing <wangqing@...o.com>
>
>Reviewed-by: Guenter Roeck <linux@...ck-us.net>
>
>Note that the version history should be after "---".
>
>Guenter
>
Thanks, Guenter.
And what do I need to do if I want merge into the next-tree?
Qing
Powered by blists - more mailing lists