All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Madhusudhan <madhu.cr@ti.com>
Cc: 'Venkatraman S' <svenkatr@ti.com>,
	'Adrian Hunter' <adrian.hunter@nokia.com>,
	'linux-mmc Mailing List' <linux-mmc@vger.kernel.org>,
	'linux-omap Mailing List' <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2] omap_hsmmc: improve interrupt synchronisation
Date: Mon, 26 Apr 2010 14:17:41 -0700	[thread overview]
Message-ID: <20100426211741.GO7225@atomide.com> (raw)
In-Reply-To: <002801cae554$09ac97c0$544ff780@am.dhcp.ti.com>

* Madhusudhan <madhu.cr@ti.com> [100426 08:17]:
> 
> 
> > -----Original Message-----
> > From: svenkatr@gmail.com [mailto:svenkatr@gmail.com] On Behalf Of
> > Venkatraman S
> > Sent: Monday, April 26, 2010 4:01 AM
> > To: Adrian Hunter
> > Cc: Madhusudhan Chikkature; linux-mmc Mailing List; linux-omap Mailing
> > List
> > Subject: Re: [PATCH v2] omap_hsmmc: improve interrupt synchronisation
> > 
> > Adrian Hunter <adrian.hunter@nokia.com> wrote:
> > > From ad2e1cd024ccf9144b6620cfe808893719db738f Mon Sep 17 00:00:00 2001
> > > From: Adrian Hunter <adrian.hunter@nokia.com>
> > > Date: Wed, 14 Apr 2010 16:26:45 +0300
> > > Subject: [PATCH] omap_hsmmc: improve interrupt synchronisation
> > >
> > > The following changes were needed:
> > >        - do not use in_interrupt() because it will not work
> > >        with threaded interrupts
> > >
> > > In addition, the following improvements were made:
> > >        - ensure DMA is unmapped only after the final DMA interrupt
> > >        - ensure a request is completed only after the final DMA
> > interrupt
> > >        - disable controller interrupts when a request is not in progress
> > >        - remove the spin-lock protecting the start of a new request from
> > >        an unexpected interrupt because the locking was complicated and
> > >        a 'req_in_progress' flag suffices (since the spin-lock only
> > defers
> > >        the unexpected interrupts anyway)
> > >        - instead use the spin-lock to protect the MMC interrupt handler
> > >        from the DMA interrupt handler
> > >        - remove the semaphore preventing DMA from being started while
> > >        the previous DMA is still in progress - the other changes make
> > that
> > >        impossible, so it is now a BUG_ON condition
> > >        - ensure the controller interrupt status is clear before exiting
> > >        the interrrupt handler
> > >
> > > In general, these changes make the code safer but do not fix any
> > specific
> > > bugs so backporting is not necessary.
> > >
> > > Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
> > > ---
> > >
> > >
> > > Changes from version 1:
> > >        - use a spin-lock to protect the MMC interrupt handler
> > >        from the DMA interrupt handler
> > >        - use do {} while loop instead of goto in omap_hsmmc_irq
> > >
> > > S Venkatraman's request to use omap_hsmmc_dma_cleanup(host, 0) in
> > > omap_hsmmc_dma_cb() was not done because the code was not
> > > sufficiently the same.
> 
> <snip>
> 
> > This looks good and I don't have any other comments.
> >      I have tested, on MMC and SD cards which I have,
> > a) Basic file read / write
> > b) boot with filesystem on ext3 partition on SD card
> >  on OMAP3 and OMAP4 SDP.
> > 
> > So you can add,
> > Tested-by: Venkatraman S <svenkatr@ti.com>
> 
> I reviewed the V2 patch. I don’t have any comments too.
> 
> Acked-by: Madhusudhan Chikkature <madhu.cr@ti.com>

Nice work Adrian!

Acked-by: Tony Lindgren <tony@atomide.com>

  reply	other threads:[~2010-04-26 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 13:08 [PATCH v2] omap_hsmmc: improve interrupt synchronisation Adrian Hunter
2010-04-26  9:00 ` Venkatraman S
2010-04-26 15:20   ` Madhusudhan
2010-04-26 21:17     ` Tony Lindgren [this message]
2010-05-03  6:57       ` Adrian Hunter

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=20100426211741.GO7225@atomide.com \
    --to=tony@atomide.com \
    --cc=adrian.hunter@nokia.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=svenkatr@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 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.