Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751458AbdINOwM (ORCPT ); Thu, 14 Sep 2017 10:52:12 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:34510 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751255AbdINOwK (ORCPT ); Thu, 14 Sep 2017 10:52:10 -0400 X-Google-Smtp-Source: ADKCNb4Hgzc04vhwx4VBt+5OIwrTEsOW98FIP6bULGY5OkfGEiO23wMOgpa+9cPNBT/3MsutH0O9ZQ== Date: Thu, 14 Sep 2017 07:52:08 -0700 From: Guenter Roeck To: Oleksij Rempel Cc: Wim Van Sebroeck , Dinh Nguyen , Rob Herring , Mark Rutland , Steffen Trumtrar , linux-watchdog@vger.kernel.org, kernel@pengutronix.de, Russell King , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] watchdog: dw_wdt: add stop watchdog operation Message-ID: <20170914145208.GC7337@roeck-us.net> References: <20170914113013.19157-1-o.rempel@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170914113013.19157-1-o.rempel@pengutronix.de> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2075 Lines: 68 On Thu, Sep 14, 2017 at 01:30:12PM +0200, Oleksij Rempel wrote: > From: Steffen Trumtrar > > The only way of stopping the watchdog is by resetting it. > Add the watchdog op for stopping the device and reset if > a reset line is provided. > > Signed-off-by: Steffen Trumtrar > Signed-off-by: Oleksij Rempel > Cc: Wim Van Sebroeck > Cc: Guenter Roeck > Cc: linux-watchdog@vger.kernel.org > --- > > changes v2: > - test if dw_wdt->rst is NULL instead of IS_ERR > > drivers/watchdog/dw_wdt.c | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/drivers/watchdog/dw_wdt.c b/drivers/watchdog/dw_wdt.c > index 36be987ff9ef..a507f36302e1 100644 > --- a/drivers/watchdog/dw_wdt.c > +++ b/drivers/watchdog/dw_wdt.c > @@ -135,6 +135,21 @@ static int dw_wdt_start(struct watchdog_device *wdd) > return 0; > } > > +static int dw_wdt_stop(struct watchdog_device *wdd) > +{ > + struct dw_wdt *dw_wdt = to_dw_wdt(wdd); > + > + if (!dw_wdt->rst) { > + dev_warn(wdd->parent, "No reset line. Will not stop.\n"); > + return -EOPNOTSUPP; Sorry, not the way to go. It now reports an error to user space when there was none previously, and it still reboots the system. Plus, this was a perfectly fine condition previously, and the reset line is optional. It is not appropriate to generate a warning for a perfectly valid condition. You can not change behavior for existing users. Guenter > + } > + > + reset_control_assert(dw_wdt->rst); > + reset_control_deassert(dw_wdt->rst); > + > + return 0; > +} > + > static int dw_wdt_restart(struct watchdog_device *wdd, > unsigned long action, void *data) > { > @@ -173,6 +188,7 @@ static const struct watchdog_info dw_wdt_ident = { > static const struct watchdog_ops dw_wdt_ops = { > .owner = THIS_MODULE, > .start = dw_wdt_start, > + .stop = dw_wdt_stop, > .ping = dw_wdt_ping, > .set_timeout = dw_wdt_set_timeout, > .get_timeleft = dw_wdt_get_timeleft, > -- > 2.11.0 >