From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/5] Pinctrl: SPEAr: Add support for plgpio driver
Date: Sat, 27 Oct 2012 15:21:34 +0530 [thread overview]
Message-ID: <cover.1351330569.git.viresh.kumar@linaro.org> (raw)
Hi Linus,
This patchset has an interesting history. It was first started by me. After i
left ST Shiraz took over and now i am back again :)
The idea of this series is to add plgpio support for SPEAr. PLGPIO's are pads
which can be configured as GPIO and so it is closely bound to pinctrl framework.
Some of these are sent earlier and Acked-by you. So, they will retain that. The
main bottleneck is still:
gpiolib: provide provision for gpiolib to register pin range
I have tried to fix most of your comments. Please see if they are fixed.
This is rebased over:
http://www.spinics.net/lists/arm-kernel/msg203465.html
--
viresh
Shiraz Hashim (1):
gpiolib: provide provision for gpiolib to register pin range
Viresh Kumar (4):
Revert "pinctrl: remove pinctrl_remove_gpio_range"
pinctrl: SPEAr: Add plgpio driver
pinctrl: SPEAr: Add gpio ranges support
ARM: SPEAr: Add plgpio node in device tree dtsi files
Documentation/devicetree/bindings/gpio/gpio.txt | 36 ++
Documentation/gpio.txt | 26 +
Documentation/pinctrl.txt | 3 +
arch/arm/boot/dts/spear1310-evb.dts | 4 +
arch/arm/boot/dts/spear1310.dtsi | 27 +
arch/arm/boot/dts/spear1340-evb.dts | 4 +
arch/arm/boot/dts/spear1340.dtsi | 26 +
arch/arm/boot/dts/spear310.dtsi | 22 +-
arch/arm/boot/dts/spear320-evb.dts | 4 +
arch/arm/boot/dts/spear320.dtsi | 23 +-
drivers/gpio/gpiolib-of.c | 56 ++
drivers/gpio/gpiolib.c | 43 ++
drivers/pinctrl/core.c | 27 +
drivers/pinctrl/devicetree.c | 13 +
drivers/pinctrl/spear/Kconfig | 11 +
drivers/pinctrl/spear/Makefile | 1 +
drivers/pinctrl/spear/pinctrl-plgpio.c | 746 ++++++++++++++++++++++++
drivers/pinctrl/spear/pinctrl-spear.c | 107 +++-
drivers/pinctrl/spear/pinctrl-spear.h | 46 ++
drivers/pinctrl/spear/pinctrl-spear1310.c | 264 +++++++++
drivers/pinctrl/spear/pinctrl-spear300.c | 2 +
drivers/pinctrl/spear/pinctrl-spear310.c | 2 +
drivers/pinctrl/spear/pinctrl-spear320.c | 2 +
drivers/pinctrl/spear/pinctrl-spear3xx.c | 37 ++
include/asm-generic/gpio.h | 25 +
include/linux/gpio.h | 3 +
include/linux/pinctrl/pinctrl.h | 19 +
27 files changed, 1560 insertions(+), 19 deletions(-)
create mode 100644 drivers/pinctrl/spear/pinctrl-plgpio.c
--
1.7.12.rc2.18.g61b472e
next reply other threads:[~2012-10-27 9:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 9:51 Viresh Kumar [this message]
2012-10-27 9:51 ` [PATCH V2 1/5] Revert "pinctrl: remove pinctrl_remove_gpio_range" Viresh Kumar
2012-11-06 8:07 ` Linus Walleij
2012-10-27 9:51 ` [PATCH V2 RESEND 2/5] gpiolib: provide provision for gpiolib to register pin range Viresh Kumar
2012-11-06 8:03 ` Linus Walleij
2012-11-06 8:08 ` Viresh Kumar
2012-10-27 9:51 ` [PATCH V2 3/5] pinctrl: SPEAr: Add plgpio driver Viresh Kumar
2012-11-06 8:08 ` Linus Walleij
2012-10-27 9:51 ` [PATCH V2 4/5] pinctrl: SPEAr: Add gpio ranges support Viresh Kumar
2012-11-06 8:09 ` Linus Walleij
2012-11-06 8:11 ` Viresh Kumar
2012-11-06 8:27 ` Linus Walleij
2012-11-11 18:07 ` Linus Walleij
2012-10-27 9:51 ` [PATCH V2 5/5] ARM: SPEAr: Add plgpio node in device tree dtsi files Viresh Kumar
2012-11-11 18:09 ` Linus Walleij
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.1351330569.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).