Re: AM3517 (Sitara) MMC2 help

[Ashwin Bihari <abihari@gmail.com>]

On Wed, Aug 25, 2010 at 9:51 AM, Gadiyar, Anand <gadiyar@ti.com> wrote:
> Ashwin Bihari wrote:
>> On Wed, Aug 25, 2010 at 4:12 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>> >  On 08/25/10 03:29, Laine Walker-Avina wrote:
>> >> On Tue, Aug 24, 2010 at 5:42 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
> ...
>
>> >> Make sure the MMC2_CLK pin is muxed as an input so the clock can
>> >> feedback to the module.
>> >
>> > omap2_mmc_mux() in arch/arm/mach-omap2/devices.c is handling this
>> > and I think properly or else any omap will fail using the mmc2.
>> >
>> >> Also, you may need to set
>> >> CONTROL_DEVCONF1.MMCSDIO2ADPCLKISEL=1 if that exists on the Sitara. I
>> >> had the same problem on the OMAP3x.
>> >
>> > I will try that.
>> >
>
> ...
>
>> I've got this exact same problem on a OMAP35x based board. We have
>> MMC1 connected to a SD card cage and MMC2 connected to an eMMC. I can
>> detect an inserted SD card and eMMC during boot up, but if I suspend
>> and resume the device, I get a ton of timeout errors on MMC1 (the SD
>> slot) and the RFS that's being used from it ends up having lots of
>> EXT3 journal errors and ends up hosing itself..
>>
>> I've confirmed that the CONTROL_DEVCONF1.MMCSDIO2ADPCLKISEL is set to
>> 1 as well and that doesn't affect any change.
>>
>> I was using a 2.6.29 Kernel on this board before and it had no
>> problems, I then jumped to 2.6.32 and this problem appeared. I'm now
>> running the latest linux-next (2.6.35) Kernel and it also presents the
>> problem..
>>
>> Any guidance would be appreciated..
>
> Ashwin,
>
> I'm not sure your problem is the same as the one originally posted.
> Do you have CONFIG_MMC_UNSAFE_RESUME enabled?
>
> - Anand
>

Anand,

Yup, have MMC_UNSAFE_RESUME set. I'm actually using the
"omap3_defconfig" to build my Kernel..

CONFIG_MMC=y
CONFIG_MMC_DEBUG=y
CONFIG_MMC_UNSAFE_RESUME=y
# MMC/SD/SDIO Card Drivers
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_MMC_TEST is not set
# MMC/SD/SDIO Host Controller Drivers
# CONFIG_MMC_SDHCI is not set
CONFIG_MMC_OMAP=y
CONFIG_MMC_OMAP_HS=y
# CONFIG_MMC_SPI is not set

The interesting thing is that enabling MMC2 causes me issues on MMC1
though I'm not doing anything on MMC2's eMMC apart from discovering
it..

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