mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Matti Vaittinen <matti.vaittinen@linux.dev>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Lee Jones <lee@kernel.org>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: bd96801_wdt: Fix timeout for enabled WDG
Date: Fri, 31 Jul 2026 07:19:01 -0700	[thread overview]
Message-ID: <171ccbd1-0a65-4ba5-ad63-16cff58d3977@roeck-us.net> (raw)
In-Reply-To: <amxskHmQbi9v-8_l@mva-rohm>

On Fri, Jul 31, 2026 at 12:36:28PM +0300, Matti Vaittinen wrote:
> From: Matti Vaittinen <mazziesaccount@gmail.com>
> 
> When watchdog is enabled at the probe time, the bd96801 driver retrieves
> the timeout configuration from the registers to set-up the heart-beat
> values.
> 
> As Sashiko pointed out at
> https://lore.kernel.org/all/20260722085819.495211F000E9@smtp.kernel.org/
> the timeout values are incorrectly computed in driver, resulting wrong
> heartbeat. This leads to devere problems if watchdog was enabled at probe
> time.
> 
> According to the data-sheet, the "too fast" ping limit is configured as
> multiple of FASTNG_MIN. Furthermore, the "too slow" ping limit is
> configured as multiples of "too fast" timeout. The FASTNG_MIN is set to
> 11, meaning 1.1 mS and "too fast" and "too slow" limits are computed from
> this. Hence, converting the limits to mS should be done by dividing by 10,
> not by dividing by USEC_PER_MSEC.
> 
> Fix this by dividing the timeout values with correct scaling factor.
> 
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> Fixes: 09dad69757b6 ("watchdog: ROHM BD96801 PMIC WDG driver")
> ---
> 
> Also, drop an extra whitespace while editing the file - feeling like
> that single whitespace fix doesn't warrant own patch. Just let me know if
> I feel wrong ;)

No problem (since you let me know and didn't do it silently).

Applied.

Thanks,
Guenter

      reply	other threads:[~2026-07-31 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  9:36 Matti Vaittinen
2026-07-31 14:19 ` Guenter Roeck [this message]

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=171ccbd1-0a65-4ba5-ad63-16cff58d3977@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=matti.vaittinen@linux.dev \
    --cc=mazziesaccount@gmail.com \
    --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

all inboxes | Powered by JetHome®