linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maurus Cuelenaere <mcuelenaere@gmail.com>
To: linux-samsung-soc@vger.kernel.org, pierre@ossman.eu,
	linux-mmc@vger.kernel.org, akpm@linux-foundation.org,
	sdhci-devel@lists.ossman.eu
Cc: ben-linux@fluff.org, thomas.ab@samsung.com
Subject: [PATCH 3/3] SDHCI: Enable multiblock transfers in sdhci-s3c
Date: Tue, 04 May 2010 11:43:30 +0200	[thread overview]
Message-ID: <4BDFEC42.5020900@gmail.com> (raw)
In-Reply-To: <cover.1272966142.git.mcuelenaere@gmail.com>

Wifi over SDIO doesn't work correctly without multiblock, so enable
this. This patch depends on the following patches:

[PATCH] s3c6410: Enable ADMA feature in 6410 sdhci controller.
[PATCH] s3c6410: Add new quirk in sdhci driver and update ADMA descriptor build.

Signed-off-by: Maurus Cuelenaere <mcuelenaere@gmail.com>
---
 drivers/mmc/host/sdhci-s3c.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/drivers/mmc/host/sdhci-s3c.c b/drivers/mmc/host/sdhci-s3c.c
index 2136794..2c1a618 100644
--- a/drivers/mmc/host/sdhci-s3c.c
+++ b/drivers/mmc/host/sdhci-s3c.c
@@ -330,9 +330,6 @@ static int __devinit sdhci_s3c_probe(struct platform_device *pdev)
 	 * support as well. */
 	host->quirks |= SDHCI_QUIRK_BROKEN_DMA;
 
-	/* PIO currently has problems with multi-block IO */
-	host->quirks |= SDHCI_QUIRK_NO_MULTIBLOCK;
-
 #endif /* CONFIG_MMC_SDHCI_S3C_DMA */
 
 	/* It seems we do not get an DATA transfer complete on non-busy
-- 
1.7.1

      parent reply	other threads:[~2010-05-04  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1272966142.git.mcuelenaere@gmail.com>
2010-05-04  9:43 ` [PATCH 1/3] s3c6410: Add new quirk in sdhci driver and update ADMA descriptor build Maurus Cuelenaere
2010-05-05 14:59   ` Ben Dooks
2010-05-05 15:06     ` Maurus Cuelenaere
2010-05-04  9:43 ` [PATCH 2/3] s3c6410: Enable ADMA feature in 6410 sdhci controller Maurus Cuelenaere
2010-05-04  9:43 ` Maurus Cuelenaere [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=4BDFEC42.5020900@gmail.com \
    --to=mcuelenaere@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben-linux@fluff.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=pierre@ossman.eu \
    --cc=sdhci-devel@lists.ossman.eu \
    --cc=thomas.ab@samsung.com \
    /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;
as well as URLs for NNTP newsgroup(s).