From: michaelsh@mellanox.com
To: linux@roeck-us.net, wim@linux-watchdog.org, andy@infradead.org,
dvhart@infradead.org
Cc: linux-watchdog@vger.kernel.org,
platform-driver-x86@vger.kernel.org, vadimp@mellanox.com,
Michael Shych <michaelsh@mellanox.com>
Subject: [PATCH v2 0/4] support watchdog with longer timeout period
Date: Tue, 28 Apr 2020 16:08:12 +0300 [thread overview]
Message-ID: <20200428130816.582-1-michaelsh@mellanox.com> (raw)
From: Michael Shych <michaelsh@mellanox.com>
This patchset adds support of extended new watchdog type 3 of Mellanox
Ethernet and Infiniband switch systems.
This type of watchdog can have a timeout period longer than 255 or 32 sec.
as it was before.
Michael Shych (4):
platform_data/mlxreg: support new watchdog type with longer timeout
period
platform/x86: mlx-platform: support new watchdog type with longer
timeout
watchdog: mlx-wdt: support new watchdog type with longer timeout
period
docs: watchdog: mlx-wdt: Add description of new watchdog type 3
Documentation/watchdog/mlx-wdt.rst | 12 ++++
drivers/platform/x86/mlx-platform.c | 106 ++++++++++++++++++++++++++++++
drivers/watchdog/mlx_wdt.c | 75 +++++++++++++++++++++----
include/linux/platform_data/mlxreg.h | 5 +-
4 files changed, 186 insertions(+), 12 deletions(-)
--
2.11.0
next reply other threads:[~2020-04-28 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 13:08 michaelsh [this message]
2020-04-28 13:08 ` [PATCH v2 1/4] platform_data/mlxreg: support new watchdog type with longer timeout period michaelsh
2020-04-28 13:08 ` [PATCH v2 2/4] platform/x86: mlx-platform: support new watchdog type with longer timeout michaelsh
2020-04-28 13:08 ` [PATCH v2 3/4] watchdog: mlx-wdt: support new watchdog type with longer timeout period michaelsh
2020-04-29 12:29 ` Guenter Roeck
2020-05-03 5:32 ` Michael Shych
2020-04-28 13:08 ` [PATCH v2 4/4] docs: watchdog: mlx-wdt: Add description of new watchdog type 3 michaelsh
2020-04-28 15:36 ` [PATCH v2 0/4] support watchdog with longer timeout period Andy Shevchenko
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=20200428130816.582-1-michaelsh@mellanox.com \
--to=michaelsh@mellanox.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@mellanox.com \
--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 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).