devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: [PATCH v3 0/3] Add device tree probe for imx/mxc gpio
Date: Thu, 7 Jul 2011 00:37:40 +0800	[thread overview]
Message-ID: <1309970263-13239-1-git-send-email-shawn.guo@linaro.org> (raw)

The first patch removes the uses of cpu_is_mx(), the second one
changes mxc gpio number macro, and the third one adds actual device
tree probe support.

Changes since v2:
 * Keep platform case gpio range code path unchanged, and get range
   from gpio core only for dt case.

Changes since v1:
 * Address review comments given by Grant and Sascha
 * Add patch #1 to get gpio range/base from gpio core

Shawn Guo (3):
      gpio/mxc: get rid of the uses of cpu_is_mx()
      ARM: mxc: use ARCH_NR_GPIOS to define gpio number
      gpio/mxc: add device tree probe support

 .../devicetree/bindings/gpio/fsl-imx-gpio.txt      |   22 +++
 arch/arm/mach-imx/mm-imx1.c                        |    8 +-
 arch/arm/mach-imx/mm-imx21.c                       |   12 +-
 arch/arm/mach-imx/mm-imx25.c                       |    9 +-
 arch/arm/mach-imx/mm-imx27.c                       |   13 +-
 arch/arm/mach-imx/mm-imx31.c                       |    6 +-
 arch/arm/mach-imx/mm-imx35.c                       |    7 +-
 arch/arm/mach-mx5/mm-mx50.c                        |   13 +-
 arch/arm/mach-mx5/mm.c                             |   24 ++--
 arch/arm/plat-mxc/devices/platform-gpio-mxc.c      |    4 +-
 arch/arm/plat-mxc/include/mach/common.h            |    2 +-
 arch/arm/plat-mxc/include/mach/irqs.h              |   21 +---
 drivers/gpio/gpio-mxc.c                            |  157 +++++++++++++++++---
 13 files changed, 211 insertions(+), 87 deletions(-)

             reply	other threads:[~2011-07-06 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 16:37 Shawn Guo [this message]
     [not found] ` <1309970263-13239-1-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-07-06 16:37   ` [PATCH v3 1/3] gpio/mxc: get rid of the uses of cpu_is_mx() Shawn Guo
2011-07-06 16:37   ` [PATCH v3 2/3] ARM: mxc: use ARCH_NR_GPIOS to define gpio number Shawn Guo
2011-07-07  7:47     ` Sascha Hauer
2011-07-07 15:13       ` Shawn Guo
     [not found]         ` <20110707151331.GB12722-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2011-07-07 19:26           ` Grant Likely
2011-07-07 19:24       ` Grant Likely
2011-07-06 16:37   ` [PATCH v3 3/3] gpio/mxc: add device tree probe support Shawn Guo
2011-07-07 19:27 ` [PATCH v3 0/3] Add device tree probe for imx/mxc gpio Grant Likely
2011-07-08 10:36   ` Sascha Hauer
2011-07-08 18:38     ` Grant Likely
2011-07-09  6:30       ` Shawn Guo

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=1309970263-13239-1-git-send-email-shawn.guo@linaro.org \
    --to=shawn.guo-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).