* AM3517 (Sitara) MMC2 help
@ 2010-08-24 12:42 Igor Grinberg
2010-08-25 0:29 ` Laine Walker-Avina
0 siblings, 1 reply; 9+ messages in thread
From: Igor Grinberg @ 2010-08-24 12:42 UTC (permalink / raw)
To: linux-omap
Hi,
I have am3517 based board and Libertas sdio (4 wires)
wifi connected directly (no transceiver / level shifter) on mmc2
(which is named mmc1 in s/w).
am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
dmesg | grep mmc1 shows:
--------------cut------------------
mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
mmc1: starting CMD52 arg 00000c00 flags 00000195
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
mmc1: starting CMD52 arg 80000c08 flags 00000195
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
mmc1: starting CMD0 arg 00000000 flags 000000c0
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
mmc1: starting CMD8 arg 000001aa flags 000002f5
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
mmc1: starting CMD5 arg 00000000 flags 000002e1
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
mmc1: req failed (CMD5): -110, retrying...
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
mmc1: req failed (CMD5): -110, retrying...
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
mmc1: req failed (CMD5): -110, retrying...
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
mmc1: starting CMD55 arg 00000000 flags 000000f5
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
mmc1: starting CMD55 arg 00000000 flags 000000f5
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
mmc1: starting CMD55 arg 00000000 flags 000000f5
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
mmc1: starting CMD55 arg 00000000 flags 000000f5
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
mmc1: starting CMD1 arg 00000000 flags 000000e1
mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
-------------------cut---------------------
Libertas is powered up and gets reseted properly.
On the oscilloscope, I see some communication going
on the CMD line and stops after some time.
am3517 PSP from TI, does not even registers/enables
the wifi combo found on am3517evm.
Have anybody got the mmc2 working on am3517?
May be with transceiver?
Any help will be appreciated.
Thanks
--
Regards,
Igor.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AM3517 (Sitara) MMC2 help
2010-08-24 12:42 AM3517 (Sitara) MMC2 help Igor Grinberg
@ 2010-08-25 0:29 ` Laine Walker-Avina
2010-08-25 0:36 ` Laine Walker-Avina
2010-08-25 8:12 ` Igor Grinberg
0 siblings, 2 replies; 9+ messages in thread
From: Laine Walker-Avina @ 2010-08-25 0:29 UTC (permalink / raw)
To: Igor Grinberg; +Cc: linux-omap
On Tue, Aug 24, 2010 at 5:42 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
> Hi,
>
> I have am3517 based board and Libertas sdio (4 wires)
> wifi connected directly (no transceiver / level shifter) on mmc2
> (which is named mmc1 in s/w).
>
> am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
>
> dmesg | grep mmc1 shows:
>
> --------------cut------------------
> mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
> mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
> mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
> mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
> mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
> mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
> mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
> mmc1: starting CMD52 arg 00000c00 flags 00000195
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
> mmc1: starting CMD52 arg 80000c08 flags 00000195
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
> mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
> mmc1: starting CMD0 arg 00000000 flags 000000c0
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
> mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
> mmc1: starting CMD8 arg 000001aa flags 000002f5
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
> mmc1: starting CMD5 arg 00000000 flags 000002e1
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> mmc1: req failed (CMD5): -110, retrying...
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> mmc1: req failed (CMD5): -110, retrying...
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> mmc1: req failed (CMD5): -110, retrying...
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
> mmc1: starting CMD55 arg 00000000 flags 000000f5
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> mmc1: starting CMD55 arg 00000000 flags 000000f5
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> mmc1: starting CMD55 arg 00000000 flags 000000f5
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> mmc1: starting CMD55 arg 00000000 flags 000000f5
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> mmc1: starting CMD1 arg 00000000 flags 000000e1
> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
> mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
> -------------------cut---------------------
>
> Libertas is powered up and gets reseted properly.
> On the oscilloscope, I see some communication going
> on the CMD line and stops after some time.
>
> am3517 PSP from TI, does not even registers/enables
> the wifi combo found on am3517evm.
>
> Have anybody got the mmc2 working on am3517?
> May be with transceiver?
>
> Any help will be appreciated.
>
> Thanks
>
> --
> Regards,
> Igor.
>
> --
> 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
>
Make sure the MMC2_CLK pin is muxed as an input so the clock can
feedback to the module. Also, you may need to set
CONTROL_DEVCONF1.MMCSDIO2ADPCLKISEL=1 if that exists on the Sitara. I
had the same problem on the OMAP3x.
--
Laine Walker-Avina
Firmware Engineer
PASCO scientific
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AM3517 (Sitara) MMC2 help
2010-08-25 0:29 ` Laine Walker-Avina
@ 2010-08-25 0:36 ` Laine Walker-Avina
2010-08-25 7:57 ` Igor Grinberg
2010-08-25 8:12 ` Igor Grinberg
1 sibling, 1 reply; 9+ messages in thread
From: Laine Walker-Avina @ 2010-08-25 0:36 UTC (permalink / raw)
To: Igor Grinberg; +Cc: linux-omap
On Tue, Aug 24, 2010 at 5:29 PM, Laine Walker-Avina <lwalkera@ieee.org> wrote:
> On Tue, Aug 24, 2010 at 5:42 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>> Hi,
>>
>> I have am3517 based board and Libertas sdio (4 wires)
>> wifi connected directly (no transceiver / level shifter) on mmc2
>> (which is named mmc1 in s/w).
>>
>> am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
>>
>> dmesg | grep mmc1 shows:
>>
>> --------------cut------------------
>> mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
>> mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
>> mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
>> mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
>> mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
>> mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
Also, shouldn't you setting the mux values for sdmmc2_* not sdmmc1_*
if your chip is on MMC2?
>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>> mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>> mmc1: starting CMD52 arg 00000c00 flags 00000195
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD52 arg 80000c08 flags 00000195
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
>> mmc1: starting CMD0 arg 00000000 flags 000000c0
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
>> mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>> mmc1: starting CMD8 arg 000001aa flags 000002f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
>> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD5 arg 00000000 flags 000002e1
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req failed (CMD5): -110, retrying...
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req failed (CMD5): -110, retrying...
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req failed (CMD5): -110, retrying...
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD1 arg 00000000 flags 000000e1
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
>> mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>> -------------------cut---------------------
>>
>> Libertas is powered up and gets reseted properly.
>> On the oscilloscope, I see some communication going
>> on the CMD line and stops after some time.
>>
>> am3517 PSP from TI, does not even registers/enables
>> the wifi combo found on am3517evm.
>>
>> Have anybody got the mmc2 working on am3517?
>> May be with transceiver?
>>
>> Any help will be appreciated.
>>
>> Thanks
>>
>> --
>> Regards,
>> Igor.
>>
>> --
>> 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
>>
>
> Make sure the MMC2_CLK pin is muxed as an input so the clock can
> feedback to the module. Also, you may need to set
> CONTROL_DEVCONF1.MMCSDIO2ADPCLKISEL=1 if that exists on the Sitara. I
> had the same problem on the OMAP3x.
>
> --
> Laine Walker-Avina
> Firmware Engineer
> PASCO scientific
>
--
Laine Walker-Avina
Firmware Engineer
PASCO scientific
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AM3517 (Sitara) MMC2 help
2010-08-25 0:36 ` Laine Walker-Avina
@ 2010-08-25 7:57 ` Igor Grinberg
0 siblings, 0 replies; 9+ messages in thread
From: Igor Grinberg @ 2010-08-25 7:57 UTC (permalink / raw)
To: Laine Walker-Avina; +Cc: linux-omap
On 08/25/10 03:36, Laine Walker-Avina wrote:
> On Tue, Aug 24, 2010 at 5:29 PM, Laine Walker-Avina <lwalkera@ieee.org> wrote:
>> On Tue, Aug 24, 2010 at 5:42 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>>> Hi,
>>>
>>> I have am3517 based board and Libertas sdio (4 wires)
>>> wifi connected directly (no transceiver / level shifter) on mmc2
>>> (which is named mmc1 in s/w).
>>>
>>> am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
>>>
>>> dmesg | grep mmc1 shows:
>>>
>>> --------------cut------------------
>>> mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
>>> mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
>>> mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
> Also, shouldn't you setting the mux values for sdmmc2_* not sdmmc1_*
> if your chip is on MMC2?
Well, this is left unintentionally, I think I can remove this.
omap2_mmc_mux() in arch/arm/mach-omap2/devices.c
does the proper muxing of the lines according to .wires field
of the platform data. I think, I don't need to do any muxing
for the mmc (4 wires) at all in the board file. Am I right?
>>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>>> mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD52 arg 00000c00 flags 00000195
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
>>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD52 arg 80000c08 flags 00000195
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
>>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD0 arg 00000000 flags 000000c0
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
>>> mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD8 arg 000001aa flags 000002f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
>>> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD5 arg 00000000 flags 000002e1
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD1 arg 00000000 flags 000000e1
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
>>> mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
>>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>>> -------------------cut---------------------
>>>
>>> Libertas is powered up and gets reseted properly.
>>> On the oscilloscope, I see some communication going
>>> on the CMD line and stops after some time.
>>>
>>> am3517 PSP from TI, does not even registers/enables
>>> the wifi combo found on am3517evm.
>>>
>>> Have anybody got the mmc2 working on am3517?
>>> May be with transceiver?
>>>
>>> Any help will be appreciated.
>>>
>>> Thanks
>>>
>>> --
>>> Regards,
>>> Igor.
>>>
>>> --
>>> 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
>>>
>> Make sure the MMC2_CLK pin is muxed as an input so the clock can
>> feedback to the module. Also, you may need to set
>> CONTROL_DEVCONF1.MMCSDIO2ADPCLKISEL=1 if that exists on the Sitara. I
>> had the same problem on the OMAP3x.
>>
>> --
>> Laine Walker-Avina
>> Firmware Engineer
>> PASCO scientific
>>
>
>
--
Regards,
Igor.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AM3517 (Sitara) MMC2 help
2010-08-25 0:29 ` Laine Walker-Avina
2010-08-25 0:36 ` Laine Walker-Avina
@ 2010-08-25 8:12 ` Igor Grinberg
2010-08-25 9:26 ` Igor Grinberg
2010-08-25 13:46 ` Ashwin Bihari
1 sibling, 2 replies; 9+ messages in thread
From: Igor Grinberg @ 2010-08-25 8:12 UTC (permalink / raw)
To: Laine Walker-Avina; +Cc: linux-omap
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:
>> Hi,
>>
>> I have am3517 based board and Libertas sdio (4 wires)
>> wifi connected directly (no transceiver / level shifter) on mmc2
>> (which is named mmc1 in s/w).
>>
>> am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
>>
>> dmesg | grep mmc1 shows:
>>
>> --------------cut------------------
>> mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
>> mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
>> mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
>> mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
>> mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
>> mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>> mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>> mmc1: starting CMD52 arg 00000c00 flags 00000195
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD52 arg 80000c08 flags 00000195
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
>> mmc1: starting CMD0 arg 00000000 flags 000000c0
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
>> mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>> mmc1: starting CMD8 arg 000001aa flags 000002f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
>> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD5 arg 00000000 flags 000002e1
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req failed (CMD5): -110, retrying...
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req failed (CMD5): -110, retrying...
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req failed (CMD5): -110, retrying...
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>> mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>> mmc1: starting CMD1 arg 00000000 flags 000000e1
>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
>> mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>> -------------------cut---------------------
>>
>> Libertas is powered up and gets reseted properly.
>> On the oscilloscope, I see some communication going
>> on the CMD line and stops after some time.
>>
>> am3517 PSP from TI, does not even registers/enables
>> the wifi combo found on am3517evm.
>>
>> Have anybody got the mmc2 working on am3517?
>> May be with transceiver?
>>
>> Any help will be appreciated.
>>
>> Thanks
>>
>> --
>> Regards,
>> Igor.
>>
>> --
>> 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
>>
> 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.
Thanks
--
Regards,
Igor.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AM3517 (Sitara) MMC2 help
2010-08-25 8:12 ` Igor Grinberg
@ 2010-08-25 9:26 ` Igor Grinberg
2010-08-25 13:46 ` Ashwin Bihari
1 sibling, 0 replies; 9+ messages in thread
From: Igor Grinberg @ 2010-08-25 9:26 UTC (permalink / raw)
To: Laine Walker-Avina; +Cc: linux-omap
On 08/25/10 11:12, Igor Grinberg 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:
>>> Hi,
>>>
>>> I have am3517 based board and Libertas sdio (4 wires)
>>> wifi connected directly (no transceiver / level shifter) on mmc2
>>> (which is named mmc1 in s/w).
>>>
>>> am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
>>>
>>> dmesg | grep mmc1 shows:
>>>
>>> --------------cut------------------
>>> mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
>>> mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
>>> mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
>>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>>> mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD52 arg 00000c00 flags 00000195
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
>>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD52 arg 80000c08 flags 00000195
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
>>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD0 arg 00000000 flags 000000c0
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
>>> mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD8 arg 000001aa flags 000002f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
>>> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD5 arg 00000000 flags 000002e1
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD1 arg 00000000 flags 000000e1
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
>>> mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
>>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>>> -------------------cut---------------------
>>>
>>> Libertas is powered up and gets reseted properly.
>>> On the oscilloscope, I see some communication going
>>> on the CMD line and stops after some time.
>>>
>>> am3517 PSP from TI, does not even registers/enables
>>> the wifi combo found on am3517evm.
>>>
>>> Have anybody got the mmc2 working on am3517?
>>> May be with transceiver?
>>>
>>> Any help will be appreciated.
>>>
>>> Thanks
>>>
>>> --
>>> Regards,
>>> Igor.
>>>
>>> --
>>> 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
>>>
>> 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.
Nope... this does not help.
Also, Stanley has restricted the above setting to non-am3517 cpus
in commit 03e7e170d6fdc5b6f75d1ab2cc1a6cb4f2b6b8c4
Any other suggestions?
Stanley, can you help us with this?
--
Regards,
Igor.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AM3517 (Sitara) MMC2 help
2010-08-25 8:12 ` Igor Grinberg
2010-08-25 9:26 ` Igor Grinberg
@ 2010-08-25 13:46 ` Ashwin Bihari
2010-08-25 13:51 ` Gadiyar, Anand
1 sibling, 1 reply; 9+ messages in thread
From: Ashwin Bihari @ 2010-08-25 13:46 UTC (permalink / raw)
To: Igor Grinberg; +Cc: Laine Walker-Avina, linux-omap
-- Ashwin
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:
>>> Hi,
>>>
>>> I have am3517 based board and Libertas sdio (4 wires)
>>> wifi connected directly (no transceiver / level shifter) on mmc2
>>> (which is named mmc1 in s/w).
>>>
>>> am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
>>>
>>> dmesg | grep mmc1 shows:
>>>
>>> --------------cut------------------
>>> mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
>>> mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
>>> mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
>>> mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
>>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>>> mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD52 arg 00000c00 flags 00000195
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
>>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD52 arg 80000c08 flags 00000195
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
>>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD0 arg 00000000 flags 000000c0
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
>>> mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
>>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
>>> mmc1: starting CMD8 arg 000001aa flags 000002f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
>>> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD5 arg 00000000 flags 000002e1
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req failed (CMD5): -110, retrying...
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
>>> mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD55 arg 00000000 flags 000000f5
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
>>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
>>> mmc1: starting CMD1 arg 00000000 flags 000000e1
>>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
>>> mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
>>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
>>> -------------------cut---------------------
>>>
>>> Libertas is powered up and gets reseted properly.
>>> On the oscilloscope, I see some communication going
>>> on the CMD line and stops after some time.
>>>
>>> am3517 PSP from TI, does not even registers/enables
>>> the wifi combo found on am3517evm.
>>>
>>> Have anybody got the mmc2 working on am3517?
>>> May be with transceiver?
>>>
>>> Any help will be appreciated.
>>>
>>> Thanks
>>>
>>> --
>>> Regards,
>>> Igor.
>>>
>>> --
>>> 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
>>>
>> 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.
>
> Thanks
>
> --
> Regards,
> Igor.
>
> --
> 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
>
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
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: AM3517 (Sitara) MMC2 help
2010-08-25 13:46 ` Ashwin Bihari
@ 2010-08-25 13:51 ` Gadiyar, Anand
2010-08-25 13:58 ` Ashwin Bihari
0 siblings, 1 reply; 9+ messages in thread
From: Gadiyar, Anand @ 2010-08-25 13:51 UTC (permalink / raw)
To: Ashwin Bihari, Igor Grinberg; +Cc: Laine Walker-Avina, linux-omap
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:
> >>> Hi,
> >>>
> >>> I have am3517 based board and Libertas sdio (4 wires)
> >>> wifi connected directly (no transceiver / level shifter) on mmc2
> >>> (which is named mmc1 in s/w).
> >>>
> >>> am3517 is configured (h/w) for 3.3V and so is Libertas wifi.
> >>>
> >>> dmesg | grep mmc1 shows:
> >>>
> >>> --------------cut------------------
> >>> mux: Setting signal sdmmc1_clk.sdmmc1_clk 0x0000 -> 0x0118
> >>> mux: Setting signal sdmmc1_cmd.sdmmc1_cmd 0x0000 -> 0x0118
> >>> mux: Setting signal sdmmc1_dat0.sdmmc1_dat0 0x0100 -> 0x0118
> >>> mux: Setting signal sdmmc1_dat1.sdmmc1_dat1 0x0100 -> 0x0118
> >>> mux: Setting signal sdmmc1_dat2.sdmmc1_dat2 0x0100 -> 0x0118
> >>> mux: Setting signal sdmmc1_dat3.sdmmc1_dat3 0x0100 -> 0x0118
> >>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
> >>> mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0
> >>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
> >>> mmc1: starting CMD52 arg 00000c00 flags 00000195
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x00000c00
> >>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: starting CMD52 arg 80000c08 flags 00000195
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD52, argument 0x80000c08
> >>> mmc1: req done (CMD52): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0
> >>> mmc1: starting CMD0 arg 00000000 flags 000000c0
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD0, argument 0x00000000
> >>> mmc1: req done (CMD0): 0: 00000000 00000000 00000000 00000000
> >>> mmc1: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0
> >>> mmc1: starting CMD8 arg 000001aa flags 000002f5
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD8, argument 0x000001aa
> >>> mmc1: req done (CMD8): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: starting CMD5 arg 00000000 flags 000002e1
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> >>> mmc1: req failed (CMD5): -110, retrying...
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> >>> mmc1: req failed (CMD5): -110, retrying...
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> >>> mmc1: req failed (CMD5): -110, retrying...
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD5, argument 0x00000000
> >>> mmc1: req done (CMD5): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: starting CMD55 arg 00000000 flags 000000f5
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> >>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: starting CMD55 arg 00000000 flags 000000f5
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> >>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: starting CMD55 arg 00000000 flags 000000f5
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> >>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: starting CMD55 arg 00000000 flags 000000f5
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD55, argument 0x00000000
> >>> mmc1: req done (CMD55): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: starting CMD1 arg 00000000 flags 000000e1
> >>> mmci-omap-hs mmci-omap-hs.1: mmc1: CMD1, argument 0x00000000
> >>> mmc1: req done (CMD1): -110: 00000000 00000000 00000000 00000000
> >>> mmc1: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
> >>> -------------------cut---------------------
> >>>
> >>> Libertas is powered up and gets reseted properly.
> >>> On the oscilloscope, I see some communication going
> >>> on the CMD line and stops after some time.
> >>>
> >>> am3517 PSP from TI, does not even registers/enables
> >>> the wifi combo found on am3517evm.
> >>>
> >>> Have anybody got the mmc2 working on am3517?
> >>> May be with transceiver?
> >>>
> >>> Any help will be appreciated.
> >>>
> >>> Thanks
> >>>
...
> >> 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
--
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AM3517 (Sitara) MMC2 help
2010-08-25 13:51 ` Gadiyar, Anand
@ 2010-08-25 13:58 ` Ashwin Bihari
0 siblings, 0 replies; 9+ messages in thread
From: Ashwin Bihari @ 2010-08-25 13:58 UTC (permalink / raw)
To: Gadiyar, Anand; +Cc: Igor Grinberg, Laine Walker-Avina, linux-omap
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
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2010-08-25 13:58 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-08-24 12:42 AM3517 (Sitara) MMC2 help Igor Grinberg
2010-08-25 0:29 ` Laine Walker-Avina
2010-08-25 0:36 ` Laine Walker-Avina
2010-08-25 7:57 ` Igor Grinberg
2010-08-25 8:12 ` Igor Grinberg
2010-08-25 9:26 ` Igor Grinberg
2010-08-25 13:46 ` Ashwin Bihari
2010-08-25 13:51 ` Gadiyar, Anand
2010-08-25 13:58 ` Ashwin Bihari
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.