From: Chris Ball <cjb@laptop.org>
To: Sekhar Nori <nsekhar@ti.com>
Cc: linux-mmc@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
Alagu Sankar <alagusankar@embwise.com>
Subject: Re: [PATCH v5] mmc: davinci: add support for SDIO irq handling
Date: Mon, 10 Jan 2011 00:17:38 +0000 [thread overview]
Message-ID: <20110110001738.GB26898@void.printf.net> (raw)
In-Reply-To: <1294038807-16450-1-git-send-email-nsekhar@ti.com>
Hi Sekhar,
On Mon, Jan 03, 2011 at 12:43:27PM +0530, Sekhar Nori wrote:
> From: Alagu Sankar <alagusankar@embwise.com>
>
> This patch adds support for handling SDIO interrupt on
> DaVinci MMC/SD controller.
>
> The patch has been tested on DM355 and DA850 EVMs with
> Marvell Libertas based SDIO wireless LAN card.
>
> Signed-off-by: Alagu Sankar <alagusankar@embwise.com>
> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
> ---
> Applies to mmc-next branch of the mmc tree
>
> Since v4, fixed a typo in patch description
>
> drivers/mmc/host/davinci_mmc.c | 78 +++++++++++++++++++++++++++++++++++++---
> 1 files changed, 73 insertions(+), 5 deletions(-)
Thanks, pushed to mmc-next for .38 with some trivial indentation fixes
as below:
diff --git a/drivers/mmc/host/davinci_mmc.c b/drivers/mmc/host/davinci_mmc.c
index 6b09752..0076c74 100644
--- a/drivers/mmc/host/davinci_mmc.c
+++ b/drivers/mmc/host/davinci_mmc.c
@@ -882,7 +882,7 @@ mmc_davinci_xfer_done(struct mmc_davinci_host *host, struct mmc_data *data)
* 2.1.6): Signal SDIO interrupt only if it is enabled by core
*/
if (host->sdio_int && !(readl(host->base + DAVINCI_SDIOST0) &
- SDIOST0_DAT1_HI)) {
+ SDIOST0_DAT1_HI)) {
writel(SDIOIST_IOINT, host->base + DAVINCI_SDIOIST);
mmc_signal_sdio_irq(host->mmc);
}
@@ -962,7 +962,7 @@ static irqreturn_t mmc_davinci_sdio_irq(int irq, void *dev_id)
status = readl(host->base + DAVINCI_SDIOIST);
if (status & SDIOIST_IOINT) {
dev_dbg(mmc_dev(host->mmc),
- "SDIO interrupt status %x\n", status);
+ "SDIO interrupt status %x\n", status);
writel(status | SDIOIST_IOINT, host->base + DAVINCI_SDIOIST);
mmc_signal_sdio_irq(host->mmc);
}
@@ -1124,12 +1124,12 @@ static void mmc_davinci_enable_sdio_irq(struct mmc_host *mmc, int enable)
} else {
host->sdio_int = true;
writel(readl(host->base + DAVINCI_SDIOIEN) |
- SDIOIEN_IOINTEN, host->base + DAVINCI_SDIOIEN);
+ SDIOIEN_IOINTEN, host->base + DAVINCI_SDIOIEN);
}
} else {
host->sdio_int = false;
writel(readl(host->base + DAVINCI_SDIOIEN) & ~SDIOIEN_IOINTEN,
- host->base + DAVINCI_SDIOIEN);
+ host->base + DAVINCI_SDIOIEN);
}
}
@@ -1331,7 +1331,7 @@ static int __init davinci_mmcsd_probe(struct platform_device *pdev)
if (host->sdio_irq >= 0) {
ret = request_irq(host->sdio_irq, mmc_davinci_sdio_irq, 0,
- mmc_hostname(mmc), host);
+ mmc_hostname(mmc), host);
if (!ret)
mmc->caps |= MMC_CAP_SDIO_IRQ;
}
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-01-10 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 7:13 [PATCH v5] mmc: davinci: add support for SDIO irq handling Sekhar Nori
2011-01-10 0:17 ` Chris Ball [this message]
2011-01-12 14:03 ` Nori, Sekhar
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=20110110001738.GB26898@void.printf.net \
--to=cjb@laptop.org \
--cc=alagusankar@embwise.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-mmc@vger.kernel.org \
--cc=nsekhar@ti.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