public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Nishanth Menon <nm@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	Tony Lindgren <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/2] omap: dma: Fix buffering disable bit setting for omap24xx
Date: Fri, 1 Oct 2010 12:20:13 +0300	[thread overview]
Message-ID: <20101001122013.dc789e6f.jhnikula@gmail.com> (raw)
In-Reply-To: <4CA591FE.7030201@ti.com>

On Fri, 1 Oct 2010 02:47:10 -0500
Nishanth Menon <nm@ti.com> wrote:

> Peter Ujfalusi had written, on 10/01/2010 01:39 AM, the following:
> [...]
> > diff --git a/arch/arm/plat-omap/dma.c b/arch/arm/plat-omap/dma.c
> > index ec7eddf..7115884 100644
> > --- a/arch/arm/plat-omap/dma.c
> > +++ b/arch/arm/plat-omap/dma.c
> > @@ -1000,7 +1000,7 @@ void omap_start_dma(int lch)
> >  	 * This will always fail on ES1.0
> >  	 */
> >  	if (cpu_is_omap24xx())
> > -		l |= OMAP_DMA_CCR_EN;
> in code comment for errata helps over time I guess.. could be my pet peeve.
> > +		l |= OMAP_DMA_CCR_BUFFERING_DISABLE;
> 
Definitely. Unfortunately I don't have a 24xx TRM or errata so I cannot
check it. This workaround was introduced by a commit 1a8bfa so I think
it originated from pre-git history or from some inhouse tree.


-- 
Jarkko

  reply	other threads:[~2010-10-01  9:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  6:39 [PATCH 0/2] OMAP2/3: DMA: FIFO drain errata fixes Peter Ujfalusi
2010-10-01  6:39 ` [PATCH 1/2] omap: dma: Fix buffering disable bit setting for omap24xx Peter Ujfalusi
2010-10-01  7:47   ` Nishanth Menon
2010-10-01  9:20     ` Jarkko Nikula [this message]
2010-10-01  6:39 ` [PATCH 2/2] OMAP3: DMA: Errata: sDMA FIFO draining does not finish Peter Ujfalusi
2010-10-01  7:00   ` Jarkko Nikula
2010-10-01  7:45   ` Nishanth Menon
2010-10-01  8:51     ` Peter Ujfalusi
2010-10-01  9:23       ` Nishanth Menon
2010-10-01 10:40         ` Peter Ujfalusi
2010-10-01  9:29       ` G, Manjunath Kondaiah
2010-10-01  9:43         ` Nishanth Menon
2010-10-01  9:45           ` G, Manjunath Kondaiah
2010-10-01 10:43             ` Peter Ujfalusi
2010-10-01 10:41         ` Peter Ujfalusi
2010-10-01 11:09           ` G, Manjunath Kondaiah
2010-10-01 11:43             ` Jarkko Nikula
2010-10-01 11:48               ` Jarkko Nikula
2010-10-01 17:02               ` Tony Lindgren

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=20101001122013.dc789e6f.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=nm@ti.com \
    --cc=peter.ujfalusi@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox