LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bastos Fernandez Alexandre <alebas@televes.com>
To: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: RE: Watchdog on MPC82xx [SOLVED]
Date: Fri, 21 Apr 2006 12:33:33 +0200	[thread overview]
Message-ID: <1145615613.4448b4fdd6052@webmail.televes.com:443> (raw)
In-Reply-To: <1145528816.444761f0a9962@webmail.televes.com:443>

Hi,

As suggested by Rune, problem was concerning to the RTC on time_init().
As I don't have a RTC on the board, the solution for me was setting
the ppc_md.get_rtc_time to NULL, which prevents time_init() from
doing the loop which tries to set the next second boundary. So

void __init
m82xx_board_setup(void)
{
[...]
    ppc_md.get_rtc_time = NULL;
    ppc_md.set_rtc_time = NULL;
}

Thanks to all.

Alex BASTOS

> Rune,
>
> > On our 8265/8280 board, the max timeout of the watchdog timer was ~1.3
> > seconds, so it kept resetting before the heartbeat function got called
> > on boot.
> >
> > I had to add a watchdog reset to time_init() because it woud pause there
> > for about 2 secondfs trying to see if there was a realtime clock.
> >
>
> I think that you are OK. Using the while(1) test suggested by Paul Bilke,
> I could verify that time_init() is the cause for the reset. In fact, I have
> no RTC on my board (so I suppose the delay looking for it will be maximum).
>
> Thanks
>
> Alex Bastos

      reply	other threads:[~2006-04-21  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 14:29 Watchdog on MPC82xx Rune Torgersen
2006-04-20 10:26 ` Bastos Fernandez Alexandre
2006-04-21 10:33   ` Bastos Fernandez Alexandre [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='1145615613.4448b4fdd6052@webmail.televes.com:443' \
    --to=alebas@televes.com \
    --cc=linuxppc-embedded@ozlabs.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