From: jhnikula@gmail.com (Jarkko Nikula)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/4] omap: dma: Fix buffering disable bit setting for omap24xx
Date: Mon, 4 Oct 2010 12:50:19 +0300 [thread overview]
Message-ID: <20101004125019.98228ee3.jhnikula@gmail.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402DB90CA39@dbde02.ent.ti.com>
On Mon, 4 Oct 2010 14:44:28 +0530
"G, Manjunath Kondaiah" <manjugk@ti.com> wrote:
>
>
> > -----Original Message-----
> > From: linux-omap-owner at vger.kernel.org
> > [mailto:linux-omap-owner at vger.kernel.org] On Behalf Of Peter Ujfalusi
> > Sent: Monday, October 04, 2010 1:48 PM
> > To: Tony Lindgren
> > Cc: linux-omap at vger.kernel.org; Jarkko Nikula;
> > linux-arm-kernel at lists.infradead.org
> > Subject: [PATCH v4 1/4] omap: dma: Fix buffering disable bit
> > setting for omap24xx
> >
> > From: ext Jarkko Nikula <jhnikula@gmail.com>
> >
> > An errata workaround for omap24xx is not setting the
> > buffering disable bit
> > 25 what is the purpose but channel enable bit 7 instead.
>
> ...
>
> > diff --git a/arch/arm/plat-omap/dma.c
> > b/arch/arm/plat-omap/dma.c index ec7eddf..6914ccf 100644
> > --- a/arch/arm/plat-omap/dma.c
> > +++ b/arch/arm/plat-omap/dma.c
> > @@ -999,8 +999,9 @@ void omap_start_dma(int lch)
> > * Errata: On ES2.0 BUFFERING disable must be set.
> > * This will always fail on ES1.0
> > */
>
> Sorry, I didn't catch this with earlier patch.
>
> Looks like wrong comment. only on 2430ES1.0 and for all omap2420,
> buffer disable should be set.
> I feel below description will be useful to the reader:
> "Errata: Inter Frame DMA buffering issue(All OMAP2420 and OMAP2430ES1.0):
> DMA will wrongly buffer elements if packing and bursting is enabled.
> This might result in data gets stalled in FIFO at the end of the block.
> Workaround: DMA channels must have BUFFERING_DISABLED bit set to guarantee
> no data will stay in the DMA FIFO in case inter frame buffering occurs.
>
Ok, no problem. I'll add this to the next version. This is good to get
documented.
--
Jarkko
next prev parent reply other threads:[~2010-10-04 9:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 8:18 [PATCH v4 0/4] OMAP2/3: DMA: FIFO drain errata fixes Peter Ujfalusi
2010-10-04 8:18 ` [PATCH v4 1/4] omap: dma: Fix buffering disable bit setting for omap24xx Peter Ujfalusi
2010-10-04 9:14 ` G, Manjunath Kondaiah
2010-10-04 9:50 ` Jarkko Nikula [this message]
2010-10-04 8:18 ` [PATCH v4 2/4] OMAP: DMA: Introduce errata handling variable, and macro Peter Ujfalusi
2010-10-04 8:18 ` [PATCH v4 3/4] OMAP2: DMA: Use errata flag for disabling buffering Peter Ujfalusi
2010-10-04 9:15 ` G, Manjunath Kondaiah
2010-10-04 8:18 ` [PATCH v4 4/4] OMAP3: DMA: Errata i541: sDMA FIFO draining does not finish Peter Ujfalusi
2010-10-04 9:17 ` G, Manjunath Kondaiah
2010-10-04 10:42 ` Peter Ujfalusi
2010-10-04 11:04 ` G, Manjunath Kondaiah
2010-10-04 16:55 ` Tony Lindgren
2010-10-04 8:29 ` [PATCH v4 0/4] OMAP2/3: DMA: FIFO drain errata fixes Peter Ujfalusi
2010-10-04 8:33 ` Peter Ujfalusi
2010-10-04 16:57 ` 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=20101004125019.98228ee3.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).