From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] replacing do_reset with a custom one
Date: Sat, 24 Oct 2009 02:19:25 -0400 [thread overview]
Message-ID: <200910240219.26063.vapier@gentoo.org> (raw)
In-Reply-To: <4AE22376.5050107@RuggedCom.com>
On Friday 23 October 2009 17:43:18 Richard Retanubun wrote:
> I am sorry if this has been asked before, It does not appear so on the
> mailing list archive.
>
> I'd like to replace do_reset function with my own custom one, (i.e.
> resetting by not petting an external hw watchdog).
>
> In previous discussion,
> http://lists.denx.de/pipermail/u-boot/2007-January/018848.html
>
> Wolfgang seems to favor creating a custom-board specific command (e.g.
> wdreset) and calling that but If I do that, I have to replace all
> instances of do_reset that matters to my board. It seems simpler to simply
> 'hijack and replace/enhance' the existing 'do_reset' to do my bidding.
>
> Is there a recommended way of doing this? Any chance of adding something
> like this:
>
> /cpu/$some-cpu/cpu.c
>
> do_reset()
> {
>
> #ifdef CUSTOM_BOARD_RESET
> custom_board_reset();
> #endif;
>
> <normal do_reset command>
> }
>
> This way each board can define their own "call_custom_board" function.
#ifdef's are the past. weaks are in!
the Blackfin port already does:
void board_reset(void) __attribute__((__weak__));
...
if (board_reset)
board_reset();
...
the bf537-stamp uses this to make sure some pins are driven low to workaround
weak pull ups in the hardware
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20091024/1e4224cf/attachment.pgp
next prev parent reply other threads:[~2009-10-24 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 21:43 [U-Boot] replacing do_reset with a custom one Richard Retanubun
2009-10-24 6:19 ` Mike Frysinger [this message]
2009-10-26 18:44 ` Richard Retanubun
2009-10-26 20:50 ` Mike Frysinger
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=200910240219.26063.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.