From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Thierry Reding <thierry.reding@avionic-design.de>,
Lars Poeschel <poeschel@lemonage.de>
Cc: Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH v2] gpio: lock adnp IRQs when enabling them
Date: Tue, 26 Nov 2013 15:15:38 +0200 [thread overview]
Message-ID: <52949EFA.3060903@ti.com> (raw)
In-Reply-To: <1385460324-30777-1-git-send-email-linus.walleij@linaro.org>
On 11/26/2013 12:05 PM, Linus Walleij wrote:
> This uses the new API for tagging GPIO lines as in use by
> IRQs. This enforces a few semantic checks on how the underlying
> GPIO line is used.
>
> Only compile tested on the lpc32xx.
>
> Cc: Lars Poeschel <poeschel@lemonage.de>
> Cc: Thierry Reding <thierry.reding@avionic-design.de>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Use the .enable() callback from the irq_chip
> - Call .unmask() from the .enable() callback to satisfy semantics.
> ---
> drivers/gpio/gpio-adnp.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/gpio/gpio-adnp.c b/drivers/gpio/gpio-adnp.c
> index b204033acaeb..3988ebc5a40e 100644
> --- a/drivers/gpio/gpio-adnp.c
> +++ b/drivers/gpio/gpio-adnp.c
> @@ -408,6 +408,25 @@ static void adnp_irq_bus_unlock(struct irq_data *data)
> mutex_unlock(&adnp->irq_lock);
> }
>
> +static void adnp_irq_enable(struct irq_data *data)
> +{
> + struct adnp *adnp = irq_data_get_irq_chip_data(data);
> +
> + if (gpio_lock_as_irq(&adnp->gpio, data->hwirq))
> + dev_err(adnp->gpio.dev,
> + "unable to lock HW IRQ %lu for IRQ\n",
> + data->hwirq);
> + /* Satisfy the .enable semantics by unmasking the line */
> + adnp_irq_unmask(data);
> +}
> +
> +static void adnp_irq_disable(struct irq_data *data)
> +{
> + struct adnp *adnp = irq_data_get_irq_chip_data(data);
> +
> + gpio_unlock_as_irq(&adnp->gpio, data->hwirq);
> +}
> +
> static struct irq_chip adnp_irq_chip = {
> .name = "gpio-adnp",
> .irq_mask = adnp_irq_mask,
> @@ -415,6 +434,8 @@ static struct irq_chip adnp_irq_chip = {
> .irq_set_type = adnp_irq_set_type,
> .irq_bus_lock = adnp_irq_bus_lock,
> .irq_bus_sync_unlock = adnp_irq_bus_unlock,
> + .irq_enable = adnp_irq_enable,
> + .irq_disable = adnp_irq_disable,
.irq_startup/irq_shutdown ?
> };
>
> static int adnp_irq_map(struct irq_domain *domain, unsigned int irq,
>
next prev parent reply other threads:[~2013-11-26 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 10:05 [PATCH v2] gpio: lock adnp IRQs when enabling them Linus Walleij
2013-11-26 13:15 ` Grygorii Strashko [this message]
2013-11-29 9:49 ` 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=52949EFA.3060903@ti.com \
--to=grygorii.strashko@ti.com \
--cc=acourbot@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=poeschel@lemonage.de \
--cc=thierry.reding@avionic-design.de \
/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.