From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [PATCH 0/3] gpio: lpc32xx: enable interrupts for port 3
Date: Wed, 10 Apr 2019 12:39:23 +0200 [thread overview]
Message-ID: <20190410103926.8781-1-alexandre.belloni@bootlin.com> (raw)
Hi,
This series enables interrupt support for GPIOs on port 3. Those are the
GPIOs that are connected directl to an interrupt controller (sic1 or
sic2). This was tested on a custom LPC3250 design.
The binding includes support for interrupts on port 0 and port 1 but
this requires the registration of a proper irqchip and I don't have any
way to test it.
Patch 1 and 2 should probably go through the gpio tree while patch 3
should go through arm-soc. They are quite independant and this shoud
cause no issue.
Alexandre Belloni (3):
dt-bindings: gpio: lpc32xx: document interrupt bindings
gpio: lpc32xx: enable interrupt lookup for port 3
ARM: dts: lpc32xx: add GPIO interrupts
.../devicetree/bindings/gpio/gpio_lpc32xx.txt | 4 +++
arch/arm/boot/dts/lpc32xx.dtsi | 25 +++++++++++++++++++
drivers/gpio/gpio-lpc32xx.c | 14 ++++-------
3 files changed, 34 insertions(+), 9 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-10 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 10:39 Alexandre Belloni [this message]
2019-04-10 10:39 ` [PATCH 1/3] dt-bindings: gpio: lpc32xx: document interrupt bindings Alexandre Belloni
2019-04-11 13:49 ` Linus Walleij
2019-04-10 10:39 ` [PATCH 2/3] gpio: lpc32xx: enable interrupt lookup for port 3 Alexandre Belloni
2019-04-11 13:55 ` Linus Walleij
2019-04-15 13:12 ` Sylvain Lemieux
2019-04-10 10:39 ` [PATCH 3/3] ARM: dts: lpc32xx: add GPIO interrupts Alexandre Belloni
2019-04-10 10:53 ` [PATCH v2 " Alexandre Belloni
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=20190410103926.8781-1-alexandre.belloni@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--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=vz@mleia.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).