All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: zhangfei gao <zhangfei.gao@gmail.com>
Cc: linux-mmc@vger.kernel.org, Saeed Bishara <saeed@marvell.com>,
	Kyungmin Park <kmpark@infradead.org>,
	eric.y.miao@gmail.com, Haojian Zhuang <haojian.zhuang@gmail.com>
Subject: Re: [PATCH] add support PXA168/PXA910/MMP2 SD Host Controller
Date: Wed, 22 Sep 2010 03:27:22 +0100	[thread overview]
Message-ID: <20100922022721.GB3821@void.printf.net> (raw)
In-Reply-To: <AANLkTi=Rwj7hDfDxKqLNwyparxWv3RvQ2HJvo1qbJVe2@mail.gmail.com>

Hi,

On Mon, Sep 20, 2010 at 11:16:18PM -0400, zhangfei gao wrote:
> We have considered using the same driver with dove once saeed push the
> driver, but at last we decide to use seperate driver to easy
> maintaince and further extension.
> 
> There are different IP developed by different group between Dove and
> pxa168/pxa910/mmp2, and would be more and more different.
> The pxa serious ip is follow sdh spec 3.0, and support sd 3.0 and emmc
> 4.4, which need ddr50 and 1.8v requirement, the limitation is adma
> still has some issue and in fixing.
> Still some private register with differnt address, such as power
> control, clock timming tunning and etc.
> 
> The dove ip is follow sdh spec 2.0, and it has own limitation, such as
> 1.8v may not be supported.
> 
> In a word, they are differnt ip, and it is reasonable to use seprate driver.

Okay.  If we're going to have two different MV_SDHCI drivers, please
coordinate to have different Kconfig entries for the Dove/MMP and MMP2
drivers that correctly identify which SoCs are supported by each, and
resend.  Neither driver should be called CONFIG_MV_SDHCI, since there
will be no one driver for all MV_SDHCIs.

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2010-09-22  2:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20  9:46 [PATCH] add support PXA168/PXA910/MMP2 SD Host Controller zhangfei gao
2010-09-20  9:50 ` Wolfram Sang
2010-09-20 12:09   ` zhangfei gao
2010-09-20 13:10     ` Wolfram Sang
2010-09-21  8:24       ` zhangfei gao
2010-09-21 10:11         ` Wolfram Sang
2010-09-21 10:18           ` Eric Miao
2010-09-21 16:18           ` Chris Ball
2010-09-21  1:03 ` Chris Ball
2010-09-21  3:16   ` zhangfei gao
2010-09-22  2:27     ` Chris Ball [this message]
2010-09-21  9:42 ` claud yu
2010-09-26  9:05   ` zhangfei gao

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=20100922022721.GB3821@void.printf.net \
    --to=cjb@laptop.org \
    --cc=eric.y.miao@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=kmpark@infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=saeed@marvell.com \
    --cc=zhangfei.gao@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.