ZOOM1 SDP2430: MMC/SDIO: doesn't work at all

[Dmitriy Chumak]

Hi,

I have a Zoom1 (3430 LDP) and SDP2430 devices.

I work on SDIO driver.

On both devices I have problems with SDIO using community kernels:

Zoom1:
--

git://git.omapzoom.org/repo/omapkernel.git

$ uname -a
Linux OMAP3430LAB 2.6.27.10-omap1-00207-g26d16da #1 Mon Mar 2 15:50:14 EET 
2009 armv7l unknown

To build a kernel I've used omap_ldp_defconfig

On kernel boot I get the following:

7mmc0: clock 40Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
7mmc0: clock 40Hz busmode 1 powermode 2 cs 1 Vdd 21 width 0 timing 0
7mmc0: starting CMD0 arg  flags 00c0
7mmci-omap mmci-omap.0: mmc0: CMD0, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 1
7mmc0: req done (CMD0): 0:    
7mmc0: clock 40Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
7mmc0: starting CMD8 arg 01aa flags 02f5
7mmci-omap mmci-omap.0: mmc0: CMD8, argument 0x01aa
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req done (CMD8): -110:    
7mmc0: starting CMD5 arg  flags 02e1
7mmci-omap mmci-omap.0: mmc0: CMD5, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req failed (CMD5): -110, retrying...
7mmci-omap mmci-omap.0: mmc0: CMD5, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req failed (CMD5): -110, retrying...
7mmci-omap mmci-omap.0: mmc0: CMD5, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req failed (CMD5): -110, retrying...
7mmci-omap mmci-omap.0: mmc0: CMD5, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req done (CMD5): -110:    
7mmc0: starting CMD55 arg  flags 00f5
7mmci-omap mmci-omap.0: mmc0: CMD55, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req done (CMD55): -110:    
7mmc0: starting CMD55 arg  flags 00f5
7mmci-omap mmci-omap.0: mmc0: CMD55, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req done (CMD55): -110:    
7mmc0: starting CMD55 arg  flags 00f5
7mmci-omap mmci-omap.0: mmc0: CMD55, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req done (CMD55): -110:    
7mmc0: starting CMD55 arg  flags 00f5
7mmci-omap mmci-omap.0: mmc0: CMD55, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req done (CMD55): -110:    
7mmc0: starting CMD1 arg  flags 00e1
7mmci-omap mmci-omap.0: mmc0: CMD1, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 : ERRI CTO
7mmc0: req done (CMD1): -110:    
7mmc0: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0


When I insert SDIO card:


7mmc0: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 21 width 0 timing 0
mmc0: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 21 width 0 timing 0
7mmc0: clock 40Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
mmc0: clock 40Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
7mmc0: clock 40Hz busmode 1 powermode 2 cs 1 Vdd 21 width 0 timing 0
mmc0: clock 40Hz busmode 1 powermode 2 cs 1 Vdd 21 width 0 timing 0
7mmc0: starting CMD0 arg  flags 00c0
mmc0: starting CMD0 arg  flags 00c0
7mmci-omap mmci-omap.0: mmc0: CMD0, argument 0x
mmci-omap mmci-omap.0: mmc0: CMD0, argument 0x
7mmci-omap mmci-omap.0: IRQ Status is 1
mmci-omap mmci-omap.0: IRQ Status is 1
7mmc0: req done (CMD0): 0:    
mmc0: req done (CMD0): 0:    
7mmc0: clock 40Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
mmc0: clock 40Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
7mmc0: starting CMD8 arg 01aa flags 02f5
mmc0: starting CMD8 arg 01aa flags 02f5
7mmci-omap mmci-omap.0: mmc0: CMD8, argument 0x01aa
mmci-omap mmci-omap.0: mmc0: CMD8, argument 0x01aa
7mmci-omap mmci-omap.0: IRQ Status is 18000
mmci-omap mmci-omap.0: IRQ Status is 18000
7mmci-omap mmci-omap.0: MMC IRQ 0x18000 :mmci-omap mmci-omap.0: MMC IRQ 
0x18000 : ERRI ERRI CTO CTO

7mmc0: req done (CMD8): -110:    
mmc0: req done (CMD8): -110:    
7mmc0: starting CMD5 arg 

sdio_writesb doesn't transfer data

[Dmitriy Chumak]

hi *

I have a problem with sdio_writesb. When I call it I get no error in return 
code, but in function mmc_omap_irq (from drivers/mmc/host/omap_hsmmc.c) I get 
status 0x11. It means CC | DDIR. And because there is no TC in status, 
mmc_omap_xfer_done is not called, but I suppose that it should be called in 
case of sdio_writesb. Maybe someone could tell me what does DDIR, CC, TC and 
OD stand for (these are defines in drivers/mmc/host/omap_hsmmc.c)?

thanks
--
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

sdio cmd53 doesn't work on omap 2430sdp

[Dmitriy Chumak]

Hi *,

Sorry for bothering all of you with my problem again.

I've asked it in [EMAIL PROTECTED] but have not got
some working solution. Maybe here somebody could help me.

I write an SDIO driver on OMAP 2430SDP platform.

I have three questions related to MMC subsystem:

1. When I issue sdio_writesb - it hangs. This happens because func
mmc_wait_for_req waits for request completion that should be
signaled by calling mmc_wait_done. mmc_wait_done is indirectly
called from mmc_omap_cmd_done if condition host-data == NULL ||
cmd-error (file: drivers/mmc/host/omap_hsmmc.c, line: 273) is
true. In my case the above condition is not true because
host-data is not NULL and cmd-error is NULL. Why this could be
happen. Which code is responsible for setting host-data to NULL
in case of successful sdio command completion?

2. Also when I issue sdio_writesb - I get an error status 108001
in mmc_omap_irq. If I've decoded it correctly it means CC, ERR and
DATA_TIMEOUT. What does it means and when this could be happened?
   
3. When I issue sdio_readw - it simply hangs, even without any
call to mmc_omap_irq.

How can I fix these?


Thanks in advance,
Dmitriy
--
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

Re: sdio cmd53 doesn't work on omap 2430sdp

[Dmitriy Chumak]

On Wednesday 21 May 2008 15:48:27 you wrote:

 the SDIO core issues a series of CMD52 to read the card capabilities and
 Setup the bus width etc... Does these go through fine for the card you are
 using? Does the core detect the new SDIO card?

Yes, all these go fine and the core detects a new SDIO card, only CMD53 
doesn't work. Could it be because of using DMA? Are there any way to not use 
DMA with CMD53?

Regards,
Dmitriy

--
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