From: Stefan Agner <stefan@agner.ch>
To: linus.walleij@linaro.org, shawn.guo@freescale.com
Cc: gnurou@gmail.com, kernel@pengutronix.de,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bpringlemeir@nbsps.com,
l.stach@pengutronix.de, stefan@agner.ch
Subject: [PATCH v4 0/4] vf610: Add GPIO support
Date: Fri, 26 Sep 2014 13:57:07 +0200 [thread overview]
Message-ID: <cover.1411731755.git.stefan@agner.ch> (raw)
Rebased version on top of pinctrl branch. In Shawn's tree the
Colibri VF61 DT file is already split, hence this v4 would not apply
cleanly. But I guess patch 3/4 goes anyway through Shawn's branch.
Shawn, to have that patch applying cleanly, you need to pick the
patch from v3 patchset.
Since 3rd version of the GPIO support for Vybrid now also includes
the wakeup support which was part of the suspend/resume patchset
I sent earlier this week.
Changes in v4:
- Rebased on pinctrl devel branch (which has one patch already applied
hence is not part of this version now)
Changes in v3:
- Configure the pin completely on imx_pmx_gpio_request_enable
- Drop the GPIO_CONTROL flag in favor of using the existing
SHARE_MUX_CONF_REG flag
- Extend GPIO driver to also include wakeup support
- Cleanup includes in GPIO driver file
- Add brackets in PORT_PCR define
- Use platform_get_irq in favor of irq_of_parse_and_map
- Use device_initcall instead of subsys_initicall
Changes in v2:
- Use bit operations in GPIO driver
- Use VF610_ prefix for GPIOS_PER_PORT define
- Drop irq in drivers struct
- Use arch/subsys_initicall for GPIO/pinctrl driver
- Fix log message title
- Add documentation for GPIO/PORT module bindings
- Extended GPIO device tree bindings for Colibri VF61
Stefan Agner (4):
pinctrl: imx: add gpio pinmux support for vf610
gpio: vf610: add gpiolib/IRQ chip driver for Vybrid
ARM: dts: vf610: use new GPIO support
Documentation: dts: add bindings for Vybrid GPIO/PORT module
.../devicetree/bindings/gpio/gpio-vf610.txt | 56 ++++
arch/arm/boot/dts/vf610-colibri.dts | 9 +
arch/arm/boot/dts/vf610-twr.dts | 1 +
arch/arm/boot/dts/vf610.dtsi | 1 +
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-vf610.c | 295 +++++++++++++++++++++
drivers/pinctrl/freescale/pinctrl-imx.c | 72 +++++
8 files changed, 442 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-vf610.txt
create mode 100644 drivers/gpio/gpio-vf610.c
--
2.1.0
next reply other threads:[~2014-09-26 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 11:57 Stefan Agner [this message]
2014-09-26 11:57 ` [PATCH v4 1/4] pinctrl: imx: add gpio pinmux support for vf610 Stefan Agner
2014-09-26 11:57 ` [PATCH v4 2/4] gpio: vf610: add gpiolib/IRQ chip driver for Vybrid Stefan Agner
2014-10-15 7:27 ` Linus Walleij
2014-09-26 11:57 ` [PATCH v4 3/4] ARM: dts: vf610: use new GPIO support Stefan Agner
2014-09-26 11:57 ` [PATCH v4 4/4] Documentation: dts: add bindings for Vybrid GPIO/PORT module Stefan Agner
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=cover.1411731755.git.stefan@agner.ch \
--to=stefan@agner.ch \
--cc=bpringlemeir@nbsps.com \
--cc=gnurou@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--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=shawn.guo@freescale.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).