All of lore.kernel.org
 help / color / mirror / Atom feed
From: 王擎 <wangqing@vivo.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re:Re: [PATCH V9 1/2] watchdog: mtk: support pre-timeout when the bark irq is available
Date: Mon, 17 May 2021 16:37:21 +0800 (GMT+08:00)	[thread overview]
Message-ID: <AGAAqwBWDoTN1eybqS54h4qu.3.1621240641040.Hmail.wangqing@vivo.com> (raw)
In-Reply-To: <ac2a3762-0b5d-a406-33e0-fca3073cd5ac@roeck-us.net>


>On 5/5/21 6:51 PM, 王擎 wrote:
>> 
>>> 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@vivo.com>
>>>
>>> Reviewed-by: Guenter Roeck <linux@roeck-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?
>> 
>Wim should take care of that.
>
>Guenter
>
Wim, can you help to pick it up to the next-tree?

Thanks,
Qing



WARNING: multiple messages have this Message-ID (diff)
From: 王擎 <wangqing@vivo.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	 linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re:Re: [PATCH V9 1/2] watchdog: mtk: support pre-timeout when the bark irq is available
Date: Mon, 17 May 2021 16:37:21 +0800 (GMT+08:00)	[thread overview]
Message-ID: <AGAAqwBWDoTN1eybqS54h4qu.3.1621240641040.Hmail.wangqing@vivo.com> (raw)
In-Reply-To: <ac2a3762-0b5d-a406-33e0-fca3073cd5ac@roeck-us.net>


>On 5/5/21 6:51 PM, 王擎 wrote:
>> 
>>> 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@vivo.com>
>>>
>>> Reviewed-by: Guenter Roeck <linux@roeck-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?
>> 
>Wim should take care of that.
>
>Guenter
>
Wim, can you help to pick it up to the next-tree?

Thanks,
Qing


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: 王擎 <wangqing@vivo.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	 linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re:Re: [PATCH V9 1/2] watchdog: mtk: support pre-timeout when the bark irq is available
Date: Mon, 17 May 2021 16:37:21 +0800 (GMT+08:00)	[thread overview]
Message-ID: <AGAAqwBWDoTN1eybqS54h4qu.3.1621240641040.Hmail.wangqing@vivo.com> (raw)
In-Reply-To: <ac2a3762-0b5d-a406-33e0-fca3073cd5ac@roeck-us.net>


>On 5/5/21 6:51 PM, 王擎 wrote:
>> 
>>> 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@vivo.com>
>>>
>>> Reviewed-by: Guenter Roeck <linux@roeck-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?
>> 
>Wim should take care of that.
>
>Guenter
>
Wim, can you help to pick it up to the next-tree?

Thanks,
Qing


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-17  8:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  1:52 [PATCH V9 0/2] watchdog: mtk: support pre-timeout when the bark irq is available Wang Qing
2021-04-25  1:52 ` Wang Qing
2021-04-25  1:52 ` Wang Qing
2021-04-25  1:52 ` [PATCH V9 1/2] " Wang Qing
2021-04-25  1:52   ` Wang Qing
2021-04-25  1:52   ` Wang Qing
2021-04-29 22:22   ` Guenter Roeck
2021-04-29 22:22     ` Guenter Roeck
2021-04-29 22:22     ` Guenter Roeck
2021-05-06  1:51     ` 王擎
2021-05-06  1:51       ` 王擎
2021-05-06  1:51       ` 王擎
2021-05-06  2:10       ` Guenter Roeck
2021-05-06  2:10         ` Guenter Roeck
2021-05-06  2:10         ` Guenter Roeck
2021-05-17  8:37         ` 王擎 [this message]
2021-05-17  8:37           ` 王擎
2021-05-17  8:37           ` 王擎
2021-04-25  1:52 ` [PATCH V9 2/2] doc: mtk-wdt: " Wang Qing
2021-04-25  1:52   ` Wang Qing
2021-04-25  1:52   ` Wang Qing
2021-04-29 21:46   ` Rob Herring
2021-04-29 21:46     ` Rob Herring
2021-04-29 21:46     ` Rob Herring
2021-04-28  1:51 ` Re:[PATCH V9 0/2] watchdog: mtk: " 王擎
2021-04-28  1:51   ` 王擎
2021-04-28  1:51   ` 王擎

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AGAAqwBWDoTN1eybqS54h4qu.3.1621240641040.Hmail.wangqing@vivo.com \
    --to=wangqing@vivo.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=wim@linux-watchdog.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.