linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Kevin Hilman <khilman@linaro.org>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Lars Poeschel <larsi@wh2.tu-dresden.de>,
	Enric Balletbo i Serra <eballetbo@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] gpio/omap: use gpiolib API to mark a GPIO used as an IRQ
Date: Wed, 16 Oct 2013 10:25:40 +0200	[thread overview]
Message-ID: <525E4D84.4030504@collabora.co.uk> (raw)
In-Reply-To: <CACRpkdYWtgExaaFZ_nV_yX43FXpMCeskjGtKMyVySd+awuepOQ@mail.gmail.com>

On 10/16/2013 10:06 AM, Linus Walleij wrote:
> On Wed, Oct 16, 2013 at 2:47 AM, Javier Martinez Canillas
> <javier.martinez@collabora.co.uk> wrote:
> 
>> The OMAP GPIO driver keeps track about GPIO pins that are
>> used as IRQ lines for two reasons:
>>
>> 1) To prevent GPIO banks to be disabled while one of their
>>    GPIO pins are only used as an interrupt line.
>>
>> 2) To not allow another caller to set the GPIO pin as output.
>>
>> Now gpiolib has an API to mark GPIO pins as used as IRQ lines
>> so the GPIO core only allows to set as output GPIO pins not
>> tied to an IRQ. So there is no need to have custom code for 2).
>>
>> The IRQ usage still has to be maintained locally for 1) though.
>>
>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> 
> Patch applied. I had to merge in v3.12-rc4 to get the dependency
> fixes, so I guess you did something similar when developing
> this...
>

Thanks and yes since this is not a critical bug it was meant to be for v3.13 on
top of fac7fa162 ("gpio/omap: auto-setup a GPIO when used as an IRQ") and after
you have merged your flag-irqs branch.

Sorry for not explicitly mentioning this dependency.

> Yours,
> Linus Walleij
> 

Best regards,
Javier

      reply	other threads:[~2013-10-16  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  0:47 [PATCH 1/1] gpio/omap: use gpiolib API to mark a GPIO used as an IRQ Javier Martinez Canillas
2013-10-16  8:06 ` Linus Walleij
2013-10-16  8:25   ` Javier Martinez Canillas [this message]

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=525E4D84.4030504@collabora.co.uk \
    --to=javier.martinez@collabora.co.uk \
    --cc=eballetbo@gmail.com \
    --cc=khilman@linaro.org \
    --cc=larsi@wh2.tu-dresden.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=swarren@wwwdotorg.org \
    --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;
as well as URLs for NNTP newsgroup(s).