Hari, > -----Original Message----- > From: Shilimkar, Santosh > Sent: Thursday, September 24, 2009 12:54 PM > 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 > > > > I don't see any problem if suspend and resume callbacks are added into > > omap-pcm.c and omap-mcbsp.c calling e.g. omap_mcbsp_config if needed. > > 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. Which option finally we converged on this issue? Shall we fix in the DMA driver or you want to do this in ALSA? Regards, Santosh -- 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
