linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
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, lethal@linux-sh.org, olof@lixom.net
Subject: Re: [PATCH] gpio: Emma Mobile GPIO driver V2
Date: Wed, 16 May 2012 10:15:39 +0000	[thread overview]
Message-ID: <CANqRtoTCo_Vwe8OMS2ovHNimoe_4ZnCEHk5TQ4YPq8oPJXMObg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdb9LbjvobsJf61VA1Nt8-UCwDZzmjqC8JuN8WPdvhq+iQ@mail.gmail.com>

On Wed, May 16, 2012 at 4:11 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Tue, May 15, 2012 at 5:43 PM, Magnus Damm <magnus.damm@gmail.com> 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>
>
> V2 is fair enough for me, so feel free to add:
> Acked-by: Linus Walleij <linus.walleij@linaro.org>

Thank you! Do you guys have any preferences how to merge this?

Can I include it together with the EMEV2 SoC bits perhaps? That may be
easy so we can keep track of the platform data header file dependency.

Cheers,

/ magnus

  reply	other threads:[~2012-05-16 10:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 15:43 [PATCH] gpio: Emma Mobile GPIO driver V2 Magnus Damm
2012-05-15 16:32 ` Joe Perches
2012-05-17  6:20   ` Magnus Damm
2012-05-16  7:11 ` Linus Walleij
2012-05-16 10:15   ` Magnus Damm [this message]
2012-05-16 11:25     ` Linus Walleij
2012-05-16 20:05       ` Rafael J. Wysocki
2012-05-16 22:22         ` Olof Johansson
2012-05-16 22:37           ` Rafael J. Wysocki
2012-05-16 22:54             ` Olof Johansson
2012-05-18 22:56               ` Grant Likely
2012-05-19  1:18                 ` Olof Johansson
2012-05-19  1:44                   ` Grant Likely
2012-05-19  2:27                     ` Olof Johansson
2012-05-19 12:06               ` Rafael J. Wysocki
2012-05-16  7:29 ` Paul Mundt
2012-05-16 10:09   ` Magnus Damm
2012-05-16 12:09     ` Arnd Bergmann
2012-05-16 15:47       ` Magnus Damm
2012-05-17  0:41       ` Paul Mundt
2012-05-18 23:25         ` Grant Likely
2012-05-19  6:46           ` Paul Mundt
2012-05-19 20:05             ` Grant Likely
2012-05-18 22:57   ` Grant Likely
2012-05-19  2:13     ` Paul Mundt

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=CANqRtoTCo_Vwe8OMS2ovHNimoe_4ZnCEHk5TQ4YPq8oPJXMObg@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=arnd@arndb.de \
    --cc=grant.likely@secretlab.ca \
    --cc=horms@verge.net.au \
    --cc=lethal@linux-sh.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --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).