[GIT PULL] pinctrl fixes for v3.8

From: Linus Walleij
Date: Wed Jan 02 2013 - 03:48:25 EST

Hi Linus,

these are the first few pinctrl fixes for the v3.8 cycle, the information
is in the signed tag as usual.

Please pull it in!

Linus Walleij

The following changes since commit a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:

Linux 3.8-rc1 (2012-12-21 17:19:00 -0800)

are available in the git repository at:


for you to fetch changes up to 9fcb4cc2d7dd192ae718f0e7484c6f5c08b8af23:

ARM: ux500: add pinctrl address resources (2012-12-26 01:59:54 +0100)

A first round of pinctrl fixes for v3.8:
- i.MX5 register configuration
- Swap a kfree to devm_kfree() to avoid memory
corruption in the at91 driver
- Add the missing device tree binding doc for the
SIRF pin controller
- Enable the SIRF GPIO pull up/down configuration
from the device tree, it was previously retired
from the hard-coded approach.
- NULL check for the prcm_base in the Nomadik pin
- Provide the prcm_base from the device tree in the
DT boot path for the Nomadik pin controller.

Barry Song (2):
pinctrl: sirf: add missing DT-binding document
pinctrl: sirf: enable GPIO pullup/down configuration from dts

Fabio Baltieri (2):
pinctrl: nomadik: return if prcm_base is NULL
ARM: ux500: add pinctrl address resources

Julia Lawall (1):
drivers/pinctrl/pinctrl-at91.c: convert kfree to devm_kfree

Linus Walleij (1):
pinctrl: fix comment mistake

Philipp Zabel (1):
pinctrl: imx5: fix GPIO_8 pad CAN1_RXCAN configuration

.../devicetree/bindings/pinctrl/pinctrl-sirf.txt | 47 +++++++++++++++++++++
arch/arm/boot/dts/dbx5x0.dtsi | 4 +-
arch/arm/mach-ux500/cpu-db8500.c | 3 +-
drivers/pinctrl/core.c | 2 +-
drivers/pinctrl/pinctrl-at91.c | 2 +-
drivers/pinctrl/pinctrl-imx53.c | 2 +-
drivers/pinctrl/pinctrl-nomadik.c | 11 ++++-
drivers/pinctrl/pinctrl-sirf.c | 48 ++++++++++++++++++++++
8 files changed, 113 insertions(+), 6 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-sirf.txt
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/