From: zhangfei gao <zhangfei.gao@gmail.com>
To: Chris Ball <cjb@laptop.org>
Cc: Philip Rakity <prakity@marvell.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Jun Nie <njun@marvell.com>, Raymond Wu <xywu@marvell.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH 2/2] sdhci-pxa: add call back interface to share sdhci-pxa
Date: Sat, 14 May 2011 13:11:44 +0800 [thread overview]
Message-ID: <BANLkTinOaVziLLun7RyNVCFx=_=DcVXomA@mail.gmail.com> (raw)
In-Reply-To: <m3ei42vhir.fsf@pullcord.laptop.org>
On Fri, May 13, 2011 at 9:47 PM, Chris Ball <cjb@laptop.org> wrote:
> Hi,
>
> On Thu, May 12 2011, Philip Rakity wrote:
>> All other platform specific code is in the host/ directory.
>>
>> This moves it to arch/arm
>>
>> If that is the direction the group wants to go in --> then the patch
>> is fine provided the mmc group can review the patches. Otherwise they
>> are handled by the arm maintainer.
>
> Thanks. Wolfram, do you have any ideas on what the best design is for
> these SoC-specific changes to sdhci-pxa?
>
> - Chris.
The code in arch/arm is
1. Accessing private register, take pxa910 and mmp2 we want to support
as example, there are several private registers differece, though they
are same ip, with same issues and quirk.
2. Handle platform difference, for example, mmp2 used in two different
platform, one use wp pin, the other does not.
Thanks
> --
> Chris Ball <cjb@laptop.org> <http://printf.net/>
> One Laptop Per Child
>
next prev parent reply other threads:[~2011-05-14 5:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 3:57 [PATCH 2/2] sdhci-pxa: add call back interface to share sdhci-pxa zhangfei gao
2011-05-12 22:25 ` Chris Ball
2011-05-12 22:58 ` Philip Rakity
2011-05-13 13:47 ` Chris Ball
2011-05-14 5:11 ` zhangfei gao [this message]
2011-05-14 17:01 ` Philip Rakity
2011-05-15 21:32 ` Philip Rakity
2011-05-16 6:26 ` zhangfei gao
2011-05-16 13:51 ` Philip Rakity
2011-05-17 2:02 ` zhangfei gao
2011-05-17 4:27 ` Philip Rakity
2011-05-17 5:39 ` zhangfei gao
2011-05-18 20:38 ` Arnd Bergmann
2011-05-19 11:34 ` zhangfei gao
2011-05-19 13:04 ` Arnd Bergmann
2011-05-23 13:13 ` zhangfei gao
2011-05-23 14:56 ` Arnd Bergmann
2011-05-19 18:24 ` Nicolas Pitre
2011-05-21 1:50 ` zhangfei gao
-- strict thread matches above, loose matches on Subject: below --
2010-12-03 6:31 [PATCH 2/2] sdhci-pxa " zhangfei gao
2010-12-07 5:56 ` Raymond Wu
2010-12-07 15:26 ` Philip Rakity
2010-12-07 15:38 ` zhangfei gao
2010-12-07 15:48 ` Philip Rakity
2010-12-07 15:58 ` zhangfei gao
2010-12-27 7:09 ` 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='BANLkTinOaVziLLun7RyNVCFx=_=DcVXomA@mail.gmail.com' \
--to=zhangfei.gao@gmail.com \
--cc=cjb@laptop.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=njun@marvell.com \
--cc=prakity@marvell.com \
--cc=w.sang@pengutronix.de \
--cc=xywu@marvell.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 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).