From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <ahmad@a3f.at>
Subject: [PATCH] arm64: Don't truncate upper 32 bits in ENTRY_FUNCTION arg registers
Date: Thu, 16 Sep 2021 11:33:56 +0200 [thread overview]
Message-ID: <20210916093356.173149-1-u.kleine-koenig@pengutronix.de> (raw)
From: Ahmad Fatoum <ahmad@a3f.at>
Use a long instead of an u32. For 32-bit arm there is no difference, for
arm64 this results in being able to use the whole register size of 64
bits.
Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
arch/arm/include/asm/barebox-arm.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/include/asm/barebox-arm.h b/arch/arm/include/asm/barebox-arm.h
index 24f9bce2ef7a..cfb5943f33d6 100644
--- a/arch/arm/include/asm/barebox-arm.h
+++ b/arch/arm/include/asm/barebox-arm.h
@@ -162,18 +162,18 @@ static inline unsigned long arm_mem_barebox_image(unsigned long membase,
}
#define ENTRY_FUNCTION(name, arg0, arg1, arg2) \
- void name (uint32_t r0, uint32_t r1, uint32_t r2); \
+ void name(ulong r0, ulong r1, ulong r2); \
\
- static void __##name(uint32_t, uint32_t, uint32_t); \
+ static void __##name(ulong, ulong, ulong); \
\
void NAKED __section(.text_head_entry_##name) name \
- (uint32_t r0, uint32_t r1, uint32_t r2) \
+ (ulong r0, ulong r1, ulong r2) \
{ \
__barebox_arm_head(); \
__##name(r0, r1, r2); \
} \
static void NAKED noinline __##name \
- (uint32_t arg0, uint32_t arg1, uint32_t arg2)
+ (ulong arg0, ulong arg1, ulong arg2)
/*
* When using compressed images in conjunction with relocatable images
base-commit: c945d24ec5dad6910b02697e4d1df09f89d2b950
--
2.30.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2021-09-16 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 9:33 Uwe Kleine-König [this message]
2021-10-02 9:18 ` Sascha Hauer
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=20210916093356.173149-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
/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