From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH 00/07] ARM: mach-shmobile: External IRQ pin update
Date: Wed, 12 Oct 2011 07:20:52 +0000 [thread overview]
Message-ID: <20111012072052.25511.44444.sendpatchset@w520> (raw)
ARM: mach-shmobile: External IRQ pin update
[PATCH 01/07] ARM: mach-shmobile: Break out INTC IRQ code
[PATCH 02/07] sh: intc: Allow triggering on both edges for ARM SoCs
[PATCH 03/07] ARM: mach-shmobile: Use common INTC IRQ code on sh7367
[PATCH 04/07] ARM: mach-shmobile: Use common INTC IRQ code on sh7377
[PATCH 05/07] ARM: mach-shmobile: Use common INTC IRQ code on sh7372
[PATCH 06/07] ARM: mach-shmobile: Use common INTC IRQ code on sh73a0
[PATCH 07/07] ARM: mach-shmobile: SDHI0 GPIO hotplug for AG5EVM
These patches update the per-SoC IRQ pin handling code. Common code
is broken out into a head file macro, the INTC IRQ triggering gets
updated to include both edge triggering. INTCA-based SoCs such as
sh7367, sh7377 and sh7372 are all converted to make use of the new
INTC macros. sh73a0 gets external IRQ support through INTCA instead
of relying on the GIC which only has limited triggering support.
As a final test case the SDHI0 hardware block on AG5EVM is converted
to use GPIO IRQ for hotplug - allowing power down of the SD controller
while waiting for card insert or eject events.
Signed-off-by: Magnus Damm <damm@opensource.se>
---
arch/arm/mach-shmobile/board-ag5evm.c | 19 ++
arch/arm/mach-shmobile/include/mach/intc.h | 195 ++++++++++++++++++++++++++++
arch/arm/mach-shmobile/intc-sh7367.c | 40 -----
arch/arm/mach-shmobile/intc-sh7372.c | 72 +---------
arch/arm/mach-shmobile/intc-sh7377.c | 67 ---------
arch/arm/mach-shmobile/intc-sh73a0.c | 122 +++++++++++++++++
arch/arm/mach-shmobile/pfc-sh73a0.c | 68 +++++----
drivers/sh/intc/chip.c | 2
8 files changed, 392 insertions(+), 193 deletions(-)
damm@w520 ~/patches/20111012 $
reply other threads:[~2011-10-12 7:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111012072052.25511.44444.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--cc=linux-sh@vger.kernel.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 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.