MMC2 support in linux-omap-2.6.27 (omap1)

MMC2 support in linux-omap-2.6.27 (omap1)

[twebb]

I'm currently using linux-omap-2.6.27 (tag=omap1) and trying to add
MMC2 support.  I've back ported what I think I need from various files
inn l-o-2.6.28-omap1.  I will eventually move to 2.6.28-omap1 but for
now am trying to get it working on 2.6.27.

Traces show that all looks good up until first command is issued, then
nothing seems to happen.  STAT reg shows 0, don't see clock or cmd
activity.  MMC1 is working fine with an SD card; MMC2 is connected to
eMMC flash.  Seems like I'm missing something basic like a clock or
enable, though I've confirmed ICLK and FCLK are enabled.  Any ideas?

Thanks,
twebb

Re: MMC2 support in linux-omap-2.6.27 (omap1)

[twebb]

On Wed, Mar 25, 2009 at 10:13 AM, twebb <taliaferro62@gmail.com> wrote:
> I'm currently using linux-omap-2.6.27 (tag=omap1) and trying to add
> MMC2 support.  I've back ported what I think I need from various files
> inn l-o-2.6.28-omap1.  I will eventually move to 2.6.28-omap1 but for
> now am trying to get it working on 2.6.27.
>
> Traces show that all looks good up until first command is issued, then
> nothing seems to happen.  STAT reg shows 0, don't see clock or cmd
> activity.  MMC1 is working fine with an SD card; MMC2 is connected to
> eMMC flash.  Seems like I'm missing something basic like a clock or
> enable, though I've confirmed ICLK and FCLK are enabled.  Any ideas?
>
> Thanks,
> twebb
>

I found at least part of my problem.  SDVS field of HCTL was being set
to 0x7 (3.3V) instead of 0x5 (1.8V), and apparently MMC2 must be set
for 0x5.
--
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

Re: MMC2 support in linux-omap-2.6.27 (omap1)

[Adrian Hunter]

twebb wrote:
> On Wed, Mar 25, 2009 at 10:13 AM, twebb <taliaferro62@gmail.com> wrote:
>> I'm currently using linux-omap-2.6.27 (tag=omap1) and trying to add
>> MMC2 support.  I've back ported what I think I need from various files
>> inn l-o-2.6.28-omap1.  I will eventually move to 2.6.28-omap1 but for
>> now am trying to get it working on 2.6.27.
>>
>> Traces show that all looks good up until first command is issued, then
>> nothing seems to happen.  STAT reg shows 0, don't see clock or cmd
>> activity.  MMC1 is working fine with an SD card; MMC2 is connected to
>> eMMC flash.  Seems like I'm missing something basic like a clock or
>> enable, though I've confirmed ICLK and FCLK are enabled.  Any ideas?
>>
>> Thanks,
>> twebb
>>
> 
> I found at least part of my problem.  SDVS field of HCTL was being set
> to 0x7 (3.3V) instead of 0x5 (1.8V), and apparently MMC2 must be set
> for 0x5.
> --
> 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
> 

The most up to date omap_hsmmc.c is here:

http://git.kernel.org/?p=linux/kernel/git/drzeus/mmc.git;a=blob;f=drivers/mmc/host/omap_hsmmc.c;h=488f222054f8a1493142d02da526c951def5ddfe;hb=next

That includes the 10 patches on LKML except number 8

Re: MMC2 support in linux-omap-2.6.27 (omap1)

[twebb]

On Thu, Mar 26, 2009 at 6:13 AM, Shankar Ganesh
<shankarganeshk@gmail.com> wrote:
>
> On Thu, Mar 26, 2009 at 2:16 PM, Adrian Hunter <adrian.hunter@nokia.com>
> wrote:
>>
>> twebb wrote:
>>>
>>> On Wed, Mar 25, 2009 at 10:13 AM, twebb <taliaferro62@gmail.com> wrote:
>>>>
>>>> I'm currently using linux-omap-2.6.27 (tag=omap1) and trying to add
>>>> MMC2 support.  I've back ported what I think I need from various files
>>>> inn l-o-2.6.28-omap1.  I will eventually move to 2.6.28-omap1 but for
>>>> now am trying to get it working on 2.6.27.
>>>>
>>>> Traces show that all looks good up until first command is issued, then
>>>> nothing seems to happen.  STAT reg shows 0, don't see clock or cmd
>>>> activity.  MMC1 is working fine with an SD card; MMC2 is connected to
>>>> eMMC flash.  Seems like I'm missing something basic like a clock or
>>>> enable, though I've confirmed ICLK and FCLK are enabled.  Any ideas?
>>>>
>>>> Thanks,
>>>> twebb
>>>>
>>>
>>> I found at least part of my problem.  SDVS field of HCTL was being set
>>> to 0x7 (3.3V) instead of 0x5 (1.8V), and apparently MMC2 must be set
>>> for 0x5.
>>> --
>>> 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
>>>
>>
>> The most up to date omap_hsmmc.c is here:
>>
>>
>> http://git.kernel.org/?p=linux/kernel/git/drzeus/mmc.git;a=blob;f=drivers/mmc/host/omap_hsmmc.c;h=488f222054f8a1493142d02da526c951def5ddfe;hb=next
>>
>> That includes the 10 patches on LKML except number 8
>>
>> --
>> 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
>
>
> Refer  http://git.omapzoom.com/?p=repo/omapkernel.git;a=summary  has working
> MMC2 code. Also this version detects eMMC on MMC2
>

I'm having difficulty detecting eMMC flash on MMC2.  I ported in the
code from the git, and most everything looks good.  However, it always
fails detecting the eMMC with a timeout.  If I handpoke commands to
the eMMC I see the same thing - even with the most basic commands.  I
see CLK and CMDs going to the eMMC, but never see any responses on the
CMD line from the eMMC.  Any ideas what I might be doing wrong?  (I do
have an SD card working fine on MMC1.  Also, the eMMC flash is
hardwired with power and has no CardDetect or WriteProtect logic - so
none of that should be an issue.)

Help,
twebb

(sorry for double posting)
--
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