linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: manjugk@ti.com (G, Manjunath Kondaiah)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/9] OMAP: DMA: hwmod and DMA as platform device
Date: Wed, 15 Dec 2010 07:29:46 +0530	[thread overview]
Message-ID: <20101215015946.GA6725@manju-desktop> (raw)
In-Reply-To: <87tyifn7ed.fsf@deeprootsystems.com>

Kevin/Tony,

On Tue, Dec 14, 2010 at 05:37:14PM -0800, Kevin Hilman wrote:
> "G, Manjunath Kondaiah" <manjugk@ti.com> writes:
> 
> > Patch series to convert DMA library into platform driver using platform
> > device model and adapting hwmod for omap2+.
> 
> After the OMAP1 fixup for PATCH 7/9,
> 
> Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
> 
> and
> 
> Tested-by: Kevin Hilman <khilman@deeprootsystems.com>
> 
> on omap1611/OSK, omap3430/n900 and omap4430/panda
> 
> Tested using a memory-to-memory DMA test which tests all available
> channels, and tests linking all the channels together.
> 
> I resurected an older DMA test that I wrote sometime around 2004, and
> lost somehow (thankfully, Tony still had a copy.)  I've updated it
> slightly and created a git repo for it now that it is known working on
> OMAP1, 2, 3 and 4.
> 
>        git://gitorious.org/omap-test/dmatest.git

Nice. TI too has exhaustive memory to memory test cases available at
public git repo(includes other driver test cases as well):

git://dev.omapzoom.org/pub/scm/richo/device_driver_test.git

> 
> It's a bit hacky as you have to manually edit the Makefile to build an
> out of tree module, but it does work.

Thanks for fixing OMAP1 irq issues and testing the same. I hope we will
have OSK5912 for future patches and we will test all upstream patches on
OMAP1 too.

-Manjunath

  parent reply	other threads:[~2010-12-15  1:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1291434246-30716-1-git-send-email-manjugk@ti.com>
2010-12-07 11:04 ` [PATCH v1 0/9] OMAP: DMA: hwmod and DMA as platform device G, Manjunath Kondaiah
2010-12-14 23:19 ` Tony Lindgren
2010-12-15  0:18   ` Kevin Hilman
     [not found] ` <1291434246-30716-8-git-send-email-manjugk@ti.com>
2010-12-15  0:40   ` [PATCH v1 7/9] OMAP1: DMA: Implement in platform device model Kevin Hilman
2010-12-15  0:55     ` Kevin Hilman
2010-12-15  1:04       ` Tony Lindgren
2010-12-15  2:01         ` G, Manjunath Kondaiah
2010-12-15  2:44           ` Tony Lindgren
2010-12-15  1:37 ` [PATCH v1 0/9] OMAP: DMA: hwmod and DMA as platform device Kevin Hilman
2010-12-15  1:55   ` Tony Lindgren
2010-12-15  2:02     ` Kevin Hilman
2010-12-15  2:08       ` Tony Lindgren
2010-12-15  1:59   ` G, Manjunath Kondaiah [this message]
     [not found] ` <1291434246-30716-4-git-send-email-manjugk@ti.com>
2010-12-15  2:25   ` [PATCH v1 3/9] OMAP2420: hwmod data: add system DMA Paul Walmsley
2010-12-15 11:09     ` G, Manjunath Kondaiah
2010-12-15 12:15       ` [PATCH v1 3/9] OMAP2420: hwmod data: add system DMA] G, Manjunath Kondaiah
2010-12-15 15:39         ` Paul Walmsley
     [not found] ` <1291434246-30716-5-git-send-email-manjugk@ti.com>
2010-12-15  2:27   ` [PATCH v1 4/9] OMAP2430: hwmod data: add system DMA Paul Walmsley
2010-12-15 10:59     ` G, Manjunath Kondaiah
2010-12-15 15:14       ` Paul Walmsley
2010-12-15 15:53         ` G, Manjunath Kondaiah

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=20101215015946.GA6725@manju-desktop \
    --to=manjugk@ti.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).