public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: Tony Lindgren <tony@atomide.com>
Subject: [PATCH 0/3] DMA clean-up for multi-boot
Date: Wed, 30 Apr 2008 10:13:58 -0700	[thread overview]
Message-ID: <1209575641-25613-1-git-send-email-tony@atomide.com> (raw)
In-Reply-To: omap-dma-2008-04-30

Hi all,

Here are three patches to clean DMA code to support multi-boot
better. I have made quick testing on 24xx and 34xx only so far,
and things seem to work.

I will also do more testing, but I would appreciate if people would
give them a quick spin and see if anything breaks. Functionality
should be same as earlier.

I've removed direct DMA register access in few places such as
omap-hw.c, usb-udc.c, and various audio drivers. So especially
those areas should be tested carefully.

Regards,

Tony


             reply	other threads:[~2008-04-30 17:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 17:13 Tony Lindgren [this message]
2008-04-30 17:13 ` [PATCH 1/3] ARM: OMAP: Make DMA channels dynamic for multi-boot Tony Lindgren
2008-04-30 17:14   ` [PATCH 2/3] ARM: OMAP: Remove __REG access in DMA code Tony Lindgren
2008-04-30 17:14     ` [PATCH 3/3] ARM: OMAP: DMA clean-up Tony Lindgren
2008-04-30 18:00 ` [PATCH 0/3] DMA clean-up for multi-boot Gadiyar, Anand
2008-05-02 15:15 ` Gadiyar, Anand
2008-05-02 18:11   ` Tony Lindgren
2008-05-16 17:34     ` Tony Lindgren
2008-05-05 10:14 ` Jarkko Nikula
2008-05-05 23:27   ` public git l2 cache off Woodruff, Richard
2008-05-06  5:38     ` Koen Kooi
2008-05-06  6:58       ` Koen Kooi
2008-05-06 15:06       ` Woodruff, Richard
2008-05-06 16:20         ` Koen Kooi
2008-05-06 16:51           ` Woodruff, Richard
2008-05-06 17:01             ` Koen Kooi
2008-05-06 21:25               ` Tony Lindgren
2008-05-07  7:42               ` Syed Mohammed, Khasim
2008-05-07 10:51                 ` Koen Kooi
2008-05-10  8:14             ` Dirk Behme
2008-05-06 18:13         ` Dirk Behme

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=1209575641-25613-1-git-send-email-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.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