From: Guenter Roeck <linux@roeck-us.net>
To: Nick & John <levelwol@gmail.com>, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH] watchdog: via_wdt: Partial fix for programming error and support additional southbridges
Date: Mon, 18 May 2015 06:15:18 -0700 [thread overview]
Message-ID: <5559E5E6.2000508@roeck-us.net> (raw)
In-Reply-To: <CANxHX8_A+v0wBt8aQPTB1mae7mnMFmULE-DuoP8kAxL3DdaNeg@mail.gmail.com>
On 05/18/2015 03:50 AM, Nick & John wrote:
> This patch fixes a programming error by limiting WDT_TIMEOUT_MAX to 255.
> That is done to avoid invalid settings. Putting a value bigger than 255
> results in non working watchdog and reset is not performed. We are trying
> to fit a 10bit value to an 8bit area! To support 1023 seconds MMIO addr+5
> bit1:0 must be used to store the last(higher) two bits of count number.
> Strangely no error was logged at the system when using values bigger than
> 255, the driver just ignores the time count.
>
While I have no idea why, the watchdog in this driver is pinged using a soft timer,
and it is always pinged every 0.5 seconds. So reducing the maximum timeout is not
necessary; in fact the driver could support a higher timeout.
The real fix, if it is really necessary, would be to either store the upper bits
as suggested above, or to just program the chip to a timeout of 255 seconds
if the desired timeout is larger than 255.
> Also it adds support for VT8235 and VT8237 series southbridges. Tested with
> VT8235M, VT8237 and VT8237S boards.
>
This should be a separate patch; see Documentation/SubmittingPatches, chapter 3.
Thanks,
Guenter
next prev parent reply other threads:[~2015-05-18 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 10:50 [PATCH] watchdog: via_wdt: Partial fix for programming error and support additional southbridges Nick & John
2015-05-18 13:15 ` Guenter Roeck [this message]
2015-05-18 13:17 ` 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=5559E5E6.2000508@roeck-us.net \
--to=linux@roeck-us.net \
--cc=levelwol@gmail.com \
--cc=linux-watchdog@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.