* Pandita, Vikram <vikram.pandita@xxxxxx> [090924 05:59]: > > > >-----Original Message----- > >From: Shilimkar, Santosh > >Sent: Thursday, September 24, 2009 2:24 AM > >To: Jarkko Nikula; hari n > >Cc: Pandita, Vikram; linux-omap@xxxxxxxxxxxxxxx > >Subject: RE: [OMAP3] ALSA driver 'suspend/resume' handlers > > > >Hari/Jarkko, > >> -----Original Message----- > >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > >> owner@xxxxxxxxxxxxxxx] On Behalf Of Jarkko Nikula > >> Sent: Thursday, September 24, 2009 12:16 PM > >> To: hari n > >> Cc: Pandita, Vikram; linux-omap@xxxxxxxxxxxxxxx > >> Subject: Re: [OMAP3] ALSA driver 'suspend/resume' handlers > >> > >> On Wed, 23 Sep 2009 00:02:01 -0500 > >> hari n <hari.zoom@xxxxxxxxx> wrote: > >> <snip> > >omap_stop_dma() should be issued when we really want to stop the DMA transfer and issuing this with > >an outstanding transfer is a BUG in ALSA driver. > > > >Having said that, there is also bug in the DMA driver which doesn't disable the channel in linking > >cases. Since we use always hardware synchronized method, hardware will take care of draining the > >buffer so no loss of data. > > > >So option B should be ok and USB case also would work as mentioned above. > > USB is not a valid use case to discuss here. > Mentor OTG controller has its internal DMA and so does EHCI/OHCI host controller. > USB on OMAP3 _does_not_ use system DMA. At least tusb6010 connected to 2420 on n800 and n810 uses the system DMA. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
