From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm64 patch: gicv3 support
Date: Fri, 21 Feb 2014 17:38:05 +0100 [thread overview]
Message-ID: <20140221173805.5b642144@lilith> (raw)
In-Reply-To: <1389773456-37854-1-git-send-email-fenghua@phytium.com.cn>
Hi fenghua at phytium.com.cn,
On Wed, 15 Jan 2014 16:10:56 +0800, fenghua at phytium.com.cn wrote:
> From: David Feng <fenghua@phytium.com.cn>
>
> This patch add gicv3 support to uboot armv8 platform.
> Modifications cover 4 source files, as follows:
> gic.S: gicv3 initialization and sgi interrupt raising.
> goc.h: gicv3 register definitions.
> vexpress_aemv8a.h: add CONFIG_GICV2/CONFIG_GICV3 switch.
> start.S: set SCR_EL3.NS bit to 1, gicv3 register of ICC_SRE_EL2
> could be accessed only when SCR_EL3.NS=1.
> set SCR_EL3.IRQ|FIQ|EA bits, reroute all interrupts to
> el3 at all cores, slaves could be waken up by interrupt
> only when the interrupt is routed to it when running
> at el3.
> Note: please use the latest gcc 4.8 compiler from linaro
> which support gicv3 system register assembling.
>
> Signed-off-by: David Feng <fenghua@phytium.com.cn>
> ---
I am not well-versed enough in aarch64 and GIC, be it v2 or v3, so...
Is this patch OK as it is, or should a V2 follow with common GIVv2/GICv3
code merged?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-02-21 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 8:10 [U-Boot] [PATCH] arm64 patch: gicv3 support fenghua at phytium.com.cn
2014-01-15 14:19 ` bhupesh.sharma at freescale.com
2014-01-16 1:17 ` FengHua
2014-01-16 3:45 ` bhupesh.sharma at freescale.com
2014-01-16 7:21 ` FengHua
2014-02-07 10:01 ` [U-Boot] " Arnab Basu
[not found] ` <450dad08.17bf3.1441ada3539.Coremail.fenghua@phytium.com.cn>
2014-02-10 10:29 ` Arnab Basu
2014-02-21 16:38 ` Albert ARIBAUD [this message]
2014-02-24 13:22 ` [U-Boot] [PATCH] " FengHua
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=20140221173805.5b642144@lilith \
--to=albert.u.boot@aribaud.net \
--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