linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 0/5] r8a7790: lager: add support for RCLK watchdog
Date: Tue, 03 Feb 2015 19:04:42 +0000	[thread overview]
Message-ID: <20150203190442.GA32699@katana> (raw)
In-Reply-To: <1422802074-1921-1-git-send-email-wsa@the-dreams.de>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On Mon, Feb 02, 2015 at 12:50:24PM +0100, Geert Uytterhoeven wrote:
> Hi Wolfram,
> 
> On Mon, Feb 2, 2015 at 12:24 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> >> I've just tried your series on Koelsch, and it suffers from the same problem.
> >> Does it work on Lager for both CONFIG_SMP=y and CONFIG_SMP=n?
> >
> > I didn't. And what a surprise, it fails with SMP=y :( I'll having a
> > look...
> 
> Good luck!

Weelllll....

I think there are multiple issues and they mostly come from the fact
that a watchdog reset does not initialize the RST module. Rebooting even
fails when I only use CPU0 with SMP=y. I could fix this very hackish by
resetting the A15 boot address (CA15BAR) to the default value in the
watchdog probe function. That alone sadly doesn't help. Once I activate
the other CPUs, it will still lock up.

Pity, but before I get too side-tracked from what I originally wanted to
do, it seems that I simply have to run my tests with SMP=n. I guess this
also renders the watchdog driver pretty useless for upstream now :(


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-02-03 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 14:47 [RFC 0/5] r8a7790: lager: add support for RCLK watchdog Wolfram Sang
2015-02-02  9:32 ` Geert Uytterhoeven
2015-02-02 11:24 ` Wolfram Sang
2015-02-02 11:50 ` Geert Uytterhoeven
2015-02-03 19:04 ` Wolfram Sang [this message]
2015-02-03 19:49 ` Geert Uytterhoeven
2015-02-03 20:11 ` Wolfram Sang

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=20150203190442.GA32699@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;
as well as URLs for NNTP newsgroup(s).