From: Chunyan Zhang <zhang.lyra@gmail.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Orson Zhai <orsonzhai@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Chunyan Zhang <chunyan.zhang@unisoc.com>,
Lingling Xu <ling_ling.xu@unisoc.com>,
Jingchao Ye <jingchao.ye@unisoc.com>,
Xiaoqing Wu <xiaoqing.wu@unisoc.com>
Subject: [PATCH v3 0/3] A few fixes to sprd watchdog driver
Date: Mon, 9 Nov 2020 11:00:52 +0800 [thread overview]
Message-ID: <20201109030055.27378-1-zhang.lyra@gmail.com> (raw)
From: Chunyan Zhang <chunyan.zhang@unisoc.com>
A few issues about sprd watchdog driver were found recently, this
patchset would fix them.
Changes since v2:
* Added Guenter Roeck's Reviewed-by on patch 2,3;
Changes since v1:
* Added Reviewed-by from Guenter Roeck;
* Abandon original patch 2, add a new patch to use usleep_range() instead of busy loop;
* Revised the max times of loop, also revised the comments for checking busy bit;
* Revised commit message for the whole patchset;
Chunyan Zhang (1):
watchdog: sprd: change to use usleep_range() instead of busy loop
Lingling Xu (2):
watchdog: sprd: remove watchdog disable from resume fail path
watchdog: sprd: check busy bit before new loading rather than after
that
drivers/watchdog/sprd_wdt.c | 43 ++++++++++++++++++-------------------
1 file changed, 21 insertions(+), 22 deletions(-)
--
2.20.1
next reply other threads:[~2020-11-09 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 3:00 Chunyan Zhang [this message]
2020-11-09 3:00 ` [PATCH v3 1/3] watchdog: sprd: remove watchdog disable from resume fail path Chunyan Zhang
2020-11-09 3:00 ` [PATCH v3 2/3] watchdog: sprd: check busy bit before new loading rather than after that Chunyan Zhang
2020-11-09 3:00 ` [PATCH v3 3/3] watchdog: sprd: change to use usleep_range() instead of busy loop Chunyan Zhang
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=20201109030055.27378-1-zhang.lyra@gmail.com \
--to=zhang.lyra@gmail.com \
--cc=chunyan.zhang@unisoc.com \
--cc=jingchao.ye@unisoc.com \
--cc=ling_ling.xu@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=orsonzhai@gmail.com \
--cc=wim@linux-watchdog.org \
--cc=xiaoqing.wu@unisoc.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;
as well as URLs for NNTP newsgroup(s).