From: Alexandre Torgue <alexandre.torgue@st.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <maz@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<marex@denx.de>, <alexandre.torgue@st.com>
Subject: [PATCH v3 0/2] Add GPIO level-sensitive interrupt support
Date: Wed, 19 Feb 2020 15:32:27 +0100 [thread overview]
Message-ID: <20200219143229.18084-1-alexandre.torgue@st.com> (raw)
This series adds the possibility to handle gpio interrupts on level.
GPIO hardware block is directly linked to EXTI block but EXTI handles
external interrupts only on edge. To be able to handle GPIO interrupt on
level a "hack" is done in gpio irq chip: parent interrupt (exti irq chip)
is retriggered following interrupt type and gpio line value.
In exti irq chip, retrigger ops function is added.
Changes since v2:
- Fix issues reported by Marc:
- do not retrigger uselessly a second time in exti irq retrigger callback
- minor comments in pinctrl patch
Changes since v1:
- Fix issue reported by Marek: return statment in "stm32_gpio_set_type"
function.
regards
alex
Alexandre Torgue (2):
irqchip/stm32: Add irq retrigger support
pinctrl: stm32: Add level interrupt support to gpio irq chip
drivers/irqchip/irq-stm32-exti.c | 14 ++++++++-
drivers/pinctrl/stm32/pinctrl-stm32.c | 45 +++++++++++++++++++++++++--
2 files changed, 56 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-19 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:32 Alexandre Torgue [this message]
2020-02-19 14:32 ` [PATCH v3 1/2] irqchip/stm32: Add irq retrigger support Alexandre Torgue
2020-03-29 20:26 ` [tip: irq/core] " tip-bot2 for Alexandre Torgue
2020-02-19 14:32 ` [PATCH v3 2/2] pinctrl: stm32: Add level interrupt support to gpio irq chip Alexandre Torgue
2020-02-20 9:04 ` Linus Walleij
2020-02-20 9:17 ` Marc Zyngier
2020-03-23 19:04 ` Marek Vasut
2020-03-23 19:19 ` Marek Vasut
2020-03-23 19:31 ` Marc Zyngier
2020-03-23 19:37 ` Marek Vasut
2020-03-23 19:49 ` Marc Zyngier
2020-03-23 23:52 ` Marek Vasut
2020-03-23 19:25 ` Marc Zyngier
2020-03-29 20:26 ` [tip: irq/core] " tip-bot2 for Alexandre Torgue
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=20200219143229.18084-1-alexandre.torgue@st.com \
--to=alexandre.torgue@st.com \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=maz@kernel.org \
--cc=tglx@linutronix.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 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).