From: Guenter Roeck <linux@roeck-us.net>
To: Florian Fainelli <f.fainelli@gmail.com>, madhuparnabhowmik10@gmail.com
Cc: wim@linux-watchdog.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org, andrianov@ispras.ru,
ldv-project@linuxtesting.org
Subject: Re: [PATCH] drivers: watchdog: rdc321x_wdt: Fix race condition bugs
Date: Fri, 7 Aug 2020 21:58:52 -0700 [thread overview]
Message-ID: <1b9fa0f7-4ea8-f4bb-3abb-375532142e91@roeck-us.net> (raw)
In-Reply-To: <5c048af7-e7b0-4928-9088-b0bbbcfab0ed@gmail.com>
[ ... ]
> The R8610-G datasheet is the one that I have had and used thus far.
>
Mine is draft version 0.2. Do you have a newer version, by any chance ?
>> Unfortunately, none of those
>> describes the use of bit(31) in the watchdog register, nor the meaning
>> of bit(12) and bit(13). Bit(31) is described in the code as "Mask",
>> and it is set by a couple of commands. I _suspect_ that bit(31) has to be
>> set to change some of the register bits, for example the counter value.
>> That is just a wild guess, but it would explain why the driver works
>> in the first place.
>>
>> It is also not clear if the bits in the counter register are accumulative
>> or if only the highest bit counts. The datasheets suggest that only the
>> highest bit counts, but then the value of RDC_CLS_TMR doesn't make much
>> sense since it sets two bits.
>>
>> Since you wrote the driver, I was hoping that you might have a datasheet
>> which explains all this in more detail.
>
> I do not, and this was over 12 years ago, and I honestly do not recall
> all the details, when I get the board running a newish kernel, I will
> poke around.
>
Surprise :-)
Thanks,
Guenter
next prev parent reply other threads:[~2020-08-08 4:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 11:29 madhuparnabhowmik10
2020-08-07 16:21 ` Guenter Roeck
2020-08-07 18:08 ` Florian Fainelli
2020-08-07 18:19 ` Guenter Roeck
2020-08-07 19:08 ` Guenter Roeck
2020-08-07 20:09 ` Florian Fainelli
2020-08-07 23:23 ` Guenter Roeck
2020-08-08 0:41 ` Florian Fainelli
2020-08-08 4:58 ` Guenter Roeck [this message]
2020-08-07 18:30 ` [ldv-project] " Evgeny Novikov
2020-08-07 19:00 ` 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=1b9fa0f7-4ea8-f4bb-3abb-375532142e91@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrianov@ispras.ru \
--cc=f.fainelli@gmail.com \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=madhuparnabhowmik10@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®