From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: linus.walleij@linaro.org
Cc: devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
driverdev-devel@linuxdriverproject.org,
linux-gpio@vger.kernel.org, robh+dt@kernel.org, neil@brown.name
Subject: [PATCH 0/2] gpio: mediatek: driver for gpio chip in MT7621 SoC
Date: Sat, 2 Jun 2018 09:30:08 +0200 [thread overview]
Message-ID: <1527924610-13135-1-git-send-email-sergio.paracuellos@gmail.com> (raw)
This patch series add support for gpio driver in mediatek MT7621
SoC. This driver has been in staging for a while and after some
cleanups cycles we consider to git it a try to get mainlined.
The functionality is presented as a single irq-chip but 3 separate
gpio-chips, as this seemed simplest. Is this acceptable, or does it
need to be changed? We'd like to have review comments and feedback
specially for this.
Hope this helps and thanks in advance.
Best regards,
Sergio Paracuellos
Sergio Paracuellos (2):
gpio: mediatek: add driver for MT7621
dt-bindings: document gpio-mt7621 bindings
.../bindings/gpio/mediatek,mt7621-gpio.txt | 68 ++++
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-mt7621.c | 370 +++++++++++++++++++++
4 files changed, 446 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt
create mode 100644 drivers/gpio/gpio-mt7621.c
--
2.7.4
next reply other threads:[~2018-06-02 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 7:30 Sergio Paracuellos [this message]
2018-06-02 7:30 ` [PATCH 1/2] gpio: mediatek: add driver for MT7621 Sergio Paracuellos
2018-06-08 11:59 ` Linus Walleij
2018-06-08 12:17 ` Linus Walleij
2018-06-09 6:17 ` Sergio Paracuellos
2018-06-09 5:54 ` Sergio Paracuellos
2018-06-11 3:29 ` Sean Wang
2018-06-02 7:30 ` [PATCH 2/2] dt-bindings: document gpio-mt7621 bindings Sergio Paracuellos
2018-06-12 20:56 ` Rob Herring
2018-06-13 9:40 ` Dan Carpenter
2018-06-13 16:23 ` Sergio Paracuellos
2018-06-13 19:28 ` Rob Herring
2018-06-14 4:45 ` Sergio Paracuellos
2018-06-14 14:17 ` Linus Walleij
2018-06-14 16:20 ` Sergio Paracuellos
2018-06-14 14:14 ` Linus Walleij
2018-06-14 14:33 ` Rob Herring
2018-06-14 14:48 ` 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=1527924610-13135-1-git-send-email-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=neil@brown.name \
--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).