public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Jarkko Nikula <jarkko.nikula@bitmer.com>,
	linux-omap@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] OMAP2+: DMA: Workaround for invalid source position
Date: Thu, 3 Nov 2011 14:29:01 -0700	[thread overview]
Message-ID: <20111103212901.GA31337@atomide.com> (raw)
In-Reply-To: <20111103212756.GZ31337@atomide.com>

* Tony Lindgren <tony@atomide.com> [111103 13:53]:
> * Peter Ujfalusi <peter.ujfalusi@ti.com> [111031 06:46]:
> > If the DMA source position has been asked before the
> > first actual data transfer has been done, the CSAC
> > register does not contain valid information.
> > We can identify this situation by checking the CDAC
> > register:
> > CDAC != 0 indicates that the DMA transfer on the channel has
> > been started already.
> > When CDAC == 0 we can not trust the CSAC value since it has
> > not been updated, and can contain random number.
> > Return the start address in case the DMA has not jet started.
> > 
> > Note: The CDAC register has been initialized to 0 at dma_start
> > time.
> > 
> > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> > ---
> >  arch/arm/plat-omap/dma.c |   15 +++++++++++++--
> >  1 files changed, 13 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm/plat-omap/dma.c b/arch/arm/plat-omap/dma.c
> > index c22217c..38b0d44 100644
> > --- a/arch/arm/plat-omap/dma.c
> > +++ b/arch/arm/plat-omap/dma.c
> > @@ -1024,12 +1024,23 @@ EXPORT_SYMBOL(omap_set_dma_callback);
> >   */
> >  dma_addr_t omap_get_dma_src_pos(int lch)
> >  {
> > +	u32 cdac;
> >  	dma_addr_t offset = 0;
> >  
> >  	if (cpu_is_omap15xx())
> >  		offset = p->dma_read(CPC, lch);
> > -	else
> > -		offset = p->dma_read(CSAC, lch);
> > +	else {
> > +		/*
> > +		 * CDAC == 0 indicates that the DMA transfer on the channel has
> > +		 * not been started (no data has been transferred so far).
> > +		 * Return the programmed source start address in this case.
> > +		 */
> > +		cdac = p->dma_read(CDAC, lch);
> > +		if (likely(cdac))
> > +			offset = p->dma_read(CSAC, lch);
> > +		else
> > +			offset = p->dma_read(CSSA, lch);
> > +	}
> >  
> >  	if (IS_DMA_ERRATA(DMA_ERRATA_3_3) && offset == 0)
> >  		offset = p->dma_read(CSAC, lch);
> 
> Should these tests be done only after the errata re-read for both
> src and dst patches? Otherwise the errata will not be handled?

Also, please Cc linux-arm-kernel list too so I don't have to repost :)

Tony

  reply	other threads:[~2011-11-03 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 14:20 [PATCH 0/2] OMAP2+: DMA: fix src/dst position reporting Peter Ujfalusi
2011-10-31 14:20 ` [PATCH 1/2] OMAP2+: DMA: Workaround for invalid source position Peter Ujfalusi
2011-11-03 21:27   ` Tony Lindgren
2011-11-03 21:29     ` Tony Lindgren [this message]
2011-11-04  9:35     ` Péter Ujfalusi
2011-11-04 20:08       ` Tony Lindgren
2011-10-31 14:20 ` [PATCH 2/2] OMAP2+: DMA: Workaround for invalid destination position Peter Ujfalusi
2011-11-01 19:26 ` [PATCH 0/2] OMAP2+: DMA: fix src/dst position reporting Jarkko Nikula

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=20111103212901.GA31337@atomide.com \
    --to=tony@atomide.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jarkko.nikula@bitmer.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@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