From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: add initilisation of watchdog in init_sequence
Date: Thu, 10 Jun 2010 15:47:16 +0200 [thread overview]
Message-ID: <4C10ECE4.3090301@atmel.com> (raw)
In-Reply-To: <4C024936.6090403@bumblecow.com>
Le 30/05/2010 13:17, Tom Rix :
> Nicolas Ferre wrote:
>> For platforms that implement a hardware watchdog, call its initialization
>> routine in init_sequence.
>> This location has been chosen to be the closest to initialization of
>> console as
>> some watchdog drivers are writing status messages. On the other hand,
>> watchdog
>> setup should be close to chip startup to be able to begin the triggering
>> quickly.
>>
> I am not opposed to putting watchdog into the init sequence.
>
> A current ARM way for initializing the watchdog is to do it in
> s_init. Why doesn't this work for you ?
Well, I only see it done like this in some omap platforms. It does work
for me because we do not always use the lowlevel_init.S file: sometimes,
the low level initialization is done by a tiny first level bootloader...
> Reviewing other watchdog additions in the init sequences from
> powerpc,sh,m68k
> If an init is to be added, this setup should be cut-n-pasted from one
> of these. There should be follow-on patches to convert the ARM s_init's
> over to using the init sequence.
I guess that as architecture implementation are different in the way of
initializing watchdog, I may include this in each board file or create a
common initialization for AT91 at board level...
Best regards,
--
Nicolas Ferre
prev parent reply other threads:[~2010-06-10 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 11:07 [U-Boot] [PATCH] arm: add initilisation of watchdog in init_sequence Nicolas Ferre
2010-05-30 11:17 ` Tom Rix
2010-06-10 13:47 ` Nicolas Ferre [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=4C10ECE4.3090301@atmel.com \
--to=nicolas.ferre@atmel.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