linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 0/9] Enable pinctrl support for mach-mxs
Date: Mon,  7 May 2012 09:16:05 +0800	[thread overview]
Message-ID: <1336353374-28939-1-git-send-email-shawn.guo@linaro.org> (raw)

[Resend to have subsystem lists Cc-ed]

With pinctrl-mxs driver (DT only) applied on pinctrl tree, the mxs
device tree conversion can start basing on that support.  This series
adopts pinctrl support for mxs device drivers with a dummy pinctrl
state provided for non-DT boot, so that the pinctrl call in the device
drivers will be bypassed for non-DT probe while it starts working for
DT probe.

To ease the merge process, I would like to ask Arnd and Olof to pull
pinctrl tree as a dependency in arm-soc and have this series go through
arm-soc.

Regards,
Shawn

Shawn Guo (9):
  ARM: mxs: enable pinctrl dummy states
  serial: amba-pl011: adopt pinctrl support
  serial: mxs-auart: adopt pinctrl support
  mmc: mxs-mmc: adopt pinctrl support
  mtd: nand: gpmi: adopt pinctrl support
  i2c: mxs: adopt pinctrl support
  ASoC: mxs-saif: adopt pinctrl support
  video: mxsfb: adopt pinctrl support
  ARM: mxs: enable pinctrl support

 arch/arm/Kconfig                        |    1 +
 arch/arm/mach-mxs/Kconfig               |    2 ++
 arch/arm/mach-mxs/include/mach/common.h |    2 ++
 arch/arm/mach-mxs/mach-apx4devkit.c     |    2 ++
 arch/arm/mach-mxs/mach-m28evk.c         |    2 ++
 arch/arm/mach-mxs/mach-mx23evk.c        |    2 ++
 arch/arm/mach-mxs/mach-mx28evk.c        |    2 ++
 arch/arm/mach-mxs/mach-stmp378x_devb.c  |    2 ++
 arch/arm/mach-mxs/mach-tx28.c           |    2 ++
 arch/arm/mach-mxs/mm.c                  |   11 +++++++++++
 drivers/i2c/busses/i2c-mxs.c            |    6 ++++++
 drivers/mmc/host/mxs-mmc.c              |    8 ++++++++
 drivers/mtd/nand/gpmi-nand/gpmi-nand.c  |    9 +++++++++
 drivers/tty/serial/amba-pl011.c         |    8 ++++++++
 drivers/tty/serial/mxs-auart.c          |    8 ++++++++
 drivers/video/mxsfb.c                   |    9 +++++++++
 sound/soc/mxs/mxs-saif.c                |    8 ++++++++
 17 files changed, 84 insertions(+), 0 deletions(-)

-- 
1.7.5.4

             reply	other threads:[~2012-05-07  1:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  1:16 Shawn Guo [this message]
2012-05-07  1:16 ` [PATCH RESEND 1/9] ARM: mxs: enable pinctrl dummy states Shawn Guo
2012-05-07  1:16 ` [PATCH RESEND 2/9] serial: amba-pl011: adopt pinctrl support Shawn Guo
2012-05-07  1:16 ` [PATCH RESEND 3/9] serial: mxs-auart: " Shawn Guo
2012-05-07  1:16 ` [PATCH RESEND 4/9] mmc: mxs-mmc: " Shawn Guo
2012-05-07  1:16 ` [PATCH RESEND 5/9] mtd: nand: gpmi: " Shawn Guo
2012-05-07  1:16 ` [PATCH RESEND 6/9] i2c: mxs: " Shawn Guo
2012-05-07  1:16 ` [PATCH RESEND 7/9] ASoC: mxs-saif: " Shawn Guo
2012-05-07 12:04   ` Mark Brown
2012-05-07  1:16 ` [PATCH RESEND 8/9] video: mxsfb: " Shawn Guo
2012-05-07  1:16 ` [PATCH RESEND 9/9] ARM: mxs: enable " Shawn Guo
2012-05-07  7:14 ` [alsa-devel] [PATCH RESEND 0/9] Enable pinctrl support for mach-mxs Dong Aisheng
2012-05-07  7:47   ` Shawn Guo
2012-05-07  8:01     ` Dong Aisheng

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=1336353374-28939-1-git-send-email-shawn.guo@linaro.org \
    --to=shawn.guo@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).