linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v4 0/2] gpio: mediatek: driver for gpio chip in MT7621 SoC
Date: Thu,  5 Jul 2018 15:43:09 +0200	[thread overview]
Message-ID: <1530798191-25471-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 give it a new try to get mainlined.

Previous comments from Linus Walleij are here:

http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-June/121742.html

Comments from Rob Herring are here:

http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-June/121974.html

Changes in v4:
 - Fix gpio banks naming issues
 - Use custom xlate to be able to use only one node in DT.
 - Add Reviewed-by: NeilBrown <neil at brown.name> to the patches.

Changes in v3:
 - Fix added Makefile entry which was wrong.

Changes in v2 are the ones pointed out in previous mails:

 - use bgpio_init
 - avoid custom irq_domain using IRQF_SHARED and
   gpiochip_set_chained_irqchip from GPIOLIB_IRQCHIP
 - use only one node in the device tree making it simple
 - Implement high and low level irqs
 - avoid include gpio.h
 - use builtin_platform_driver
 - add COMPILE_TEST
 - cleanups after this changes


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         |  35 +++
 drivers/gpio/Kconfig                               |   8 +
 drivers/gpio/Makefile                              |   1 +
 drivers/gpio/gpio-mt7621.c                         | 331 +++++++++++++++++++++
 4 files changed, 375 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt
 create mode 100644 drivers/gpio/gpio-mt7621.c

-- 
2.7.4

             reply	other threads:[~2018-07-05 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05 13:43 Sergio Paracuellos [this message]
2018-07-05 13:43 ` [PATCH v4 1/2] gpio: mediatek: add driver for MT7621 Sergio Paracuellos
2018-07-09 11:45   ` Linus Walleij
2018-07-09 13:28     ` Sergio Paracuellos
2018-07-09 13:30       ` Dan Carpenter
2018-07-09 16:07         ` Sergio Paracuellos
2018-07-05 13:43 ` [PATCH v4 2/2] dt-bindings: document gpio-mt7621 bindings Sergio Paracuellos
2018-07-05 23:11   ` Rob Herring
2018-07-09 11:37   ` Linus Walleij
2018-07-09 12:02     ` Sergio Paracuellos

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=1530798191-25471-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).