From: Guenter Roeck <linux@roeck-us.net>
To: Freddy Hsin <freddy.hsin@mediatek.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: wsd_upstream@mediatek.com, chang-an.chen@mediatek.com,
kuohong.wang@mediatek.com
Subject: Re: driver: watchdog: Remove mtk_wdt_stop() in probe() to prevent the system freeze and it doesn't reboot by watchdog problem
Date: Fri, 25 Dec 2020 06:27:54 -0800 [thread overview]
Message-ID: <4b88a313-4184-5bf6-a0a7-db608558a9ed@roeck-us.net> (raw)
In-Reply-To: <1608881450-11081-1-git-send-email-freddy.hsin@mediatek.com>
On 12/24/20 11:30 PM, Freddy Hsin wrote:
> Before user space daemon start to access the watchdog device,
> there is a time interval that watchdog is disabled in the
> original flow. If the system freezing at this interval, it
> cannot be rebooted by watchdog hardware automatically.
>
> In order to solve this problem, the watchdog hardware should be
> kept working, and start hrtimer in framework to ping it by
> setting max_hw_heartbeat_ms and HW_RUNNING used in
> watchdog_need_worker to determine whether the worker should be
> started or not
>
This intro email is unnecessary.
Guenter
prev parent reply other threads:[~2020-12-25 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 7:30 Freddy Hsin
2020-12-25 7:30 ` [PATCH v1 1/1] " Freddy Hsin
2020-12-25 14:27 ` Guenter Roeck
[not found] ` <1609231194.9252.6.camel@mtkswgap22>
2020-12-29 15:08 ` Guenter Roeck
2020-12-25 14:29 ` Guenter Roeck
2020-12-25 14:27 ` Guenter Roeck [this message]
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=4b88a313-4184-5bf6-a0a7-db608558a9ed@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chang-an.chen@mediatek.com \
--cc=freddy.hsin@mediatek.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=wim@linux-watchdog.org \
--cc=wsd_upstream@mediatek.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®