From: Brad Parker <brad@heeltoe.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UNS: [Nios2-dev] [PATCH] nios2: fix out of reach case for do_reset
Date: Fri, 13 Aug 2010 19:51:43 -0400 [thread overview]
Message-ID: <4C65DA8F.5000301@heeltoe.com> (raw)
In-Reply-To: <1281667205-23282-1-git-send-email-thomas@wytron.com.tw> (sfid-20100812_224039_277713_FED0353C)
As a comment, that patch looks pretty ugly. I might suggest an inline
function (called "callr" or "nios2_callr") which
encapsulates the __asm__. That would make the code much easier to read.
You could put the inline function in one of the asm headers.
-brad
Thomas Chou wrote:
> The "Nios II Processor Reference Handbook" said,
> "call can transfer execution anywhere within the 256 MByte range
> determined by PC31..28. The Nios II GNU linker does not automatically
> handle cases in which the address is out of this range."
>
> So we have to use registered "callr" instruction to do the job.
>
> Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
> ---
> arch/nios2/cpu/cpu.c | 14 ++++++++------
> 1 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/arch/nios2/cpu/cpu.c b/arch/nios2/cpu/cpu.c
> index 6379534..d9c3003 100644
> --- a/arch/nios2/cpu/cpu.c
> +++ b/arch/nios2/cpu/cpu.c
> @@ -40,11 +40,13 @@ int checkcpu (void)
> return (0);
> }
>
> -
> -int do_reset (void)
> +int do_reset(void)
> {
> - void (*rst)(void) = (void(*)(void))CONFIG_SYS_RESET_ADDR;
> - disable_interrupts ();
> - rst();
> - return(0);
> + disable_interrupts();
> + __asm__ __volatile__ (
> + "callr %0"
> + :
> + : "r" (CONFIG_SYS_RESET_ADDR)
> + );
> + return 0;
> }
>
next prev parent reply other threads:[~2010-08-13 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 2:40 [U-Boot] [PATCH] nios2: fix out of reach case for do_reset Thomas Chou
2010-08-13 2:52 ` Mike Frysinger
2010-08-13 3:26 ` Thomas Chou
2010-08-13 23:51 ` Brad Parker [this message]
2010-08-16 2:48 ` [U-Boot] UNS: [Nios2-dev] " Thomas Chou
2010-08-16 2:49 ` [U-Boot] [PATCH v2] " Thomas Chou
2010-08-20 2:25 ` Scott McNutt
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=4C65DA8F.5000301@heeltoe.com \
--to=brad@heeltoe.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