From: Johannes Thumshirn <johannes.thumshirn@men.de>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: <linux-watchdog@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] watchdog: Add sysfs interface for MEN A21 watchdog
Date: Wed, 29 May 2013 10:35:27 +0200 [thread overview]
Message-ID: <20130529083527.GA12478@jtlinux> (raw)
In-Reply-To: <20130527194154.GE14258@spo001.leaseweb.com>
On Mon, May 27, 2013 at 09:41:54PM +0200, Wim Van Sebroeck wrote:
> Hi Johannes,
>
> > This patch adds a sysfs interface for the watchdog device found on MEN A21
> > Boards.
> >
> > The newly generated files are:
> > * rebootcause:
> > Can be one of:
> > Power on Reset,
> > CPU Reset Request,
> > Push Button,
> > FPGA Reset Request,
> > Watchdog,
> > Local Power Bad,
> > Invalid or
> > BDI
> > and shows the reason of the boards last reboot.
>
> Question: why don't you use the detection of the reboot cause in your driver
> initialization so that you can:
> 1) report the reboot cause at the start of the driver (like we do in most
> drivers that support these kind of features)
> 2) set the .bootstatus info in the watchdog_device struct data?
> (See the WDIOF flags in #include <uapi/linux/watchdog.h>
> #define WDIOF_OVERHEAT 0x0001 /* Reset due to CPU overheat */
> #define WDIOF_FANFAULT 0x0002 /* Fan failed */
> #define WDIOF_EXTERN1 0x0004 /* External relay 1 */
> #define WDIOF_EXTERN2 0x0008 /* External relay 2 */
> #define WDIOF_POWERUNDER 0x0010 /* Power bad/power fault */
> #define WDIOF_CARDRESET 0x0020 /* Card previously reset the CPU */
> #define WDIOF_POWEROVER 0x0040 /* Power over voltage */
> #define WDIOF_SETTIMEOUT 0x0080 /* Set timeout (in seconds) */
> #define WDIOF_MAGICCLOSE 0x0100 /* Supports magic close char */
> #define WDIOF_PRETIMEOUT 0x0200 /* Pretimeout (in seconds), get/set */
> #define WDIOF_ALARMONLY 0x0400 /* Watchdog triggers a management or
> other external alarm not a reboot */
> #define WDIOF_KEEPALIVEPING 0x8000 /* Keep alive ping reply */
> (Example driver: wdt_pci.c )).
>
> Kind regards,
> Wim.
>
Ok I'll do. Should I repost this as a change of this patch or the "add driver"
patch?
Regards,
Johannes
next prev parent reply other threads:[~2013-05-29 8:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:58 [PATCH] watchdog: New watchdog driver for MEN A21 watchdogs johannes.thumshirn
2013-05-13 22:44 ` Guenter Roeck
2013-05-14 19:09 ` [PATCH v2] " johannes.thumshirn
2013-05-14 19:33 ` Joe Perches
2013-05-15 18:50 ` [PATCH v3] " johannes.thumshirn
2013-05-26 14:34 ` Wim Van Sebroeck
2013-05-27 6:45 ` AW: " Thumshirn, Johannes Tobias
2013-05-27 9:07 ` Wim Van Sebroeck
2013-05-27 18:13 ` [PATCH v4 1/2] " johannes.thumshirn
2013-05-27 18:13 ` [PATCH v4 2/2] watchdog: Add sysfs interface for MEN A21 watchdog johannes.thumshirn
2013-05-27 19:41 ` Wim Van Sebroeck
2013-05-29 8:35 ` Johannes Thumshirn [this message]
2013-05-30 22:00 ` Wim Van Sebroeck
2013-05-27 18:25 ` [PATCH v4 1/2] watchdog: New watchdog driver for MEN A21 watchdogs Wim Van Sebroeck
2013-05-28 8:10 ` Johannes Thumshirn
2013-05-28 16:22 ` Guenter Roeck
2013-05-29 8:14 ` Johannes Thumshirn
2013-05-30 21:59 ` Wim Van Sebroeck
2013-05-30 22:02 ` Guenter Roeck
2013-05-31 8:24 ` Johannes Thumshirn
2013-05-31 9:35 ` anish singh
2013-05-31 10:09 ` Guenter Roeck
2013-05-30 21:52 ` Wim Van Sebroeck
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=20130529083527.GA12478@jtlinux \
--to=johannes.thumshirn@men.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/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).