From: "kishore kadiyala" <kishore.kadiyala@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
madhu.cr@ti.com, jarkko.lavinen@nokia.com, rmk@arm.linux.org.uk,
paul@pwsan.com, santosh.shilimkar@ti.com
Subject: Re: [PATCH v4 0/5] Adding MMC Support on OMAP4430 SDP
Date: Thu, 20 May 2010 23:01:06 +0530 [thread overview]
Message-ID: <087101caf842$3d7aabe0$LocalHost@wipblrx0099945A> (raw)
In-Reply-To: 20100520005800.GK5818@atomide.com
----- Original Message -----
From: "Tony Lindgren" <tony@atomide.com>
To: "kishore kadiyala" <kishore.kadiyala@ti.com>
Cc: <linux-mmc@vger.kernel.org>; <linux-omap@vger.kernel.org>;
<madhu.cr@ti.com>; <jarkko.lavinen@nokia.com>; <rmk@arm.linux.org.uk>;
<paul@pwsan.com>; <santosh.shilimkar@ti.com>
Sent: Thursday, May 20, 2010 6:28 AM
Subject: Re: [PATCH v4 0/5] Adding MMC Support on OMAP4430 SDP
>* kishore kadiyala <kishore.kadiyala@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.
Even disabling CONFIG_RTC_DRV_TWL4030 in omap_4430sdp_defconfig, card gets
detected
always on booting up.
>
>> 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?
Yes I booted with file system mounted on card present on MMC1,
and I can see cards getting detected properly and also filesystem gettting
mounted.
Here are the boot logs with "CONFIG_RTC_DRV_TWL4030 " disabled and
filesystem
on ext2 partition of card present on MMC1
http://pastebin.mozilla.org/726228
Regards,
Kishore
>
>> >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.
>
>> >I've piled all these patches into linux-omap master branch
>> >for easy testing. Let me know if I missed some patch.
>>
>> Following is the commit ID :1674c0ceabfb7726246989874bb4da7bcb55ea89
>> used on LO master branch for testing. All the patches were merged.
>
> OK, thanks for checking that.
>
> Regards,
>
> Tony
>
prev parent reply other threads:[~2010-05-20 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 18:20 [PATCH v4 0/5] Adding MMC Support on OMAP4430 SDP kishore kadiyala
2010-05-18 2:50 ` Tony Lindgren
2010-05-19 0:09 ` Tony Lindgren
2010-05-19 15:25 ` Madhusudhan
2010-05-19 15:44 ` kishore kadiyala
2010-05-20 0:58 ` Tony Lindgren
2010-05-20 5:02 ` Shilimkar, Santosh
2010-05-20 17:31 ` kishore kadiyala [this message]
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='087101caf842$3d7aabe0$LocalHost@wipblrx0099945A' \
--to=kishore.kadiyala@ti.com \
--cc=jarkko.lavinen@nokia.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=paul@pwsan.com \
--cc=rmk@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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