Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755756AbYKCUK3 (ORCPT ); Mon, 3 Nov 2008 15:10:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754209AbYKCUKO (ORCPT ); Mon, 3 Nov 2008 15:10:14 -0500 Received: from aeryn.fluff.org.uk ([87.194.8.8]:36626 "EHLO teyla.home.fluff.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754169AbYKCUKN (ORCPT ); Mon, 3 Nov 2008 15:10:13 -0500 Message-Id: <20081103201010.165171320@fluff.org.uk> References: <20081103200944.099353331@fluff.org.uk> User-Agent: quilt/0.46-1 Date: Mon, 03 Nov 2008 20:09:46 +0000 From: Ben Dooks To: linux-kernel@vger.kernel.org Cc: drzeus-mmc@drzeus.cx, sdhci-devel@list.drzeus.cx, Ben Dooks Subject: [patch 2/7] SDHCI: Print ADMA status and pointer on debug Content-Disposition: inline; filename=simtec/s3c64xx/sdhci-print-adma-status-if-enabled.patch Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1108 Lines: 30 If using ADMA, then we should print the ADMA error and current pointer in sdhci_dumpregs() when any debug is requested. Signed-off-by: Ben Dooks --- linux.git.orig/drivers/mmc/host/sdhci.c 2008-10-27 08:17:43.000000000 +0000 +++ linux.git/drivers/mmc/host/sdhci.c 2008-10-27 11:01:20.000000000 +0000 @@ -73,6 +73,11 @@ static void sdhci_dumpregs(struct sdhci_ readl(host->ioaddr + SDHCI_CAPABILITIES), readl(host->ioaddr + SDHCI_MAX_CURRENT)); + if (host->flags & SDHCI_USE_ADMA) + printk(KERN_DEBUG DRIVER_NAME ": ADMA Err: 0x%08x | ADMA Ptr: 0x%08x\n", + readl(host->ioaddr + SDHCI_ADMA_ERROR), + readl(host->ioaddr + SDHCI_ADMA_ADDRESS)); + printk(KERN_DEBUG DRIVER_NAME ": ===========================================\n"); } -- Ben (ben@fluff.org, http://www.fluff.org/) 'a smiley only costs 4 bytes' -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/