All of lore.kernel.org
 help / color / mirror / Atom feed
From: michaelsh@mellanox.com
To: wim@linux-watchdog.org, linux@roeck-us.net, 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 v4 3/3] Documentation/watchdog: Add documentation mlx-wdt driver
Date: Wed, 20 Feb 2019 09:34:24 +0000	[thread overview]
Message-ID: <20190220093424.5374-4-michaelsh@mellanox.com> (raw)
In-Reply-To: <20190220093424.5374-1-michaelsh@mellanox.com>

From: Michael Shych <michaelsh@mellanox.com>

Add documentation with details of Mellanox watchdog driver.

Signed-off-by: Michael Shych <michaelsh@mellanox.com>
---
v1->v4
1. Remove sentence that now doesn't correspond to code.
2. Add explanations about nowayout and start_at_boot options.
---
 Documentation/watchdog/mlx-wdt.txt | 52 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 52 insertions(+)
 create mode 100644 Documentation/watchdog/mlx-wdt.txt

diff --git a/Documentation/watchdog/mlx-wdt.txt b/Documentation/watchdog/mlx-wdt.txt
new file mode 100644
index 000000000000..434eadece41b
--- /dev/null
+++ b/Documentation/watchdog/mlx-wdt.txt
@@ -0,0 +1,52 @@
+		Mellanox watchdog drivers
+		for x86 based system switches
+
+This driver provides watchdog functionality for various Mellanox
+Ethernet and Infiniband switch systems.
+
+Mellanox watchdog device is implemented in a programmable logic device.
+
+There are 2 types of HW watchdog implementations.
+
+Type 1:
+Actual HW timeout can be defined as a power of 2 msec.
+e.g. timeout 20 sec will be rounded up to 32768 msec.
+The maximum timeout period is 32 sec (32768 msec.),
+Get time-left isn't supported
+
+Type 2:
+Actual HW timeout is defined in sec. and it's the same as
+a user-defined timeout.
+Maximum timeout is 255 sec.
+Get time-left is supported.
+
+Type 1 HW watchdog implementation exist in old systems and
+all new systems have type 2 HW watchdog.
+Two types of HW implementation have also different register map.
+
+Mellanox system can have 2 watchdogs: main and auxiliary.
+Main and auxiliary watchdog devices can be enabled together
+on the same system.
+There are several actions that can be defined in the watchdog:
+system reset, start fans on full speed and increase register counter.
+The last 2 actions are performed without a system reset.
+Actions without reset are provided for auxiliary watchdog device,
+which is optional.
+Watchdog can be started during a probe, in this case it will be
+pinged by watchdog core before watchdog device will be opened by
+user space application.
+Watchdog can be initialised in nowayout way, i.e. oncse started
+it can be stopped.
+
+This mlx-wdt driver supports both HW watchdog implementations.
+
+Watchdog driver is probed from the common mlx_platform driver.
+Mlx_platform driver provides an appropriate set of registers for
+Mellanox watchdog device, identity name (mlx-wdt-main or mlx-wdt-aux),
+initial timeout, performed action in expiration and configuration flags.
+watchdog configuration flags: nowayout and start_at_boot, hw watchdog
+version - type1 or type2.
+The driver checks during initialization if the previous system reset
+was done by the watchdog. If yes, it makes a notification about this event.
+
+Access to HW registers is performed through a generic regmap interface.
-- 
2.11.0


  parent reply	other threads:[~2019-02-20  9:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  9:34 [PATCH v4 0/3] introduce watchdog driver for Mellanox systems michaelsh
2019-02-20  9:34 ` [PATCH v4 1/3] platform_data/mlxreg: additions for Mellanox watchdog driver michaelsh
2019-02-23 17:12   ` Guenter Roeck
2019-02-20  9:34 ` [PATCH v4 2/3] watchdog: mlx-wdt: introduce a watchdog driver for Mellanox systems michaelsh
2019-02-23 17:12   ` Guenter Roeck
2019-02-24 11:36     ` Vadim Pasternak
2019-02-24 16:39       ` Guenter Roeck
2019-02-24 18:01         ` Vadim Pasternak
2019-03-07  6:39           ` Darren Hart
2019-02-20  9:34 ` michaelsh [this message]
2019-02-23 17:13   ` [PATCH v4 3/3] Documentation/watchdog: Add documentation mlx-wdt driver Guenter Roeck
2019-02-24 17:26     ` Michael Shych

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=20190220093424.5374-4-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 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.