From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: linux-omap@vger.kernel.org, Jarkko Nikula <jhnikula@gmail.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH v3 2/2] OMAP3: DMA: Errata: sDMA FIFO draining does not finish
Date: Fri, 1 Oct 2010 16:23:42 -0700 [thread overview]
Message-ID: <20101001232342.GK3117@atomide.com> (raw)
In-Reply-To: <20101001165542.GS3117@atomide.com>
* Tony Lindgren <tony@atomide.com> [101001 09:47]:
>
> Thinking about moving to use dmaengine.c, we should not use
> cpu_is_omapxxxx except during the platform init.
>
> Can you please change this to be in u32 flags in dma.c that get set during
> the init only for omap3? Then we can have something like:
>
> #define OMAP_DMA_ERRATA_AAA (1 << 2)
> #define OMAP_DMA_ERRATA_BBB (1 << 0)
> ...
BTW, can you also please Cc linux-arm-kernel on your patches?
That way I don't need to repost them.
Also, we might be able to get these two in as fixes.
Regards,
Tony
prev parent reply other threads:[~2010-10-01 23:23 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
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 [this message]
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=20101001232342.GK3117@atomide.com \
--to=tony@atomide.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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).