From patchwork Tue Feb 3 14:05:58 2009 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Jean Pihet X-Patchwork-Id: 5232 Received: from vger.kernel.org (vger.kernel.org [209.132.176.167]) by demeter.kernel.org (8.14.2/8.14.2) with ESMTP id n13E6RCF011727 for ; Tue, 3 Feb 2009 14:06:28 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751978AbZBCOG0 (ORCPT ); Tue, 3 Feb 2009 09:06:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752038AbZBCOG0 (ORCPT ); Tue, 3 Feb 2009 09:06:26 -0500 Received: from gateway-1237.mvista.com ([63.81.120.158]:54132 "EHLO gateway-1237.mvista.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751583AbZBCOGZ (ORCPT ); Tue, 3 Feb 2009 09:06:25 -0500 Received: from ip6-localhost (asshur.mvista.com [10.0.0.11]) by hermes.mvista.com (Postfix) with ESMTP id 905DD18BAD; Tue, 3 Feb 2009 06:06:14 -0800 (PST) From: Jean Pihet Organization: MontaVista To: Tony Lindgren , Adrian Hunter , linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org, "Jarkko Lavinen (NMP/Helsinki)" , Pierre Ossman , linux-kernel@vger.kernel.org Subject: [PATCH] OMAP: MMC: recover from transfer failures - Resend Date: Tue, 3 Feb 2009 15:05:58 +0100 User-Agent: KMail/1.9.9 References: <20081207213617.10456.43951.stgit@localhost> <200902020946.16508.jpihet@mvista.com> <20090202190503.GT7215@atomide.com> In-Reply-To: <20090202190503.GT7215@atomide.com> MIME-Version: 1.0 Message-Id: <200902031505.58697.jpihet@mvista.com> Sender: linux-omap-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-omap@vger.kernel.org Hi, This is a re-send of the patch that fixes a MMC host controller deadlock. The problem happens when removing the MMC/SD device when a transfer is on-going. It has been tested on OMAP3430 but this fix should apply to OMAP2 chips as well, as seen from the TRMs. Regards, Jean From d143f6b2e705aa4e9d2b032097fd1c82f8163262 Mon Sep 17 00:00:00 2001 From: Jean Pihet Date: Thu, 8 Jan 2009 12:35:21 +0100 Subject: [PATCH] OMAP: MMC: recover from transfer failures Timeouts during a command that has a data phase can result in the next command issued after the command that failed not being processed, i.e. no interrupt ever occurs to indicate the command has completed. This failure can result in a deadlock. This patch resets the data state machine to clear the error in case of a command timeout. Tested on OMAP3430 chip and intensive MMC/SD device removal while transferring data. Signed-off-by: Andy Lowe Signed-off-by: Jean Pihet Signed-off-by: Adrian Hunter ---  drivers/mmc/host/omap_hsmmc.c |    9 ++++++++-  1 files changed, 8 insertions(+), 1 deletions(-) -- 1.5.4.4.21.gc4a6c On Monday 02 February 2009 20:05:06 Tony Lindgren wrote: > Hi, > > * Jean Pihet [090202 00:46]: > > Tony, > > > > Has this patch been applied to the linux-omap tree? Does it need to go > > the patchwork? > > > > Cf. http://marc.info/?l=linux-omap&m=123141577308177&w=2 > > I'm not applying MMC patches, we need to move that discussion to LKML > and keep Pierre involved. > > Jarkko Lavinen was planning to set up a git branch against the mainline > tree for the omap mmc patches, so until we have that, let's just let the > patches float on the list for a while. > > But yeah, if you want patchwork to pick up your patch so it does not > get lost, just please resend it to the linux-omap list and it should > get automatically picked up by patchwork. > > Regards, > > Tony From d143f6b2e705aa4e9d2b032097fd1c82f8163262 Mon Sep 17 00:00:00 2001 From: Jean Pihet Date: Thu, 8 Jan 2009 12:35:21 +0100 Subject: [PATCH] OMAP: MMC: recover from transfer failures Timeouts during a command that has a data phase can result in the next command issued after the command that failed not being processed, i.e. no interrupt ever occurs to indicate the command has completed. This failure can result in a deadlock. This patch resets the data state machine to clear the error in case of a command timeout. Tested on OMAP3430 chip and intensive MMC/SD device removal while transferring data. Signed-off-by: Andy Lowe Signed-off-by: Jean Pihet Signed-off-by: Adrian Hunter --- drivers/mmc/host/omap_hsmmc.c | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c index d5c1e9d..97150c0 100644 --- a/drivers/mmc/host/omap_hsmmc.c +++ b/drivers/mmc/host/omap_hsmmc.c @@ -464,8 +464,15 @@ static irqreturn_t mmc_omap_irq(int irq, void *dev_id) } end_cmd = 1; } - if (host->data) + if (host->data) { mmc_dma_cleanup(host); + OMAP_HSMMC_WRITE(host->base, SYSCTL, + OMAP_HSMMC_READ(host->base, + SYSCTL) | SRD); + while (OMAP_HSMMC_READ(host->base, + SYSCTL) & SRD) + ; + } } if ((status & DATA_TIMEOUT) || (status & DATA_CRC)) { -- 1.5.4.4.21.gc4a6c