From: Neil Armstrong <narmstrong@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Peter Rosin <peda@axentia.se>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Roland Stigge <stigge@antcom.de>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Subject: Re: [PATCH v3] pinctrl: Add SX150X GPIO Extender Pinctrl Driver
Date: Tue, 25 Oct 2016 08:57:08 +0200 [thread overview]
Message-ID: <580F0244.7070701@baylibre.com> (raw)
In-Reply-To: <CACRpkdY7vLU4yVP7M-O4rGt_L5cqL57ApmMQJ4aRGgzh3Nat6Q@mail.gmail.com>
Hi Linus,
Le 24/10/2016 16:39, Linus Walleij a écrit :
> On Mon, Oct 24, 2016 at 6:51 AM, Andrey Smirnov
> <andrew.smirnov@gmail.com> wrote:
>
>> It seem strange to me that the driver uses "handle_edge_irq", given
>> how none of the individual interrupts seem to require any ACKing,
>> since it is all handled in sx150x_irq_thread_fn(), line 533. More so,
>> I had trouble finding who/where sets .irq_ack() callback, which AFAIU
>> is mandatory for handle_edge_irq().
>
> Yes that looks strange.
>
> Neil have you tested IRQs with this code?
To be frank, I took the IRQ code from the GPIO driver verbatim, and only tested
a simple use case on beagle bone black.
The interrupt code is very complex and sincerely I was not able to understand
clearly how it worked.
The IRQ_TYPE_EDGE_BOTH did work for me since the BBB irq controller dealt with it.
I will dig in the datasheet and run more uses cases next week, but since the
code hasn't changed since the GPIO driver, so this is a nice to have !
>
> If there is trouble, please follow up with a fix for the edge handler.
> Maybe it should just be handle_simple_irq().
>
> Yours,
> Linus Walleij
>
Andrey, can we talk over irc somehow ? I'm idling as narmstrong on freenode.
Neil
next prev parent reply other threads:[~2016-10-25 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 9:09 [PATCH v3] pinctrl: Add SX150X GPIO Extender Pinctrl Driver Neil Armstrong
2016-10-21 9:09 ` Neil Armstrong
2016-10-21 9:19 ` Neil Armstrong
[not found] ` <1477040998-2016-1-git-send-email-narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-10-23 2:50 ` Andrey Smirnov
2016-10-23 2:50 ` Andrey Smirnov
2016-10-23 10:47 ` Linus Walleij
2016-10-24 4:51 ` Andrey Smirnov
2016-10-24 14:39 ` Linus Walleij
2016-10-25 6:57 ` Neil Armstrong [this message]
2016-10-23 10:41 ` Linus Walleij
2016-10-23 10:41 ` 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=580F0244.7070701@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=andrew.smirnov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=stigge@antcom.de \
--cc=vladimir_zapolskiy@mentor.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.