All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saeed Bishara <saeed@marvell.com>
To: Haojian Zhuang <haojian.zhuang@gmail.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Chris Ball <cjb@laptop.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] mmc: Add architecture dependency for Marvell SoC controller
Date: Wed, 15 Sep 2010 13:29:11 +0300	[thread overview]
Message-ID: <FCBE654890C0334289D0AD3AF4EF009FD18EE74AE9@IL-MB01.marvell.com> (raw)
In-Reply-To: <AANLkTi=fsntfyAoFygrTrksVARvQpuxie6tFxCcuLtVR@mail.gmail.com>

 

>-----Original Message-----
>From: Haojian Zhuang [mailto:haojian.zhuang@gmail.com] 
>Sent: Wednesday, September 15, 2010 1:21 PM
>To: Saeed Bishara
>Cc: Mark Brown; Chris Ball; Andrew Morton; 
>linux-mmc@vger.kernel.org; linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] mmc: Add architecture dependency for 
>Marvell SoC controller
>
>On Wed, Sep 15, 2010 at 6:06 PM, Saeed Bishara 
><saeed@marvell.com> wrote:
>>
>>>Which CPUs does the driver actually support?  The Kconfig and
>>>commit log
>>>just say "Marvell" so I went for the conservative option and included
>>>all Marvell CPUs I was aware of.
>> The Marvell Dove SoC includes this device, this SoC defined 
>by ARCH_DOVE
>> I guess it found also only on mmp (defined by ARCH_MMP), 
>Haojian, can you confirm?
>> saeed
>
>As I know, MG1 is also using this IP. Although MG1 isn't supported in
>mainline, it's planned to be added into ARCH_PXA or one new ARCH. So
>PLAT_PXA is preferred.
I think (ARCH_DOVE || ARCH_MMP) is prefered, when MG1 gets added to mainline, then we will add that new ARCH.

saeed

  reply	other threads:[~2010-09-15 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13  8:24 [PATCH] mmc: Add architecture dependency for Marvell SoC controller Mark Brown
2010-09-13 10:48 ` Arnd Bergmann
2010-09-13 12:02   ` Mark Brown
2010-09-14 19:05 ` Chris Ball
2010-09-15  9:40   ` Mark Brown
2010-09-15  9:55     ` Saeed Bishara
2010-09-15 11:00       ` Mark Brown
2010-09-15 10:06         ` Saeed Bishara
2010-09-15 11:20           ` Haojian Zhuang
2010-09-15 10:29             ` Saeed Bishara [this message]
2010-09-15 11:59               ` Haojian Zhuang
2010-09-15 20:59               ` Chris Ball

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=FCBE654890C0334289D0AD3AF4EF009FD18EE74AE9@IL-MB01.marvell.com \
    --to=saeed@marvell.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cjb@laptop.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@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 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.