public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Peppe CAVALLARO <peppe.cavallaro@st.com>
To: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: sdhci-stm performance issues
Date: Tue, 31 Aug 2010 12:59:01 +0200	[thread overview]
Message-ID: <4C7CE075.8060309@st.com> (raw)
In-Reply-To: <107012446AC13D4C90B85672EAF5FB0E9E0FB3CE8E@SAFEX1MAIL3.st.com>

[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]

 Hello
The problem was due to the missing both 8BIT and MMC_SPEED supports in
my sdhci driver (comes from the 2.6.32 Kernel series).
I've also added the patch in attachment.

Best Regards
Peppe

On 8/24/2010 5:11 PM, Peppe CAVALLARO wrote:
>
> Hello,
> testing the sdhci-stm.c driver, I sent some weeks ago to the mailing list,
> I'm facing some performance issues.
> For example, when copy a file (e.g. ~10MiB) to the card, I've noticed
> that,
> in the sdhci_prepare_data, the maximum value for data->blocks is 248.
>
> The sdhci-stm driver uses the ADMA and:
>   max_seg_size = 65536,
>   max_hw_segs = 128,
>   max_phys_segs = 128,
>   max_req_size = 524288,
>   max_blk_size = 2048,
>   max_blk_count = 65535.
>
> Using my arasan.c code, I've also sent to this mailing list in July,
> I could see that the data->blocks was bigger than 248 and the
> performances were better.
> Note that this driver used the same mmc_host parameters (max_blk_size
> etc.) reported
> above for the sdhci-stm.
>
> What am I missing?
>
> Welcome advice.
>
> Best Regards,
> Giuseppe
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-sdhci-add-MMC_CAP_8_BIT_DATA-in-the-Host-capabiliti.patch --]
[-- Type: text/x-patch; name="0001-sdhci-add-MMC_CAP_8_BIT_DATA-in-the-Host-capabiliti.patch", Size: 912 bytes --]

From b3427a938ed04febdaa729ca500f266274e06bd2 Mon Sep 17 00:00:00 2001
From: Giuseppe Cavallaro <peppe.cavallaro@st.com>
Date: Tue, 31 Aug 2010 05:43:45 +0200
Subject: [PATCH (sh-2.6.32.y)] sdhci: add MMC_CAP_8_BIT_DATA in the Host capabilities

Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@st.com>
---
 drivers/mmc/host/sdhci.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index 955cad9..1c49326 100644
--- a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
@@ -1799,7 +1799,7 @@ int sdhci_add_host(struct sdhci_host *host)
 	mmc->caps = MMC_CAP_SDIO_IRQ;
 
 	if (!(host->quirks & SDHCI_QUIRK_FORCE_1_BIT_DATA))
-		mmc->caps |= MMC_CAP_4_BIT_DATA;
+		mmc->caps |= MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA;
 
 	if (caps & SDHCI_CAN_DO_HISPD)
 		mmc->caps |= MMC_CAP_SD_HIGHSPEED;
-- 
1.5.5.6


  reply	other threads:[~2010-08-31 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 15:11 sdhci-stm performance issues Peppe CAVALLARO
2010-08-31 10:59 ` Peppe CAVALLARO [this message]
2010-09-17 22:19   ` [PATCH RESEND] sdhci: add MMC_CAP_8_BIT_DATA in the Host capabilities Chris Ball
2010-09-20  6:51     ` Peppe CAVALLARO
2010-09-21  1:24       ` Chris Ball

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=4C7CE075.8060309@st.com \
    --to=peppe.cavallaro@st.com \
    --cc=akpm@linux-foundation.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