linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 1/2] of: Add generic device tree DMA helpers
Date: Wed, 19 Sep 2012 09:10:22 -0500	[thread overview]
Message-ID: <5059D24E.20707@gmail.com> (raw)
In-Reply-To: <1347662517-4210-2-git-send-email-jon-hunter@ti.com>

On 09/14/2012 05:41 PM, Jon Hunter wrote:
> This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
> to add some basic helpers to retrieve a DMA controller device_node and the
> DMA request/channel information.

[snip]

> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> Reviewed-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
> ---
>  Documentation/devicetree/bindings/dma/dma.txt |   81 +++++++++
>  drivers/of/Makefile                           |    2 +-
>  drivers/of/dma.c                              |  219 +++++++++++++++++++++++++

We've been moving in the direction of not putting subsystem related code
under drivers/of, but rather with the subsystem. Although in some cases
(i2c), the maintainers didn't want the OF code there.

In any case, I guess this will go thru Vinod's tree, so:

Acked-by: Rob Herring <rob.herring@calxeda.com>

  parent reply	other threads:[~2012-09-19 14:10 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 22:41 [PATCH V6 0/2] of: Add generic device tree DMA helpers Jon Hunter
2012-09-14 22:41 ` [PATCH V6 1/2] " Jon Hunter
2012-09-14 22:46   ` Stephen Warren
2012-09-15  0:14   ` Russell King - ARM Linux
2012-09-17 20:42     ` Arnd Bergmann
2012-09-17 23:06       ` David Brown
2012-09-18 12:50         ` Arnd Bergmann
2012-09-18 22:19       ` Mitch Bradley
2012-09-18 22:32         ` Russell King - ARM Linux
2012-09-19 11:09         ` Arnd Bergmann
2012-09-19 14:40           ` Mitch Bradley
2012-09-19 13:52   ` Matt Porter
2012-09-19 14:07   ` Matt Porter
2012-09-19 14:24     ` Arnd Bergmann
2012-09-19 14:36       ` Rob Herring
2012-09-19 14:40         ` Matt Porter
2012-09-19 14:50           ` Arnd Bergmann
2012-09-19 21:25       ` Mitch Bradley
2012-09-19 14:10   ` Rob Herring [this message]
2012-09-14 22:41 ` [PATCH V6 2/2] dmaengine: add helper function to request a slave DMA channel Jon Hunter
2012-09-17  3:33   ` Vinod Koul
2012-09-17 11:59     ` Arnd Bergmann
2012-09-17 22:36       ` Russell King - ARM Linux
2012-09-18  3:13         ` Vinod Koul
2012-09-18 13:21           ` Matt Porter
2012-09-18 15:20             ` Arnd Bergmann
2012-09-18 18:10               ` Russell King - ARM Linux
2012-09-24 22:25           ` Jon Hunter
2012-09-25  4:35             ` Vinod Koul
2012-10-16  2:43               ` Shawn Guo
2012-10-16  2:39                 ` Vinod Koul
2012-11-09 20:01                   ` Jon Hunter
2012-11-16  1:37                     ` Vinod Koul
2012-11-16  8:39                       ` Nicolas Ferre
2012-11-16 15:45                       ` Jon Hunter
2012-11-28 17:06                         ` Vinod Koul
2012-12-19 17:12                       ` Jon Hunter
2012-12-20 14:57                         ` Vinod Koul
2012-09-18  3:00       ` Vinod Koul

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=5059D24E.20707@gmail.com \
    --to=robherring2@gmail.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).