From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Guenter Roeck <linux@roeck-us.net>,
Brian Masney <masneyb@onstation.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org,
Guenter Roeck <groeck@chromium.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org,
Doug Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, Sibi Sankar <sibis@codeaurora.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv2] watchdog: qcom: Add suspend/resume support
Date: Thu, 17 Jan 2019 20:56:31 +0530 [thread overview]
Message-ID: <747da233-8b8c-2aa9-59cf-542ab46cc161@codeaurora.org> (raw)
In-Reply-To: <20190117151942.6092-1-saiprakash.ranjan@codeaurora.org>
On 1/17/2019 8:49 PM, Sai Prakash Ranjan wrote:
> This adds the support for qcom watchdog suspend and resume
> when entering and exiting deep sleep states. Otherwise
> having watchdog active after suspend would result in unwanted
> crashes/resets if resume happens after a long time.
>
> Signed-off-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
>
> ---
>
> v2:
> * Use __maybe_unused instead of #ifdef as suggested by
> Brian and Guenter
> ---
> drivers/watchdog/qcom-wdt.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
>
Adding Brian.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2019-01-17 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:19 [PATCHv2] watchdog: qcom: Add suspend/resume support Sai Prakash Ranjan
2019-01-17 15:26 ` Sai Prakash Ranjan [this message]
2019-01-17 18:16 ` Guenter Roeck
2019-01-18 2:58 ` Sai Prakash Ranjan
2019-01-18 3:53 ` Guenter Roeck
2019-01-18 4:25 ` Sai Prakash Ranjan
2019-01-17 18:37 ` Stephen Boyd
2019-01-17 19:09 ` Guenter Roeck
2019-01-17 21:14 ` Jerry Hoemann
2019-01-17 21:16 ` Guenter Roeck
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=747da233-8b8c-2aa9-59cf-542ab46cc161@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=masneyb@onstation.org \
--cc=rnayak@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=sibis@codeaurora.org \
--cc=vivek.gautam@codeaurora.org \
--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