From: Philip Rakity <prakity@marvell.com>
To: Chris Ball <cjb@laptop.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] sdhci: Enable BUS WIDTH testing for MMC/eMMC cards
Date: Thu, 19 May 2011 14:32:34 -0700 [thread overview]
Message-ID: <CB69738F-30B5-4409-84B3-73D655B22FAC@marvell.com> (raw)
In-Reply-To: <m3wrhmbjz2.fsf@pullcord.laptop.org>
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@marvell.com>
>> ---
>> 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@laptop.org> <http://printf.net/>
> One Laptop Per Child
prev parent reply other threads:[~2011-05-19 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 19:25 [PATCH] sdhci: Enable BUS WIDTH testing for MMC/eMMC cards Philip Rakity
2011-05-19 18:53 ` Chris Ball
2011-05-19 21:32 ` Philip Rakity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CB69738F-30B5-4409-84B3-73D655B22FAC@marvell.com \
--to=prakity@marvell.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox