> -----Original Message-----
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Thursday, May 20, 2010 6:28 AM
> To: Kadiyala, Kishore
> Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; Chikkature 
> Rajashekar, Madhusudhan;
> jarkko.lavi...@nokia.com; r...@arm.linux.org.uk; p...@pwsan.com; Shilimkar, 
> Santosh
> Subject: Re: [PATCH v4 0/5] Adding MMC Support on OMAP4430 SDP
> 
> * kishore kadiyala <kishore.kadiy...@ti.com> [100519 08:39]:
> > >
> > >FYI, the MMC on omap4 is not quite there yet at least
> > >on my board. It mostly detects the card with
> > >omap_4430sdp_defconfig, but fails always unless
> > >CONFIG_RTC_DRV_TWL92330=y.. This is without CONFIG_SMP
> > >as it oopses.
> >
> > Hope you are referring CONFIG_RTC_DRV_TWL92330 to omap3_defconfig
> > and not to omap_4430sdp_defconfig.
> 
> Sorry I meant CONFIG_RTC_DRV_TWL4030 in the omap_4430sdp_defconfig.
> If you take that out, MMC is never detected.
> 
> > With omap_4430sdp_defconfig , I've tested on 4430SDP and Blaze and always
> > Cards on MMC1 & MMC2 gets detected once bootedup.
> 
> Are you able to actually mount root on the MMC with let's say
> current linux-omap master branch?
> 
> > >Also MMC is never detected with omap3_defconfig.
> >
> > With omap3_defconfig  +  disabling "CONFIG_OMAP_RESET_CLOCKS",
> > I've tested on 4430SDP and Blaze and always Cards on MMC1 & MMC2
> > gets detected on bootup.
> 
> That should be fixed so CONFIG_OMAP_RESET_CLOCKS works. Otherwise
> we're relying on some random clocks being enabled.
> 
The fix for this is already in Paul's queue now.

https://patchwork.kernel.org/patch/101094/

Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to