[PATCH 0/3 v2] The Designware GPIO Supporting

From: Weike Chen
Date: Fri Sep 05 2014 - 03:01:24 EST


Hi,
These patches are for Intel Quark X1000 designware GPIO supporting. The first
patch enables the Synopsys DesignWare APB GPIO driver to support the MFD device.
And the Quark designware GPIO controller is registered as MFD device,
because Quark exports a single PCI device with both GPIO and I2C functions.
It is about reviewing the GPIO changes in gpio-dwapb, and in near future,
the Quark I2C driver and the MFD driver that binds these GPIO & I2C
functions will be sent subsequently. The second patch enables the gpio
'debounce' feature. And the third patch enables the power management.

---
v2:
[PATCH 1/3]
* Fixed a bug to set the base gpio number to '-1' for the OF flow.
* Set device node for each gpio chip for the OF flow.
* Change the name of 'struct dwapb_gpio_platform_data' to
'struct dwapb_platform_data'.
* Change the name of 'struct dwapb_gpio_port_property' to
'struct dwapb_port_property'.
* Access pdata directly in 'probe' instead of accesing it
by 'struct dwapb_gpio'.
* Free 'pdata' at the end of 'probe' if it is OF case to save memory.
* Improve the interrupt handler.
* Move 'irq_set_handler_data' together with 'irq_set_chained_hanlder'.
* Remove unncessary comments.
[PATCH 2/3]
* Change all 'readl'&'writel' to 'dwapb_read'&'dwapb_write'.
[PATCH 3/3]
* Change the name for 'struct gpio_saved_regs' to 'struct dwapb_context'.
* Save the registers for all ports according to the port index.
* Change '#if defined' to '#ifdef'.

Weike Chen (3):
GPIO: gpio-dwapb: Enable platform driver binding to MFD driver
GPIO: gpio-dwapb: Support Debounce
GPIO: gpio-dwapb: Suspend & Resume PM enabling

drivers/gpio/Kconfig | 1 -
drivers/gpio/gpio-dwapb.c | 397 +++++++++++++++++++++++++-----
include/linux/platform_data/gpio-dwapb.h | 32 +++
3 files changed, 365 insertions(+), 65 deletions(-)
create mode 100644 include/linux/platform_data/gpio-dwapb.h

--
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/