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 v2 0/2] Move Freescale MXS gpio driver into drivers/gpio
Date: Sat, 28 May 2011 23:09:32 +0800	[thread overview]
Message-ID: <1306595374-25178-1-git-send-email-shawn.guo@linaro.org> (raw)

The patch set moves Freescale MXS gpio driver from mach-mxs into
drivers/gpio.

Changes since v1:
 * Squash the 4 gpio-mxs patches into one
 * Do not add new gpio Kconfig option and use ARCH_MXS directly
 * Clean up platform-gpio-mxs.c per Arnd's comments
 * Add device mxs_apbh_bus and set it as the parent of gpio devices

Shawn Guo (2):
      gpio: gpio-mxs: add gpio driver for Freescale MXS architecture
      ARM: mxs: use gpio-mxs driver by adding platform device

 arch/arm/mach-mxs/Makefile                         |    2 +-
 arch/arm/mach-mxs/devices.c                        |   11 +
 arch/arm/mach-mxs/devices/Makefile                 |    1 +
 arch/arm/mach-mxs/devices/platform-gpio-mxs.c      |   53 +++++
 arch/arm/mach-mxs/gpio.h                           |   34 ---
 arch/arm/mach-mxs/include/mach/devices-common.h    |    2 +
 arch/arm/mach-mxs/mach-mx28evk.c                   |    1 -
 arch/arm/mach-mxs/mm-mx23.c                        |    1 -
 arch/arm/mach-mxs/mm-mx28.c                        |    1 -
 drivers/gpio/Makefile                              |    1 +
 .../arm/mach-mxs/gpio.c => drivers/gpio/gpio-mxs.c |  228 ++++++++++++--------

             reply	other threads:[~2011-05-28 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28 15:09 Shawn Guo [this message]
2011-05-28 15:09 ` [PATCH v2 1/2] gpio: gpio-mxs: add gpio driver for Freescale MXS architecture Shawn Guo
2011-05-28 15:09 ` [PATCH v2 2/2] ARM: mxs: use gpio-mxs driver by adding platform device Shawn Guo
2011-05-29 19:16   ` Arnd Bergmann
2011-05-30  6:45 ` [PATCH v2 0/2] Move Freescale MXS gpio driver into drivers/gpio Sascha Hauer
2011-06-03 17:57   ` Grant Likely

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=1306595374-25178-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).