[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <FCBE654890C0334289D0AD3AF4EF009FD18EE74AE9@IL-MB01.marvell.com>
Date: Wed, 15 Sep 2010 13:29:11 +0300
From: Saeed Bishara <saeed@...vell.com>
To: Haojian Zhuang <haojian.zhuang@...il.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC: Chris Ball <cjb@...top.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] mmc: Add architecture dependency for Marvell SoC
controller
>-----Original Message-----
>From: Haojian Zhuang [mailto:haojian.zhuang@...il.com]
>Sent: Wednesday, September 15, 2010 1:21 PM
>To: Saeed Bishara
>Cc: Mark Brown; Chris Ball; Andrew Morton;
>linux-mmc@...r.kernel.org; linux-kernel@...r.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@...vell.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--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists