mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Roberto Nibali <rnibali@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Add two architectures which can detect the reset source
Date: Thu, 21 Jun 2012 23:50:21 +0200	[thread overview]
Message-ID: <CAONxwYPA1xhS8X0VrzJzSrYratGKdsnV3F=Ks8kB56L+vfvk=A@mail.gmail.com> (raw)
In-Reply-To: <201206212101.42996.jbe@pengutronix.de>

Hi

> Sascha Hauer wrote:
> > On Thu, Jun 21, 2012 at 11:16:18AM +0200, Juergen Beisert wrote:
> > > These are examples how to provide the reset source. Not really tested on
> > > the corresponding hardware yet.
> >
> > I did. On i.MX1 it does not work. The reset source register is not
> > inside the watchdog module, but at 0x0021b800 (Reset source register,
> > RSR)
>
> Hmm, in my old MC9328MX1 manual the watchdog register at 0x201008 (=Watchdog
> Status Register) reports in bit 0 (=TOUT) if the watchdog timed out.
>
> But the RSR seems a more reliable source to read the status.
>
> > On i.MX27 it correctly detects a watchdog reset but not a power on
> > reset. On i.MX27 it must be:
> >
> > #  define WDOG_WRSR_EXT (1 << 3)
> > #  define WDOG_WRSR_PWR (1 << 4)
>
> Ups, sure. "not really tested"...I told you so ;)
> Time for a #ifdef hell?


On i.MX258 it's 0x53FDC000 + 0x0004 (WRSR) and bits 0 and 1, as follows:

Bit: 1 (TOUT)

Time-out. Indicates whether the reset is the result of a WDOG time-out.

    0 Reset is not the result of a WDOG time-out.
    1 Reset is the result of a WDOG time-out.

Bit: 0 (SFTW)

Software Reset. Indicates whether the reset is the result of a WDOG
software reset by asserting SRS bit

     0 Reset is not the result of a software reset.
     1 Reset is the result of a software reset.


Cheers
Roberto

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2012-06-21 21:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  9:16 [PATCHv2] Enable a way to provide the reason for "being here" Juergen Beisert
2012-06-21  9:16 ` [PATCH 1/2] " Juergen Beisert
2012-06-21  9:16 ` [PATCH 2/2] Add two architectures which can detect the reset source Juergen Beisert
2012-06-21 18:27   ` Sascha Hauer
2012-06-21 19:01     ` Juergen Beisert
2012-06-21 19:03       ` Sascha Hauer
2012-06-21 21:50       ` Roberto Nibali [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-20 14:32 [PATCH] Enable a way to provide the reason for "being here" Juergen Beisert
2012-06-20 14:32 ` [PATCH 2/2] Add two architectures which can detect the reset source Juergen Beisert
2012-06-20 14:59   ` Marc Kleine-Budde
2012-06-20 15:05     ` Juergen Beisert
2012-06-20 15:09       ` Marc Kleine-Budde

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='CAONxwYPA1xhS8X0VrzJzSrYratGKdsnV3F=Ks8kB56L+vfvk=A@mail.gmail.com' \
    --to=rnibali@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.de \
    /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