From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Semen Protsenko <semen.protsenko@globallogic.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: max732x: Add IRQF_SHARED to irq flags
Date: Wed, 22 Apr 2015 22:53:05 +0300 [thread overview]
Message-ID: <5537FC21.9050602@mentor.com> (raw)
In-Reply-To: <1429622344-19429-1-git-send-email-semen.protsenko@globallogic.com>
Hi Semen,
On 21.04.2015 16:19, Semen Protsenko wrote:
> It's possible that multiple MAX732X can be hooked up to the same
> interrupt line with the processor. So add IRQF_SHARED in requesting irq.
>
> Signed-off-by: Semen Protsenko <semen.protsenko@globallogic.com>
> ---
> drivers/gpio/gpio-max732x.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpio/gpio-max732x.c b/drivers/gpio/gpio-max732x.c
> index 0fa4543..55b13d4 100644
> --- a/drivers/gpio/gpio-max732x.c
> +++ b/drivers/gpio/gpio-max732x.c
> @@ -507,12 +507,10 @@ static int max732x_irq_setup(struct max732x_chip *chip,
> chip->irq_features = has_irq;
> mutex_init(&chip->irq_lock);
>
> - ret = devm_request_threaded_irq(&client->dev,
> - client->irq,
> - NULL,
> - max732x_irq_handler,
> - IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> - dev_name(&client->dev), chip);
> + ret = devm_request_threaded_irq(&client->dev, client->irq,
> + NULL, max732x_irq_handler, IRQF_ONESHOT |
> + IRQF_TRIGGER_FALLING | IRQF_SHARED,
> + dev_name(&client->dev), chip);
is it still the case that for shared interrupts a hard IRQ handler is
mandatory to have?
Here I rely on
http://lists.kernelnewbies.org/pipermail/kernelnewbies/2011-March/001118.html
With best wishes,
Vladimir
next prev parent reply other threads:[~2015-04-22 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 13:19 [PATCH] gpio: max732x: Add IRQF_SHARED to irq flags Semen Protsenko
2015-04-22 19:53 ` Vladimir Zapolskiy [this message]
2015-04-23 14:15 ` Sam Protsenko
2015-05-06 13:07 ` Linus Walleij
2015-05-06 13:27 ` Sam Protsenko
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=5537FC21.9050602@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=semen.protsenko@globallogic.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).