From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH] gpio: lynxpoint: lock IRQs when starting them
Date: Wed, 20 Nov 2013 20:29:12 +0200 [thread overview]
Message-ID: <528CFF78.9080703@ti.com> (raw)
In-Reply-To: <1384958549-23722-1-git-send-email-linus.walleij@linaro.org>
Hi Linus,
On 11/20/2013 04:42 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.
>
> Cc: Mathias Nyman <mathias.nyman@linux.intel.com>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/gpio/gpio-lynxpoint.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/gpio/gpio-lynxpoint.c b/drivers/gpio/gpio-lynxpoint.c
> index f1ca9d5880b6..8c7634250aff 100644
> --- a/drivers/gpio/gpio-lynxpoint.c
> +++ b/drivers/gpio/gpio-lynxpoint.c
> @@ -301,6 +301,24 @@ static void lp_irq_disable(struct irq_data *d)
> spin_unlock_irqrestore(&lg->lock, flags);
> }
>
> +static unsigned int lp_irq_startup(struct irq_data *d)
> +{
> + struct lp_gpio *lg = irq_data_get_irq_chip_data(d);
> +
> + if (gpio_lock_as_irq(&lg->chip, irqd_to_hwirq(d)))
> + dev_err(lg->chip.dev,
> + "unable to lock HW IRQ %lu for IRQ\n",
> + irqd_to_hwirq(d));
> + return 0;
> +}
> +
> +static void lp_irq_shutdown(struct irq_data *d)
> +{
> + struct lp_gpio *lg = irq_data_get_irq_chip_data(d);
> +
> + gpio_unlock_as_irq(&lg->chip, irqd_to_hwirq(d));
> +}
Seems, such changes may be risky, because .irq_startup()
and irq_enable()/irq_umask() are mutually exclusive, at least at IRQ request time.
request_threaded_irq()->__setup_irq()->irq_startup()
More over, IRQ core assumes that IRQ is enabled, unmasked and ready for use after
.irq_startup() call. You can check functions irq/chip.c->irq_startup() for more info.
So, .irq_enable() functionality need to be duplicated in .irq_startup() at least.
if you agree - above comment is valid for most of similar recent patches ;)
> +
> static struct irq_chip lp_irqchip = {
> .name = "LP-GPIO",
> .irq_mask = lp_irq_mask,
> @@ -308,6 +326,8 @@ static struct irq_chip lp_irqchip = {
> .irq_enable = lp_irq_enable,
> .irq_disable = lp_irq_disable,
> .irq_set_type = lp_irq_type,
> + .irq_startup = lp_irq_startup,
> + .irq_shutdown = lp_irq_shutdown,
> .flags = IRQCHIP_SKIP_SET_WAKE,
> };
>
>
Regards,
-grygorii
next prev parent reply other threads:[~2013-11-20 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 14:42 [PATCH] gpio: lynxpoint: lock IRQs when starting them Linus Walleij
2013-11-20 18:29 ` Grygorii Strashko [this message]
2013-11-26 9:52 ` Linus Walleij
2013-11-26 13:18 ` Grygorii Strashko
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=528CFF78.9080703@ti.com \
--to=grygorii.strashko@ti.com \
--cc=acourbot@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.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 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.