From: Melin Tomas <tomas.melin@vaisala.com>
To: "wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux@roeck-us.net" <linux@roeck-us.net>
Cc: "linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
Melin Tomas <tomas.melin@vaisala.com>
Subject: [PATCH v2 0/4] watchdog: cadence_wdt: Support all available prescaler values
Date: Fri, 5 Jul 2019 11:46:01 +0000 [thread overview]
Message-ID: <20190705114522.42565-1-tomas.melin@vaisala.com> (raw)
Cadence watchdog HW supports prescaler values of 8, 64, 512 and 4096,
currently only 512 and 4096 are used by driver.
This series adds support to select prescaler values of 8 and 64 for
lower input clock frequencies.
Changes v2:
- Add calculation of actual min/max timeout values
- Validate input clock frequencies to not allow
frequencies that would result in timeout granularity
of > 1 second.
Tomas Melin (4):
watchdog: cadence_wdt: Move clock detection eariler in probe
watchdog: cadence_wdt: Calculate actual timeout limits
watchdog: cadence_wdt: Group struct member init statements
watchdog: cadence_wdt: Support all available prescaler values
drivers/watchdog/cadence_wdt.c | 65 ++++++++++++++++++++--------------
1 file changed, 38 insertions(+), 27 deletions(-)
--
2.17.2
next reply other threads:[~2019-07-05 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 11:46 Melin Tomas [this message]
2019-07-05 11:46 ` [PATCH v2 1/4] watchdog: cadence_wdt: Move clock detection eariler in probe Melin Tomas
2019-07-08 18:03 ` Guenter Roeck
2019-07-05 11:46 ` [PATCH v2 2/4] watchdog: cadence_wdt: Calculate actual timeout limits Melin Tomas
2019-07-08 18:06 ` Guenter Roeck
2019-07-05 11:46 ` [PATCH v2 3/4] watchdog: cadence_wdt: Group struct member init statements Melin Tomas
2019-07-08 18:09 ` Guenter Roeck
2019-07-05 11:46 ` [PATCH v2 4/4] watchdog: cadence_wdt: Support all available prescaler values Melin Tomas
2019-07-08 18:14 ` 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=20190705114522.42565-1-tomas.melin@vaisala.com \
--to=tomas.melin@vaisala.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 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.