From: Guenter Roeck <linux@roeck-us.net>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-watchdog@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [PATCH] watchdog: add documentation for PM usage
Date: Mon, 17 Dec 2018 12:08:39 -0800 [thread overview]
Message-ID: <20181217200839.GB29585@roeck-us.net> (raw)
In-Reply-To: <20181217193314.3487-1-wsa+renesas@sang-engineering.com>
On Mon, Dec 17, 2018 at 08:33:14PM +0100, Wolfram Sang wrote:
> Add the first rule we recently agreed on.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> Documentation/watchdog/watchdog-pm.txt | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 Documentation/watchdog/watchdog-pm.txt
>
> diff --git a/Documentation/watchdog/watchdog-pm.txt b/Documentation/watchdog/watchdog-pm.txt
> new file mode 100644
> index 000000000000..7a4dd46e0d24
> --- /dev/null
> +++ b/Documentation/watchdog/watchdog-pm.txt
> @@ -0,0 +1,19 @@
> +The Linux WatchDog Timer Power Management Guide
> +===============================================
> +Last reviewed: 17-Dec-2018
> +
> +Wolfram Sang <wsa+renesas@sang-engineering.com>
> +
> +Introduction
> +------------
> +This document states rules about watchdog devices and their power management
> +handling to ensure a uniform behaviour for Linux systems.
> +
> +
> +Ping on resume
> +--------------
> +On resume, a watchdog timer shall be reset to its selected value to give
> +userspace enough time to resume. [1] [2]
> +
> +[1] https://patchwork.kernel.org/patch/10252209/
> +[2] https://patchwork.kernel.org/patch/10711625/
> --
> 2.19.1
>
next prev parent reply other threads:[~2018-12-17 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 19:33 [PATCH] watchdog: add documentation for PM usage Wolfram Sang
2018-12-17 20:08 ` Guenter Roeck [this message]
2018-12-18 7:48 ` Geert Uytterhoeven
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=20181217200839.GB29585@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@linux-watchdog.org \
--cc=wsa+renesas@sang-engineering.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).