From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] add restart function for mpc52xx
Date: Thu, 11 Jan 2007 09:20:40 -0700 [thread overview]
Message-ID: <528646bc0701110820r77aa7bb6oe44904da3f6841e8@mail.gmail.com> (raw)
In-Reply-To: <528646bc0701110750m15cd0f01xe014f75a2c9db625@mail.gmail.com>
On 1/11/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> On 1/11/07, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > BTW the watchdog timer is only implemented for gpt0. Is it guaranteed
> > that I get gpt0 with mpc52xx_find_and_map("mpc52xx-gpt")? As long as
> > all flat trees start with gpt0 I guess yes.
>
> No, you cannot make this assumption. There are no guarantees on order
> that nodes are found.
Sylvain and I just discussed this a bit. Since gpt0 is different (has
the watchdog bits) it should have a compatible property that reflects
it. We're thinking about adding "mpc52xx-wdt" to the compatible list
for gpt0.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-01-11 16:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 12:28 [PATCH] add restart function for mpc52xx Sascha Hauer
2007-01-11 13:15 ` Sylvain Munaut
2007-01-11 13:59 ` Kumar Gala
2007-01-11 15:21 ` Sascha Hauer
2007-01-11 15:50 ` Grant Likely
2007-01-11 16:20 ` Grant Likely [this message]
2007-01-11 16:57 ` Segher Boessenkool
2007-01-12 3:37 ` Paul Mackerras
2007-01-12 8:46 ` Sascha Hauer
2007-01-12 9:00 ` Sylvain Munaut
2007-01-12 10:42 ` Sascha Hauer
2007-01-12 10:43 ` Sylvain Munaut
2007-01-12 16:05 ` Kumar Gala
2007-01-12 12:27 ` Segher Boessenkool
2007-01-28 18:09 ` Robert Schwebel
2007-01-28 21:48 ` Benjamin Herrenschmidt
2007-01-28 23:56 ` David Gibson
2007-01-12 12:23 ` Segher Boessenkool
2007-01-12 12:39 ` Sylvain Munaut
2007-01-12 12:19 ` Segher Boessenkool
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=528646bc0701110820r77aa7bb6oe44904da3f6841e8@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=s.hauer@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;
as well as URLs for NNTP newsgroup(s).