From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] at91: gpio: use gpiolib API to mark a GPIO used as an IRQ
Date: Wed, 12 Mar 2014 18:29:26 +0100 [thread overview]
Message-ID: <53209976.80008@atmel.com> (raw)
In-Reply-To: <5320714C.3050306@atmel.com>
On 12/03/2014 15:38, Nicolas Ferre :
> On 31/01/2014 09:57, Nicolas Ferre :
>> On 31/01/2014 08:55, Linus Walleij :
>>> On Thu, Jan 23, 2014 at 11:37 AM, Jean-Jacques Hiblot
>>> <jjhiblot@traphandler.com> wrote:
>>>
>>>> When an IRQ is started on a GPIO line, mark this GPIO as IRQ in
>>>> the gpiolib so we can keep track of the usage centrally.
>>>>
>>>> Signed-off-by: Jean-Jacques Hiblot <jjhiblot@traphandler.com>
>>>
>>> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>>>
>>> Nicolas, are you queueing this patch?
>>
>> Yes, I will.
>
> stacked on at91-3.15-cleanup branch.
... And immediately removed thanks to Boris' advice: it seems that you
will move to a gpio_irq_request/release_resources() model.
So, we might wait for the solution to settle in 3.15-rc before building
on top of it.
Thanks, bye,
>>> I guess this custom GPIO implementation is going away with
>>> the transition to pinctrl else I'd requested that it be moved to
>>> drivers/gpio...
>>
>> Absolutely. But I suspect it will still be around for some time...
>>
>> Thanks for your review. Bye,
>>
>
>
--
Nicolas Ferre
next prev parent reply other threads:[~2014-03-12 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 10:37 [PATCH v2 0/2] at91: gpio: pinctrl: use gpiolib API to mark a GPIO used as an IRQ Jean-Jacques Hiblot
2014-01-23 10:37 ` [PATCH v2 1/2] at91: gpio: " Jean-Jacques Hiblot
2014-01-31 7:55 ` Linus Walleij
2014-01-31 8:57 ` Nicolas Ferre
2014-02-07 8:07 ` Jean-Christophe PLAGNIOL-VILLARD
2014-03-12 14:38 ` Nicolas Ferre
2014-03-12 17:29 ` Nicolas Ferre [this message]
2014-03-14 10:17 ` Linus Walleij
2014-01-23 10:37 ` [PATCH v2 2/2] at91: pinctrl: " Jean-Jacques Hiblot
2014-01-31 7:57 ` Linus Walleij
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=53209976.80008@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.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 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).