mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: George Cherian <gcherian@marvell.com>
Cc: "wim@linux-watchdog.org" <wim@linux-watchdog.org>,
	"zhangshaokun@hisilicon.com" <zhangshaokun@hisilicon.com>,
	"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] watchdog: sbsa_wdog: Make sure the timeout programming is within the limits
Date: Wed, 8 Feb 2023 09:55:47 -0800	[thread overview]
Message-ID: <20230208175547.GA3065515@roeck-us.net> (raw)
In-Reply-To: <BYAPR18MB267995FB55301778894B3334C5D89@BYAPR18MB2679.namprd18.prod.outlook.com>

On Wed, Feb 08, 2023 at 05:20:34PM +0000, George Cherian wrote:
> 
> 
> > -----Original Message-----
> > From: Guenter Roeck <groeck7@gmail.com> On Behalf Of Guenter Roeck
> > Sent: Wednesday, February 8, 2023 8:41 PM
> > To: George Cherian <gcherian@marvell.com>; wim@linux-watchdog.org;
> > zhangshaokun@hisilicon.com
> > Cc: linux-watchdog@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH v2] watchdog: sbsa_wdog: Make sure the timeout
> > programming is within the limits
> > 
> > 
> > ----------------------------------------------------------------------
> > On 2/8/23 00:37, George Cherian wrote:
> > > Make sure to honour the max_hw_heartbeat_ms while programming the
> > > timeout value to WOR. Clamp the timeout passed to
> > > sbsa_gwdt_set_timeout() to make sure the programmed value is within
> > the permissible range.
> > >
> > > Fixes: abd3ac7902fb ("watchdog: sbsa: Support architecture version 1")
> > >
> > > Signed-off-by: George Cherian <george.cherian@marvell.com>
> > > ---
> > >   drivers/watchdog/sbsa_gwdt.c | 1 +
> > >   1 file changed, 1 insertion(+)
> > >
> > > diff --git a/drivers/watchdog/sbsa_gwdt.c
> > > b/drivers/watchdog/sbsa_gwdt.c index 9791c74aebd4..ee1039a652f1
> > 100644
> > > --- a/drivers/watchdog/sbsa_gwdt.c
> > > +++ b/drivers/watchdog/sbsa_gwdt.c
> > > @@ -149,6 +149,7 @@ static int sbsa_gwdt_set_timeout(struct
> > watchdog_device *wdd,
> > >   {
> > >   	struct sbsa_gwdt *gwdt = watchdog_get_drvdata(wdd);
> > >
> > > +	timeout = clamp_t(unsigned int, timeout, 1, wdd-
> > >max_hw_heartbeat_ms
> > > +/ 1000);
> > >   	wdd->timeout = timeout;
> > >
> > 
> > Wrong order. wdd->timeout should still contain the requested timeout.
> But then the requested timeout is not being set in HW.
> Isn't that a disconnect?

No. The driver is supposed to set a timeout no larger than
max_hw_heartbeat_ms. The watchdog core then takes care of
differences between ->timeout (as seen by the user) and
max_hw_heartbeat_ms and pings the watchdog as needed.

Guenter

  reply	other threads:[~2023-02-08 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  8:37 George Cherian
2023-02-08 15:10 ` Guenter Roeck
2023-02-08 17:20   ` George Cherian
2023-02-08 17:55     ` Guenter Roeck [this message]
2023-02-09  2:09       ` George Cherian

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=20230208175547.GA3065515@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=wim@linux-watchdog.org \
    --cc=zhangshaokun@hisilicon.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

all inboxes | Powered by JetHome®