From: David Updegraff <dave@cray.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] mpc83xx watchdog
Date: Thu, 09 Nov 2006 11:27:18 -0600 [thread overview]
Message-ID: <455364F6.7050205@cray.com> (raw)
In-Reply-To: <45536227.1080506@freescale.com>
Timur
Good to hear you already have one; fine by me.
But.. I dont know how it can work w/o the tweek to start.S, since by my
reading of the PPC 603 asm.ref., the existing instruction there will not
accept full 16bit value. Did you have another workaround for it?
> David Updegraff wrote:
>> Hi.
>>
>> Watchdog could work with this.
>
> A patch that does something similar is already in Freescale's 83xx tree
> that is waiting for Wolfgang to pull.
>
> Here's the relevant bit:
>
> @@ -150,9 +213,21 @@ unsigned long get_tbclk(void)
> #if defined(CONFIG_WATCHDOG)
> void watchdog_reset (void)
> {
> - hang(); /* FIXME: implement watchdog_reset()? */
> +#ifdef CONFIG_MPC834X
> + int re_enable = disable_interrupts();
> +
> + /* Reset the 83xx watchdog */
> + volatile immap_t *immr = (immap_t *) CFG_IMMRBAR;
> + immr->wdt.swsrr = 0x556c;
> + immr->wdt.swsrr = 0xaa39;
> +
> + if (re_enable)
> + enable_interrupts ();
> +#else
> + hang();
> +#endif
> }
> -#endif /* CONFIG_WATCHDOG */
> +#endif
>
>
> We don't have any changes for start.S, though. Also, our tree renames
> CFG_IMMRBAR to CFG_IMMR.
>
> I'm going to NACK your patch, simply because it's incompatible with
> ours. I'm willing to work with you to fix that, though, if you like.
>
prev parent reply other threads:[~2006-11-09 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 16:51 [U-Boot-Users] mpc83xx watchdog David Updegraff
2006-11-09 17:07 ` Wolfgang Denk
2006-11-09 17:15 ` Timur Tabi
2006-11-09 17:27 ` David Updegraff [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=455364F6.7050205@cray.com \
--to=dave@cray.com \
--cc=u-boot@lists.denx.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