From: Phil Edworthy <phil.edworthy@renesas.com>
To: Hoan Tran <hotran@apm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Lee Jones <lee.jones@linaro.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Michel Pollet <michel.pollet@bp.renesas.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Phil Edworthy <phil.edworthy@renesas.com>
Subject: [PATCH v2 0/2] gpio: dwapb: Add support for 1 interrupt per port A GPIO
Date: Fri, 13 Apr 2018 09:08:18 +0100 [thread overview]
Message-ID: <1523606900-2332-1-git-send-email-phil.edworthy@renesas.com> (raw)
All details about the change is in patch 0001. patch 0002 fixes up other users
of 'struct dwapb_port_property'.
One point to mention is that I have made it possible for users to have
unconncted interrupts by specifying holes in the list of interrupts. This is
done by supporting the interrupts-extended DT prop.
However, I have no use for this and had to hack some test case for this.
Perhaps the driver should support 1 interrupt or all GPIOa as interrupts?
Phil Edworthy (2):
gpio: dwapb: Add support for 1 interrupt per port A GPIO
mfd: intel_quark_i2c_gpio: Update Synopsys GPIO interrupts
.../devicetree/bindings/gpio/snps-dwapb-gpio.txt | 9 ++++-
drivers/gpio/gpio-dwapb.c | 43 +++++++++++++++++-----
drivers/mfd/intel_quark_i2c_gpio.c | 3 +-
include/linux/platform_data/gpio-dwapb.h | 3 +-
4 files changed, 45 insertions(+), 13 deletions(-)
--
2.7.4
next reply other threads:[~2018-04-13 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 8:08 Phil Edworthy [this message]
2018-04-13 8:08 ` [PATCH v2 1/2] gpio: dwapb: Add support for 1 interrupt per port A GPIO Phil Edworthy
2018-04-13 22:16 ` kbuild test robot
2018-04-14 0:46 ` kbuild test robot
2018-04-13 8:08 ` [PATCH v2 2/2] mfd: intel_quark_i2c_gpio: Update Synopsys GPIO interrupts Phil Edworthy
2018-04-13 8:20 ` Geert Uytterhoeven
2018-04-13 8:24 ` Phil Edworthy
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=1523606900-2332-1-git-send-email-phil.edworthy@renesas.com \
--to=phil.edworthy@renesas.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hotran@apm.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michel.pollet@bp.renesas.com \
--cc=robh+dt@kernel.org \
/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).