linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SPEAr pinctrl updates for v-3.5
Date: Wed, 9 May 2012 16:45:36 +0530	[thread overview]
Message-ID: <1336562136-24498-1-git-send-email-viresh.kumar@st.com> (raw)

Hi Arnd,Olof,

This have few more dependencies:
- ARM: 7376/1: clkdev: Implement managed clk_get()
- pinctrl branch from Linus

The following changes since commit 880702fb50ec63a832aaeafcb251295f3c6ce722:

  SPEAr: Update defconfigs (2012-05-09 14:53:53 +0530)

are available in the git repository at:

  git://git.stlinux.com/spear/linux-2.6.git for-v3.5-spear-pinctrl-update

for you to fetch changes up to a8f048037fb467b39ac1aeb15361a2c8366d8a2d:

  SPEAr: Add plgpio node in device tree dtsi files (2012-05-09 14:55:55 +0530)

----------------------------------------------------------------
Viresh Kumar (6):
      gpiolib: Add of_get_gpio_chip_by_phandle() helper
      pinctrl: SPEAr: Don't set all non muxreg bits on pinctrl_disable
      pinctrl: SPEAr1310: Fix pin numbers for clcd_high_res
      pinctrl: SPEAr: Add plgpio driver
      pinctrl: SPEAr: Add gpio ranges support
      SPEAr: Add plgpio node in device tree dtsi files

 arch/arm/boot/dts/spear1310-evb.dts       |    4 +
 arch/arm/boot/dts/spear1310.dtsi          |   22 +
 arch/arm/boot/dts/spear1340-evb.dts       |    4 +
 arch/arm/boot/dts/spear1340.dtsi          |   21 +
 arch/arm/boot/dts/spear310-evb.dts        |    4 +
 arch/arm/boot/dts/spear310.dtsi           |   15 +
 arch/arm/boot/dts/spear320-evb.dts        |    4 +
 arch/arm/boot/dts/spear320.dtsi           |   16 +
 drivers/of/gpio.c                         |   32 ++
 drivers/pinctrl/spear/Kconfig             |   11 +
 drivers/pinctrl/spear/Makefile            |    1 +
 drivers/pinctrl/spear/pinctrl-plgpio.c    |  738 +++++++++++++++++++++++++++++
 drivers/pinctrl/spear/pinctrl-spear.c     |  110 ++++-
 drivers/pinctrl/spear/pinctrl-spear.h     |   26 +
 drivers/pinctrl/spear/pinctrl-spear1310.c |  182 +++++++-
 drivers/pinctrl/spear/pinctrl-spear1340.c |    8 +
 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  |   29 ++
 include/linux/of_gpio.h                   |    9 +-
 21 files changed, 1228 insertions(+), 14 deletions(-)
 create mode 100644 drivers/pinctrl/spear/pinctrl-plgpio.c

             reply	other threads:[~2012-05-09 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 11:15 Viresh Kumar [this message]
2012-05-10 11:33 ` [GIT PULL] SPEAr pinctrl updates for v-3.5 viresh kumar
2012-05-12 21:42   ` Arnd Bergmann
2012-05-12 23:54     ` Linus Walleij
2012-05-14  4:02       ` Viresh Kumar
2012-05-17  4:26       ` Viresh Kumar
2012-05-20 20:45         ` Linus Walleij
2012-06-19 14:11           ` viresh kumar
2012-06-20  8:25             ` Linus Walleij
2012-09-01 11:22               ` shiraz hashim
2012-09-03 11:48                 ` Linus Walleij
2012-09-04  4:19                   ` Shiraz Hashim
2012-09-04  7:17                     ` Linus Walleij
2012-10-27  9:33                   ` viresh kumar

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=1336562136-24498-1-git-send-email-viresh.kumar@st.com \
    --to=viresh.kumar@st.com \
    --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).