[PATCH 00/11] Generalized broadcom cygnus gpio driver
From: Pramod Kumar
Date: Mon Oct 19 2015 - 01:43:20 EST
Generalized pinctrl-cygnus-gpio driver so that it could be used for all
iProc architecture based future SoCs having same gpio pin controller.
Generalization process made the below changes in driver-
1. Removed pin mapping from driver and addressed this via DT through
"gpio-ranges" property.
2. Addressed number of pins from DT through "ngpios" property and removed
from driver.
3. Since all iProc based SoCs would use this driver hence renamed all
variables/macros/functions and even file name on iproc.
This patchset applies on v4.3-rc4 and is tested on cygnus SVK and could be
find at-
https://github.com/Broadcom/arm64-linux/tree/iproc-gpio-v1
Pramod Kumar (11):
dt-bindings: pinctrl: Optional DT property to support pin mappings
pinctrl: Remove GPIO to Pinctrl pin mapping from driver
dts: pinctrl: Add GPIO to Pinctrl pin mapping in DT
dt-binding: Add new compatible string for gpio controller driver
dt-binding: Add ngpios property to GPIO controller node
dts: define ngpios property in gpio controller's node
pinctrl: use ngpios propety from DT
pinctrl: Add new compatible string to GPIO controller driver
gpio: Rename func/macro/var to IP-block,iproc
Documentation: Rename gpio controller name from cygnus to iproc
pinctrl: Rename gpio driver from cygnus to iproc
.../{brcm,cygnus-gpio.txt => brcm,iproc-gpio.txt} | 25 +-
arch/arm/boot/dts/bcm-cygnus.dtsi | 56 +-
drivers/pinctrl/bcm/Kconfig | 30 +-
drivers/pinctrl/bcm/Makefile | 2 +-
drivers/pinctrl/bcm/pinctrl-cygnus-gpio.c | 909 ---------------------
drivers/pinctrl/bcm/pinctrl-iproc-gpio.c | 759 +++++++++++++++++
6 files changed, 854 insertions(+), 927 deletions(-)
rename Documentation/devicetree/bindings/pinctrl/{brcm,cygnus-gpio.txt => brcm,iproc-gpio.txt} (75%)
delete mode 100644 drivers/pinctrl/bcm/pinctrl-cygnus-gpio.c
create mode 100644 drivers/pinctrl/bcm/pinctrl-iproc-gpio.c
--
1.9.1
--
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/