From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "ext G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: Jarkko Nikula <jhnikula@gmail.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 v3 1/2] omap: dma: Fix buffering disable bit setting for omap24xx
Date: Mon, 4 Oct 2010 10:15:35 +0300 [thread overview]
Message-ID: <201010041015.35457.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402DB90C8C2@dbde02.ent.ti.com>
On Monday 04 October 2010 09:23:18 ext G, Manjunath Kondaiah wrote:
> No errata numbers numbers used with TI errata documents till omap2430.
> Errata numbers avaialable from omap3430 onwards.
>
> > For OMAP3 the errata number is i541, but I do not know the
> > iXYZ number for OMAP2 class.
>
> Being said that no errata numbers for omap2 class, it's ok to use
> omap3 errata numbers for common errata(like your patch 2/2)
Thanks,
we are going to use the same errata ID for OMAP2, and OMAP3, but going to use
different workaround for them:
OMAP2: disable buffering
OMAP3: implement the workaround as it is in the errata
So, as Tony suggested, I'll add the errata handling, and
we are going to have:
DMA_ERRATA_i541_OMAP2, and DMA_ERRATA_i541_OMAP3 to differentiate the different
workarounds. We can than experiment, and we might use the OMAP3 workaround for
OMAP2 as well.
I'll send the v4 series shortly (after testing).
--
Péter
--
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-10-04 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 12:36 [PATCH v3 0/2] OMAP2/3: DMA: FIFO drain errata fixes Peter Ujfalusi
2010-10-01 12:36 ` [PATCH v3 1/2] omap: dma: Fix buffering disable bit setting for omap24xx Peter Ujfalusi
2010-10-02 4:42 ` G, Manjunath Kondaiah
2010-10-04 5:43 ` Jarkko Nikula
2010-10-04 5:55 ` G, Manjunath Kondaiah
2010-10-04 6:15 ` Peter Ujfalusi
2010-10-04 6:23 ` G, Manjunath Kondaiah
2010-10-04 7:15 ` Peter Ujfalusi [this message]
2010-10-04 7:36 ` G, Manjunath Kondaiah
2010-10-04 7:41 ` Peter Ujfalusi
2010-10-01 12:36 ` [PATCH v3 2/2] OMAP3: DMA: Errata: sDMA FIFO draining does not finish Peter Ujfalusi
2010-10-01 15:04 ` Shilimkar, Santosh
2010-10-02 4:43 ` G, Manjunath Kondaiah
2010-10-01 16:55 ` Tony Lindgren
2010-10-01 23:23 ` 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=201010041015.35457.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=manjugk@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.