Re: [PATCH] sdhci: Enable BUS WIDTH testing for MMC/eMMC cards

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Chris,

This is the reason why I did the other patch for bus width testing !  Some hardware does not work.

Philip

On May 19, 2011, at 11:53 AM, Chris Ball wrote:

> Hi Philip,
> 
> On Fri, Jan 21 2011, Philip Rakity wrote:
>> The PXA family of controllers (PXA168/PXA910/MMP2) support CMD14/CMD19
>> transactions that are used to test the MMC/eMMC bus width for 1, 4, or
>> 8 bits.
>> 
>> Indicate to the mmc layer that it is safe to do bus width testing.
>> 
>> Signed-off-by: Philip Rakity <prakity@xxxxxxxxxxx>
>> ---
>> drivers/mmc/host/sdhci-pxa.c |    3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>> 
>> diff --git a/drivers/mmc/host/sdhci-pxa.c b/drivers/mmc/host/sdhci-pxa.c
>> index ed044a8..0afc763 100644
>> --- a/drivers/mmc/host/sdhci-pxa.c
>> +++ b/drivers/mmc/host/sdhci-pxa.c
>> @@ -121,6 +121,9 @@ static int __devinit sdhci_pxa_probe(struct platform_device *pdev)
>> 	host->irq = irq;
>> 	host->quirks = SDHCI_QUIRK_BROKEN_ADMA | SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;
>> 
>> +	/* enable mmc bus width testing */
>> +	host->mmc->caps |= MMC_CAP_BUS_WIDTH_TEST;
>> +
>> 	/* If slot design supports 8 bit data, indicate this to MMC. */
>> 	if (pdata->flags & PXA_FLAG_SD_8_BIT_CAPABLE_SLOT)
>> 		host->mmc->caps |= MMC_CAP_8_BIT_DATA;
> 
> This patch causes a 10 second boot time delay here, on XO-1.75/MMP2:
> 
> [  625.245478] Waiting for root device /dev/mmcblk0p2...
> [  634.877598] mmc2: Timeout waiting for hardware interrupt.
> [  634.882966] sdhci: =========== REGISTER DUMP (mmc2)===========
> [  634.888756] sdhci: Sys addr: 0x1cfc7864 | Version:  0x00000002
> [  634.888756] sdhci: Blk size: 0x00007004 | Blk cnt:  0x00000000
> [  634.894544] sdhci: Argument: 0x00000000 | Trn mode: 0x00000003
> [  634.900334] sdhci: Present:  0x01fa0000 | Host ctl: 0x00000007
> [  634.911913] sdhci: Power:    0x0000000b | Blk gap:  0x00000000
> [  634.911913] sdhci: Wake-up:  0x00000000 | Clock:    0x00000207
> [  634.917703] sdhci: Timeout:  0x0000000e | Int stat: 0x00000000
> [  634.929283] sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
> [  634.929283] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
> [  634.935071] sdhci: Caps:     0x25fcc8b2 | Caps_1:   0x00002f77
> [  634.940861] sdhci: Cmd:      0x0000133a | Max curr: 0x00000000
> [  634.946651] sdhci: Host ctl2: 0x00000000
> [  634.952438] sdhci: ===========================================
> [  634.962269] mmc2: new high speed DDR MMC card at address 0001
> 
> Everything seems to work after the delay, though.  Any ideas?
> Doesn't seem to happen with CONFIG_MMC_DEBUG=y.
> (Maybe you can test on an XO?)
> 
> Thanks,
> 
> - Chris.
> -- 
> Chris Ball   <cjb@xxxxxxxxxx>   <http://printf.net/>
> One Laptop Per Child

--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux