From: Melin Tomas <tomas.melin@vaisala.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] watchdog: cadence_wdt: Support all available prescaler values
Date: Tue, 9 Jul 2019 20:49:20 +0000 [thread overview]
Message-ID: <4cc8b578-07f1-f0ec-1150-e0db9e47107c@vaisala.com> (raw)
In-Reply-To: <20190709202113.GD27937@roeck-us.net>
On 7/9/19 11:21 PM, Guenter Roeck wrote:
> On Tue, Jul 09, 2019 at 08:09:06PM +0000, Melin Tomas wrote:
>> Cadence watchdog HW supports prescaler values of
>> 8, 64, 512 and 4096.
>>
>> Add support to select prescaler values of 8 and 64 for lower
>> input clock frequencies.
>>
>> Prescaler value is selected to keep timeout resolution of 1 second.
>> For clock frequencies below 32kHz, 1 second resolution does
>> no longer hold, thereby returning an error.
>>
> I think I am missing something. Why was this valid/supported up to now,
> and if it was, why is it no longer possible to support it ?
This driver hasn't really supported smaller input clock frequencies. The
watchdog
can be driven from an internal clock with rather high frequency, which
I think is the default setting. So typically, one might not even use the
smaller prescalers.
>
> I am also a bit confused about the logic. With a slower clock, I would
> expect that the timeouts are getting larger, not smaller. Can you explain ?
Yes, that is correct. So with a 32kHz clock using smallest available
prescaler,
we get 1 second resolution (and 1 second as smallest timeout).
With an even slower clock than that, we would end up with granularity
and smallest value larger than 1 second.
Thanks,
Tomas
>
>> Signed-off-by: Tomas Melin <tomas.melin@vaisala.com>
>> ---
>> drivers/watchdog/cadence_wdt.c | 21 +++++++++++++++------
>> 1 file changed, 15 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/watchdog/cadence_wdt.c b/drivers/watchdog/cadence_wdt.c
>> index 0bdb275d904a..037faf557f9d 100644
>> --- a/drivers/watchdog/cadence_wdt.c
>> +++ b/drivers/watchdog/cadence_wdt.c
>> @@ -33,16 +33,17 @@
>> #define CDNS_WDT_COUNTER_VALUE_DIVISOR 0x1000
>>
>> /* Clock prescaler value and selection */
>> +#define CDNS_WDT_PRESCALE_8 8
>> #define CDNS_WDT_PRESCALE_64 64
>> #define CDNS_WDT_PRESCALE_512 512
>> #define CDNS_WDT_PRESCALE_4096 4096
>> +#define CDNS_WDT_PRESCALE_SELECT_8 0
>> #define CDNS_WDT_PRESCALE_SELECT_64 1
>> #define CDNS_WDT_PRESCALE_SELECT_512 2
>> #define CDNS_WDT_PRESCALE_SELECT_4096 3
>>
>> -/* Input clock frequency */
>> -#define CDNS_WDT_CLK_10MHZ 10000000
>> -#define CDNS_WDT_CLK_75MHZ 75000000
>> +/* Base input clock frequency */
>> +#define CDNS_WDT_CLK_32KHZ 32768
> ^ Please use a tab here
>
>>
>> /* Counter maximum value */
>> #define CDNS_WDT_COUNTER_MAX 0xFFF
>> @@ -318,10 +319,18 @@ static int cdns_wdt_probe(struct platform_device *pdev)
>> return ret;
>>
>> clock_f = clk_get_rate(wdt->clk);
>> - if (clock_f == 0) {
>> - dev_err(dev, "invalid clock frequency, (f=%lu)\n", clock_f);
>> + if (clock_f < CDNS_WDT_CLK_32KHZ) {
>> + dev_err(dev,
>> + "cannot find suitable clock prescaler, (f=%lu)\n",
>> + clock_f);
>> return -EINVAL;
>> - } else if (clock_f <= CDNS_WDT_CLK_75MHZ) {
>> + } else if (clock_f <= CDNS_WDT_CLK_32KHZ * CDNS_WDT_PRESCALE_8) {
>> + wdt->prescaler = CDNS_WDT_PRESCALE_8;
>> + wdt->ctrl_clksel = CDNS_WDT_PRESCALE_SELECT_8;
>> + } else if (clock_f <= CDNS_WDT_CLK_32KHZ * CDNS_WDT_PRESCALE_64) {
>> + wdt->prescaler = CDNS_WDT_PRESCALE_64;
>> + wdt->ctrl_clksel = CDNS_WDT_PRESCALE_SELECT_64;
>> + } else if (clock_f <= CDNS_WDT_CLK_32KHZ * CDNS_WDT_PRESCALE_512) {
>> wdt->prescaler = CDNS_WDT_PRESCALE_512;
>> wdt->ctrl_clksel = CDNS_WDT_PRESCALE_SELECT_512;
>> } else {
>> --
>> 2.17.2
>>
next prev parent reply other threads:[~2019-07-09 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 20:09 [PATCH v3 0/4] watchdog: cadence_wdt: Support all available prescaler values Melin Tomas
2019-07-09 20:09 ` [PATCH v3 1/4] watchdog: cadence_wdt: Move clock detection earlier in probe Melin Tomas
2019-07-09 20:15 ` Guenter Roeck
2019-07-09 20:09 ` [PATCH v3 2/4] watchdog: cadence_wdt: Calculate actual timeout limits Melin Tomas
2019-07-09 20:14 ` Guenter Roeck
2019-07-09 20:09 ` [PATCH v3 4/4] watchdog: cadence_wdt: Support all available prescaler values Melin Tomas
2019-07-09 20:21 ` Guenter Roeck
2019-07-09 20:49 ` Melin Tomas [this message]
2019-07-09 21:07 ` Guenter Roeck
2019-07-10 19:20 ` Melin Tomas
2019-07-10 20:39 ` Guenter Roeck
2019-07-11 20:10 ` Melin Tomas
2019-07-09 20:09 ` [PATCH v3 3/4] watchdog: cadence_wdt: Group struct member init statements Melin Tomas
2019-07-09 20:16 ` 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=4cc8b578-07f1-f0ec-1150-e0db9e47107c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).