From: Magnus Damm <magnus.damm@gmail.com>
To: linux@arm.linux.org.uk
Cc: kgene.kim@samsung.com, kmpark@infradead.org, konkers@android.com,
tony@atomide.com, adharmap@codeaurora.org, avorontsov@mvista.com,
linux-kernel@vger.kernel.org, srinidhikasagar@gmail.com,
dwalker@codeaurora.org, santosh.shilimkar@ti.com,
ccross@android.com, olof@lixom.net,
Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/07] ARM: Common GIC entry macro code V3
Date: Fri, 12 Nov 2010 17:20:59 +0900 [thread overview]
Message-ID: <20101112082059.27221.52879.sendpatchset@t400s> (raw)
ARM: Common GIC entry macro code V3
[PATCH 01/07] ARM: Introduce asm/hardware/entry-macro-gic.S
[PATCH 02/07] ARM: Use shared GIC entry macros on CNS3XXX
[PATCH 03/07] ARM: Use shared GIC entry macros on Realview
[PATCH 04/07] ARM: Use shared GIC entry macros on Tegra
[PATCH 05/07] ARM: Use shared GIC entry macros on UX500
[PATCH 06/07] ARM: Use shared GIC entry macros on Vexpress
[PATCH 07/07] ARM: Use shared GIC entry macros on OMAP
Put GIC demux code in a common place to avoid duplicated code.
These patches are almost identical to 6284/1 in the RMKs
patch tracker. The main difference is that these ones require
each platform to specify base address using the macro
get_irqnr_preable. Both Tegra and OMAP are supported in V3.
The s5pv310 subarch is excluded due to the special "addne"
instruction in the get_irqnr_and_base macro.
The msm subarch is excluded as well since it treats PPIs
differently than other platforms and needs a different
version of the get_irqnr_and_base macro.
I intend to submit these patches to the RMK patch tracker
unless I hear any objections.
Signed-off-by: Magnus Damm <damm@opensource.se>
---
arch/arm/include/asm/hardware/entry-macro-gic.S | 68 +++++++++++++++
arch/arm/mach-cns3xxx/include/mach/entry-macro.S | 61 -------------
arch/arm/mach-omap2/include/mach/entry-macro.S | 92 +++++++--------------
arch/arm/mach-realview/include/mach/entry-macro.S | 60 -------------
arch/arm/mach-tegra/include/mach/entry-macro.S | 64 --------------
arch/arm/mach-ux500/include/mach/entry-macro.S | 67 ---------------
arch/arm/mach-vexpress/include/mach/entry-macro.S | 57 -------------
7 files changed, 104 insertions(+), 365 deletions(-)
next reply other threads:[~2010-11-12 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 8:20 Magnus Damm [this message]
2010-11-12 8:21 ` [PATCH 01/07] ARM: Introduce asm/hardware/entry-macro-gic.S Magnus Damm
2010-11-12 8:21 ` [PATCH 03/07] ARM: Use shared GIC entry macros on Realview Magnus Damm
2010-11-12 8:21 ` [PATCH 04/07] ARM: Use shared GIC entry macros on Tegra Magnus Damm
2010-11-12 17:14 ` Olof Johansson
2010-11-12 8:21 ` [PATCH 05/07] ARM: Use shared GIC entry macros on UX500 Magnus Damm
2010-11-12 8:22 ` [PATCH 06/07] ARM: Use shared GIC entry macros on Vexpress Magnus Damm
2010-11-12 8:22 ` [PATCH 07/07] ARM: Use shared GIC entry macros on OMAP Magnus Damm
2010-11-12 8:25 ` Shilimkar, Santosh
2010-11-12 17:45 ` Tony Lindgren
2010-11-12 16:46 ` [PATCH 00/07] ARM: Common GIC entry macro code V3 Arnd Bergmann
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=20101112082059.27221.52879.sendpatchset@t400s \
--to=magnus.damm@gmail.com \
--cc=adharmap@codeaurora.org \
--cc=avorontsov@mvista.com \
--cc=ccross@android.com \
--cc=dwalker@codeaurora.org \
--cc=kgene.kim@samsung.com \
--cc=kmpark@infradead.org \
--cc=konkers@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=santosh.shilimkar@ti.com \
--cc=srinidhikasagar@gmail.com \
--cc=tony@atomide.com \
/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