AM3517 (Sitara) MMC2 help

DISCUSSION Igor Grinberg 4 participants 9 messages Aug 24, 2010 – Aug 25, 2010

Share & tools

Igor Grinberg

author

2010-08-24 12:42 UTC #0 lore raw

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

Signature · 2 lines

Regards,
Igor.

Laine Walker-Avina

2010-08-25 00:29 UTC #1 lore raw

Quoted 75 lines · Igor Grinberg

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

Quoted 9 lines

--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
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.

Signature · 7 lines

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Laine Walker-Avina

2010-08-25 00:36 UTC #2 lore raw

Quoted 11 lines · Laine Walker-Avina

Quoted 10 lines · Igor Grinberg
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:

Quoted 7 lines

Quoted 7 lines
--------------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?

Quoted 78 lines

Quoted 58 lines
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
Quoted 9 lines
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
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

Signature · 7 lines

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Igor Grinberg

author

2010-08-25 07:57 UTC #3 lore raw

Quoted 19 lines · Laine Walker-Avina

Quoted 11 lines · Laine Walker-Avina
Quoted 10 lines · Igor Grinberg
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:
Quoted 7 lines
Quoted 7 lines
--------------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

Quoted 2 lines

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?

Quoted 79 lines

Quoted 77 lines
Quoted 58 lines
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
Quoted 9 lines
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
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

Signature · 2 lines

Regards,
Igor.

Igor Grinberg

author

2010-08-25 08:12 UTC #4 lore raw

In reply to Laine Walker-Avina

Quoted 80 lines · Laine Walker-Avina

Quoted 79 lines · Igor Grinberg
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.

Quoted 7 lines

Quoted 5 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
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.

Quoted 3 lines

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

Signature · 2 lines

Regards,
Igor.

Igor Grinberg

author

2010-08-25 09:26 UTC #5 lore raw

Quoted 86 lines · Igor Grinberg

Quoted 85 lines · Laine Walker-Avina
Quoted 84 lines · Igor Grinberg
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Quoted 8 lines

Quoted 2 lines
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.
Quoted 3 lines
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?

Signature · 2 lines

Regards,
Igor.

Ashwin Bihari

2010-08-25 13:46 UTC #6 lore raw

In reply to Igor Grinberg

-- Ashwin

Quoted 100 lines · Igor Grinberg

Quoted 80 lines · Laine Walker-Avina
Quoted 79 lines · Igor Grinberg
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.
Quoted 7 lines
Quoted 5 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
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.
Quoted 3 lines
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

Quoted 9 lines

--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Gadiyar, Anand

2010-08-25 13:52 UTC #7 lore raw

Quoted 78 lines · Ashwin Bihari

Quoted 77 lines · Igor Grinberg
Quoted 76 lines · Laine Walker-Avina
Quoted 75 lines · Igor Grinberg
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

...

Quoted 12 lines

Quoted 12 lines
Quoted 2 lines
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.
Quoted 3 lines
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.

...

Quoted 10 lines

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.

Quoted 6 lines

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Ashwin Bihari

2010-08-25 13:58 UTC #8 lore raw

Quoted 36 lines · Anand

Quoted 3 lines · Ashwin Bihari
Quoted 2 lines · Igor Grinberg
Quoted 1 line · Laine Walker-Avina
On Tue, Aug 24, 2010 at 5:42 AM, Igor Grinberg <[email protected]> wrote:
...
Quoted 12 lines
Quoted 12 lines
Quoted 2 lines
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.
Quoted 3 lines
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.
...
Quoted 15 lines
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..

Quoted 9 lines

Quoted 1 line
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html