From: Tony Lindgren <tony@atomide.com>
To: Venkatraman S <svenkatr@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2] dma: fix scope of errata i88 upto 3430ES1.0
Date: Mon, 3 May 2010 09:35:04 -0700 [thread overview]
Message-ID: <20100503163504.GP29604@atomide.com> (raw)
In-Reply-To: <g2q618f0c911004260751kae29a2fq6b90db2f221e15ca@mail.gmail.com>
* Venkatraman S <svenkatr@ti.com> [100426 07:46]:
> Tony Lindgren <tony@atomide.com> wrote:
> > * Venkatraman S <svenkatr@ti.com> [100419 03:47]:
> >> Hi Tony,
> >> > Venkatraman S <svenkatr@ti.com> wrote:
> >> > From 2799506180649cbb61d24cf2b4171425b2e1fa80 Mon Sep 17 00:00:00 2001
> >> > From: Venkatraman S <svenkatr@ti.com>
> >> > Date: Mon, 5 Apr 2010 20:56:27 +0530
> >> > Subject: [PATCH] dma: fix scope of errata i88 upto 3430ES1.0
> >> >
> >> > DMA errata for special end of block programming is applicable
> >> > only for OMAP2430 & OMAP3430 ES1.0.
> >> > This patch does the necessary checks before the workaround
> >> > is applied. Tested on 3430 SDP
> >> >
> >> > Signed-off-by: Thara Gopinath <thara@ti.com>
> >> > Signed-off-by: Venkatraman S <svenkatr@ti.com>
> >> > Reviewed-by: Shilimkar Santosh <santosh.shilimkar@ti.com>
> >> > ---
> >> > From v1, removed the redundant omap3430() check
> >> >
> >> > arch/arm/plat-omap/dma.c | 20 ++++++++++++--------
> >> > 1 files changed, 12 insertions(+), 8 deletions(-)
> >> >
> >> > diff --git a/arch/arm/plat-omap/dma.c b/arch/arm/plat-omap/dma.c
> >> > index 2ab224c..a9b480a 100644
> >> > --- a/arch/arm/plat-omap/dma.c
> >> > +++ b/arch/arm/plat-omap/dma.c
> >> > @@ -1663,14 +1663,17 @@ int omap_stop_dma_chain_transfers(int chain_id)
> >> > channels = dma_linked_lch[chain_id].linked_dmach_q;
> >> >
> >> > /*
> >> > - * DMA Errata:
> >> > - * Special programming model needed to disable DMA before end of block
> >> > + * DMA Errata: i88
> >> > + * Special programming model needed
> >> > + * to disable DMA before end of block
> >> > */
> >> > sys_cf = dma_read(OCP_SYSCONFIG);
> >> > - l = sys_cf;
> >> > - /* Middle mode reg set no Standby */
> >> > - l &= ~((1 << 12)|(1 << 13));
> >> > - dma_write(l, OCP_SYSCONFIG);
> >> > + if (cpu_is_omap2430() || (omap_rev() == OMAP3430_REV_ES1_0)) {
> >> > + l = sys_cf;
> >> > + /* Middle mode reg set no Standby */
> >> > + l &= ~((1 << 12)|(1 << 13));
> >> > + dma_write(l, OCP_SYSCONFIG);
> >> > + }
> >> >
> >> > for (i = 0; i < dma_linked_lch[chain_id].no_of_lchs_linked; i++) {
> >> >
> >
> > What about other omaps? It seems that we're currently doing the workaround
> > for all omaps. Seems like "Tested on 3430 SDP" is not quite safe enough
> > for making change that might affect other omaps.
> >
> > Tony
>
> The Errata document specifically mentions that the workaround is
> needed only for
> 3430 ES1.0 or earlier. I had actually tested on the ES2.0. [Now that
> you have mentioned it,
> I tested on 3630 and 4430 as well]
> Let me know if you need more test results or information.
Uhh. The old code does this for all omaps. I rather trust the existing
than TI documentation. What about 2420 and 2430?
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-03 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 11:35 [PATCH] dma: fix scope of errata i88 upto 3430ES1.0 Venkatraman S
2010-04-05 14:26 ` Shilimkar, Santosh
2010-04-05 15:19 ` Venkatraman S
2010-04-05 15:36 ` [PATCH v2] " Venkatraman S
2010-04-19 10:51 ` Venkatraman S
2010-04-21 21:14 ` Tony Lindgren
2010-04-26 14:51 ` Venkatraman S
2010-05-03 16:35 ` Tony Lindgren [this message]
2010-05-04 6:50 ` Venkatraman S
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=20100503163504.GP29604@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=svenkatr@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;
as well as URLs for NNTP newsgroup(s).