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 -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html