On Mon, Sep 20, 2010 at 9:03 PM, Chris Ball <cjb@xxxxxxxxxx> wrote: > Hi Zhangfei/Saeed, > > On Mon, Sep 20, 2010 at 05:46:02PM +0800, zhangfei gao wrote: >> Hi, Chris, >> >> Here is patch to support pxa168(aspen)/pxa910(ttc)/mmp2, the >> controller follow sdh 3.0. >> Currently verified sd, Micron 16G emmc need some workaround, 8G is OK, >> marvell 8787 would be verified later. >> Help review. > > Could you help me understand how this new driver relates to the Marvell > SoC driver that I merged last week (CONFIG_MMC_SDHCI_MV)? Are the SD > IPs in Dove and MMP2 different enough to warrant a separate driver, or > could support for both be included in sdhci-mv.c? > > If we're going to have multiple drivers for the SD blocks in Armada/PXA, > it at least seems that MMC_SDHCI_MV has been mis-named. Any thoughts? > > Thanks, > > - Chris. > -- > Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> > One Laptop Per Child > Hi, Chris 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. Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
