From: Chris Ball <cjb@laptop.org>
To: Venkatraman S <svenkatr@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@nokia.com>,
Madhusudhan Chikkature <madhu.cr@ti.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 01/03] omap hsmmc: prevent race between dma and hsmmc callback
Date: Fri, 27 Aug 2010 20:37:27 +0100 [thread overview]
Message-ID: <20100827193727.GF23079@void.printf.net> (raw)
In-Reply-To: <618f0c911003100611q42e7f23cuc3c8d3f116ca7eb3@mail.gmail.com>
Hi,
Looks like the discussion on this patch stopped: do we think there's a
race worth fixing here?
On Wed, Mar 10, 2010 at 07:41:38PM +0530, Venkatraman S wrote:
> See previous post http://patchwork.kernel.org/patch/82907/
> Rebased to 2.6.34-rc1 and fixed comment alignment.
>
> CC: Adrian Hunter <adrian.hunter@nokia.com>
> CC: Madhusudhan C <madhu.cr@ti.com>
> CC: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Venkatraman S <svenkatr@ti.com>
> ---
> drivers/mmc/host/omap_hsmmc.c | 19 +++++++++++--------
> 1 files changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
> index 83f0aff..ea2a082 100644
> --- a/drivers/mmc/host/omap_hsmmc.c
> +++ b/drivers/mmc/host/omap_hsmmc.c
> @@ -1046,8 +1046,18 @@ static irqreturn_t omap_hsmmc_irq(int irq, void *dev_id)
>
> if (end_cmd || ((status & CC) && host->cmd))
> omap_hsmmc_cmd_done(host, host->cmd);
> - if ((end_trans || (status & TC)) && host->mrq)
> + if ((end_trans || (status & TC)) && host->mrq) {
> omap_hsmmc_xfer_done(host, data);
> + if (host->dma_ch != -1) {
> + omap_free_dma(host->dma_ch);
> + host->dma_ch = -1;
> + /*
> + * Callback: run in interrupt context.
> + * mutex_unlock will throw a kernel warning if used.
> + */
> + up(&host->sem);
> + }
> + }
>
> spin_unlock(&host->irq_lock);
>
> @@ -1267,13 +1277,6 @@ static void omap_hsmmc_dma_cb(int lch, u16
> ch_status, void *data)
> return;
> }
>
> - omap_free_dma(host->dma_ch);
> - host->dma_ch = -1;
> - /*
> - * DMA Callback: run in interrupt context.
> - * mutex_unlock will throw a kernel warning if used.
> - */
> - up(&host->sem);
> }
>
> /*
> --
> 1.6.3.3
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/03] omap hsmmc: prevent race between dma and hsmmc callback
Date: Fri, 27 Aug 2010 20:37:27 +0100 [thread overview]
Message-ID: <20100827193727.GF23079@void.printf.net> (raw)
In-Reply-To: <618f0c911003100611q42e7f23cuc3c8d3f116ca7eb3@mail.gmail.com>
Hi,
Looks like the discussion on this patch stopped: do we think there's a
race worth fixing here?
On Wed, Mar 10, 2010 at 07:41:38PM +0530, Venkatraman S wrote:
> See previous post http://patchwork.kernel.org/patch/82907/
> Rebased to 2.6.34-rc1 and fixed comment alignment.
>
> CC: Adrian Hunter <adrian.hunter@nokia.com>
> CC: Madhusudhan C <madhu.cr@ti.com>
> CC: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Venkatraman S <svenkatr@ti.com>
> ---
> drivers/mmc/host/omap_hsmmc.c | 19 +++++++++++--------
> 1 files changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
> index 83f0aff..ea2a082 100644
> --- a/drivers/mmc/host/omap_hsmmc.c
> +++ b/drivers/mmc/host/omap_hsmmc.c
> @@ -1046,8 +1046,18 @@ static irqreturn_t omap_hsmmc_irq(int irq, void *dev_id)
>
> if (end_cmd || ((status & CC) && host->cmd))
> omap_hsmmc_cmd_done(host, host->cmd);
> - if ((end_trans || (status & TC)) && host->mrq)
> + if ((end_trans || (status & TC)) && host->mrq) {
> omap_hsmmc_xfer_done(host, data);
> + if (host->dma_ch != -1) {
> + omap_free_dma(host->dma_ch);
> + host->dma_ch = -1;
> + /*
> + * Callback: run in interrupt context.
> + * mutex_unlock will throw a kernel warning if used.
> + */
> + up(&host->sem);
> + }
> + }
>
> spin_unlock(&host->irq_lock);
>
> @@ -1267,13 +1277,6 @@ static void omap_hsmmc_dma_cb(int lch, u16
> ch_status, void *data)
> return;
> }
>
> - omap_free_dma(host->dma_ch);
> - host->dma_ch = -1;
> - /*
> - * DMA Callback: run in interrupt context.
> - * mutex_unlock will throw a kernel warning if used.
> - */
> - up(&host->sem);
> }
>
> /*
> --
> 1.6.3.3
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-08-27 19:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 14:11 [PATCH 01/03] omap hsmmc: prevent race between dma and hsmmc callback Venkatraman S
2010-03-10 14:11 ` Venkatraman S
2010-03-10 14:27 ` Shilimkar, Santosh
2010-03-10 14:27 ` Shilimkar, Santosh
2010-03-10 15:20 ` Venkatraman S
2010-03-10 15:20 ` Venkatraman S
2010-03-10 17:07 ` Kevin Hilman
2010-03-10 17:07 ` Kevin Hilman
2010-03-10 14:27 ` Shilimkar, Santosh
2010-08-27 19:37 ` Chris Ball [this message]
2010-08-27 19:37 ` Chris Ball
-- strict thread matches above, loose matches on Subject: below --
2010-03-01 11:25 Venkatraman S
2010-03-01 11:25 ` Venkatraman S
2010-03-01 12:44 ` Sergei Shtylyov
2010-03-01 12:44 ` Sergei Shtylyov
2010-03-10 16:47 ` Madhusudhan
2010-03-10 16:47 ` Madhusudhan
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=20100827193727.GF23079@void.printf.net \
--to=cjb@laptop.org \
--cc=adrian.hunter@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=svenkatr@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.