linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: linux-mmc <linux-mmc@vger.kernel.org>, linux-samsung-soc@vger.kernel.org
Cc: Chris Ball <cjb@laptop.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	'kgene kim' <kgene.kim@samsung.com>
Subject: [PATCH v3 0/4] mmc: sdhci-s3c: use the sdhci-pltfm.c and move the header file
Date: Tue, 06 Mar 2012 15:17:20 +0900	[thread overview]
Message-ID: <4F55ABF0.1060801@samsung.com> (raw)

This patchset is the purpose for using sdhci-pltfm.c and 
removing the arch dependency.
The sdhci-s3c has too heavy arch dependency.
For example, if work for sdhci-s3c.c at mmc-tree, sometime need to change sdhci.h for Samsung-Soc.
But now we need to work at both mmc-next tree and Samsung-SoC tree.
I think this is very inefficient and can conflict to merge.
So remained at least dependency and moved the header file to mmc folder.

And sdhci-s3c changed to use the sdhci-pltfm.c.
There is no reason that didn't use the sdhci-pltfm.c.
If we use the sdhci-pltfm.c,we can easily maintain the common part.

In future, i will work more removing the arch dependency.

This patchset based on mmc-next tree.

Changelog v3:
	- Modify mmc/host/Makefile for sdhci-s3c.c
	- remove unnecessary code

Changelog V2:
	- modified driver/mmc/host/Kconfig
	- Add the comments for s3c64xx
	- based-on latest mmc-tree. 


Jaehoon Chung (4):
  mmc: sdhci-s3c: use the sdhci-pltfm for Samsung-SoC
  ARM: SAMSUNG: move the sdhci header file to driver directory
  mmc: sdhci-s3c: use the sdhci-s3c.h instead of regs-sdhci.h
  ARM: SAMSUNG: move the mmc platdata header file into linux/mmc/

 arch/arm/mach-exynos/setup-sdhci-gpio.c         |    1 -
 arch/arm/mach-s5pc100/setup-sdhci-gpio.c        |    1 -
 arch/arm/mach-s5pv210/setup-sdhci-gpio.c        |    1 -
 arch/arm/plat-samsung/include/plat/regs-sdhci.h |   87 --------
 arch/arm/plat-samsung/include/plat/sdhci.h      |   53 +-----
 drivers/mmc/host/Kconfig                        |   20 +-
 drivers/mmc/host/Makefile                       |    2 +-
 drivers/mmc/host/sdhci-s3c.c                    |  265 ++++++++---------------
 drivers/mmc/host/sdhci-s3c.h                    |   89 ++++++++
 include/linux/mmc/sdhci-s3c.h                   |   84 +++++++
 10 files changed, 273 insertions(+), 330 deletions(-)
 delete mode 100644 arch/arm/plat-samsung/include/plat/regs-sdhci.h
 create mode 100644 drivers/mmc/host/sdhci-s3c.h
 create mode 100644 include/linux/mmc/sdhci-s3c.h

             reply	other threads:[~2012-03-06  6:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  6:17 Jaehoon Chung [this message]
2012-03-06 13:00 ` [PATCH v3 0/4] mmc: sdhci-s3c: use the sdhci-pltfm.c and move the header file Mark Brown
2012-03-06 13:15   ` Heiko Stübner
2012-03-06 14:40     ` Jae hoon Chung
2012-03-06 16:30       ` Mark Brown
2012-03-07  3:03         ` Jaehoon Chung
2012-03-07 18:48           ` Mark Brown
2012-03-08  5:35             ` Jaehoon Chung
2012-03-08 11:01               ` Mark Brown
2012-03-09  1:53                 ` Jaehoon Chung
2012-03-09 11:48                   ` Mark Brown

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=4F55ABF0.1060801@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=cjb@laptop.org \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.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).