From: Paul Mundt <lethal@linux-sh.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, rjw@sisk.pl,
linus.walleij@stericsson.com, arnd@arndb.de,
linux-sh@vger.kernel.org, horms@verge.net.au,
grant.likely@secretlab.ca, olof@lixom.net
Subject: Re: [PATCH][RESEND] gpio: Emma Mobile GPIO driver V2
Date: Thu, 17 May 2012 07:24:50 +0000 [thread overview]
Message-ID: <20120517072450.GC11623@linux-sh.org> (raw)
In-Reply-To: <20120517062223.1314.98945.sendpatchset@w520>
On Thu, May 17, 2012 at 03:22:23PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> This patch is V2 of the Emma Mobile GPIO driver. This
> driver is designed to be reusable between multiple SoCs
> that share the same basic building block, but so far it
> has only been used on Emma Mobile EV2.
>
> Each driver instance handles 32 GPIOs with individually
> maskable IRQs. The driver operates on two I/O memory
> ranges and the 32 GPIOs are hooked up to two interrupts.
>
> In the case of Emma Mobile EV2 this GPIO building block
> is used as main external interrupt controller hooking up
> 159 GPIOS as 159 interrupts via 5 driver instances and
> 10 interrupts to the GIC and the Cortex-A9 Dual.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> ---
>
> Rafael, can you please pick up?
>
> Changes since V1:
> - use inline for private data functions using container_of()
> - use BIT(n) instead of 1 << n
> - added legacy irq domain support for static mappings
My distaste for arbitrary static mappings aside, it makes no sense to
support this as a module if the irq domain can't be cleaned up at
present.
next prev parent reply other threads:[~2012-05-17 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 6:22 [PATCH][RESEND] gpio: Emma Mobile GPIO driver V2 Magnus Damm
2012-05-17 7:24 ` Paul Mundt [this message]
2012-05-17 7:46 ` Magnus Damm
2012-05-17 19:27 ` Rafael J. Wysocki
2012-05-18 1:29 ` Simon Horman
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=20120517072450.GC11623@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=horms@verge.net.au \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).