From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC v4 0/4] watchdog: add driver for RWDT watchdog
Date: Tue, 01 Mar 2016 13:49:45 +0000 [thread overview]
Message-ID: <20160301134945.GB1514@katana> (raw)
In-Reply-To: <1452287553-18895-1-git-send-email-wsa@the-dreams.de>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
> >> I tested this on Lager with my hacky patches enabling RWDT in UP mode. For this
> >> series, I picked and updated the integration patches for Gen3 from the BSP.
> >> Note that this driver also needs a RESET module driver to work on Gen3. Since
> >> we don't have that yet (couldn't even find it in the BSP), it is untested on
> >> Gen3. Since it works on Gen2 and the datasheet doesn't specify any difference,
> >> my proposal would be that I mark this task as done and leave the integration
> >> with the reset module to the core group. If any problems with this driver show
> >> up, I'll be there, of course. Would that be okay with the core group?
> >
> > Just wondering: can't you test it on Gen3 the same way as on Gen2?
> > Or does the firmware interfere?
>
> Have you tried this on Gen3?
I tried clearing the bit in WDTRSTCR like with Gen2, but without success
:( I heard that Ben Dooks tried as well and did not succeed. I was
hoping that the new BSP might bring some light into this since they
patched my RWDT driver, so I assume they got it to work.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-01 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 21:12 [RFC v4 0/4] watchdog: add driver for RWDT watchdog Wolfram Sang
2016-01-14 17:32 ` Geert Uytterhoeven
2016-03-01 11:31 ` Geert Uytterhoeven
2016-03-01 13:49 ` Wolfram Sang [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=20160301134945.GB1514@katana \
--to=wsa@the-dreams.de \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox