sd-io CTO error - advice

From: Ram
Date: Sat May 06 2006 - 06:37:46 EST


Hi,

I am using OMAP.

I am trying to extend sd card driver in linux to support sdio.

When i send CMD 5 - i get CTO error . i dont know whats the problem?.

if i do enable MMC_DEBUG prints i do get the response sometimes.

I dont know why the response is not consitent. add some printks it
works sometimes. remove them it does not work.

I tried sending CMD 5 in a loop - most of the time i do get CTO Errors?.


Any ideas on how to solve this problem?


is it related to the clock - i think it is set to what ever 400KHZ
(this works for MMC/SD Cards)
Is it different for SDIO ?.

The specs says 0-400KHZ during init phase.


Any ideas, where i should look at.

I have set CTO Value to the maximus - 0xff.




MMC1: set_ios: clock 0Hz busmode 1 powermode 0 Vdd 0.00
MMC1: set_ios: clock 400000Hz busmode 1 powermode 1 Vdd 0.21
MMC1: set_ios: clock 400000Hz busmode 1 powermode 2 Vdd 0.21
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0001 (CMD 5): EOC
MMC1: Response 90ff8000
MMC1: End request, err 0
MMC: req done (05): 0: 90ff8000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0001 (CMD 5): EOC
MMC1: Response 90000000
MMC1: End request, err 0
MMC: req done (05): 0: 90000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC: starting cmd 05 arg 00000000 flags 00000009
MMC1: CMD5, argument 0x00000000, 32-bit response, CRC
MMC IRQ 0080 (CMD 5): CTO
MMC1: Command timeout, CMD5
MMC1: Response 00000000
MMC1: End request, err 1
MMC: req done (05): 1: 00000000 00000000 00000000 00000000
MMC1: set_ios: clock 0Hz busmode 1 powermode 0 Vdd 0.00
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/