public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] of: Add generic device tree DMA helpers
Date: Sun, 18 Mar 2012 20:13:22 +0000	[thread overview]
Message-ID: <201203182013.22790.arnd@arndb.de> (raw)
In-Reply-To: <20120317094059.7C2333E08E2@localhost>

On Saturday 17 March 2012, Grant Likely wrote:
> > +static LIST_HEAD(of_dma_list);
> > +
> > +struct of_dma {
> > +     struct list_head of_dma_controllers;
> > +     struct device_node *of_node;
> > +     int of_dma_n_cells;
> > +     int (*of_dma_xlate)(struct of_phandle_args *dma_spec, void *data);
> > +};
> 
> This _xlate is nearly useless as a generic API.  It solves the problem for
> the specific case where the driver is hard-coded to know which DMA engine
> to talk to, but since the returned data doesn't provide any context, it
> isn't useful if there are multiple DMA controllers to choose from.
> 
> The void *data pointer must be replaced with a typed structure so that
> context can be returned.

I've read up a bit more on how the existing drivers use the filter
functions, it seems there are multiple classes of them, the classes
that I've encountered are:

1. matches on chan->device pointer and/or chan_id
   (8 drivers)
2. will match anything
   (6 drivers)
3. requires specific dma engine driver, then behaves like 1 or 2
   (8 drivers, almost all freescale)
4. one of a kind, matches resource name string or device->dev_id
   (two drivers)
5. filter function and data both provided by platform code,
   platform picks dmaengine driver.
   (4 amba pl* drivers, used on ARM, ux500, ...)

The last category is interesting because here, the dmaengine
driver (pl330, coh901318, sirf-dma, ste_dma40) provides the filter
function while in the other cases that is provided by the device
driver! Out of these, the ste_dma40 is special because it's the
only one where the data is a complex data structure describing the
constraints on the driver, while all others just find the right
channel.

Some drivers also pass assign driver specific data to chan->private.

I would hope that we can all make them use something like
     struct dma_channel *of_dma_request_channel(struct of_node*,
					int index, void *driver_data);
with an appropriate common definition behind it. In the cases
where the driver can just match anything, I'd assume that all
channels are equal, so #dma-cells would be 0. For the ste_dma40,
#dma-cells needs to cover all of stedma40_chan_cfg. In most
other cases, #dma-cells can be 1 and just enumerate the channels,
unless we want to simplify the cases that Russell mentioned where
we want to keep a two stage mapping channel identifiers and physical
channel numbers.

How about an implementation like this:?

typedef bool dma_filter_simple(struct dma_chan *chan, void *filter_param)
{
	/* zero #dma-cells, accept anything */
	return true;
}

struct dma_channel *of_dma_request_channel(struct of_node*, int index,
					dma_cap_mask_t *mask,
					void *driver_data)
{
	struct of_phandle_args dma_spec;
	struct dma_device *device;
	struct dma_chan *chan = NULL;
	dma_filter_fn *filter;

	ret = of_parse_phandle_with_args(np, "dma-request", "#dma-cells",
					 index, &dma_spec);

	device = dma_find_device(dma_spec->np);
	if (!device)
		goto out;

	if (dma_spec->args_count == 0)
		filter = dma_filter_simple;
	else
		filter = device->dma_dt_filter; /* new member */

	chan = private_candidate(mask, device, filter, dma_spec->args);

	if (chan && !chan->private)
		chan->private = driver_data;
out:
	return chan;
}

	Arnd

  reply	other threads:[~2012-03-18 20:13 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 17:29 [RFC PATCH 1/2] of: Add generic device tree DMA helpers Cousson, Benoit
2012-01-27 18:13 ` Stephen Warren
2012-01-27 20:36   ` Cousson, Benoit
2012-01-28 18:12     ` Grant Likely
2012-01-28 18:06 ` Grant Likely
2012-01-31 21:26   ` Cousson, Benoit
2012-02-02  4:52     ` Grant Likely
2012-01-31 23:09   ` Russell King - ARM Linux
2012-02-01 10:50     ` Cousson, Benoit
2012-02-02  8:45       ` Russell King - ARM Linux
2012-02-02  8:54         ` Cousson, Benoit
2012-02-22 10:59 ` Nicolas Ferre
2012-02-23 10:03   ` Cousson, Benoit
2012-02-23 15:51     ` Nicolas Ferre
2012-02-23 15:57       ` Cousson, Benoit
2012-02-27 13:09         ` Nicolas Ferre
2012-02-27 14:22           ` Cousson, Benoit
2012-02-27 17:28             ` Nicolas Ferre
2012-02-29 14:54 ` [RFC PATCH] of: DMA helpers: manage generic requests specification Nicolas Ferre
2012-02-29 20:54   ` Stephen Warren
2012-03-05 13:14     ` Cousson, Benoit
2012-03-05 18:30       ` Stephen Warren
2012-03-05 19:57         ` Russell King - ARM Linux
2012-03-05 10:55   ` Cousson, Benoit
2012-03-05 15:36   ` Grant Likely
2012-03-14 17:47     ` Nicolas Ferre
2012-03-14 18:16       ` Stephen Warren
2012-03-15  8:38 ` [PATCH] of: Add generic device tree DMA helpers Nicolas Ferre
2012-03-15  9:22   ` Arnd Bergmann
2012-03-15  9:26     ` Russell King - ARM Linux
2012-03-15 10:09       ` Arnd Bergmann
2012-03-17  9:42       ` Grant Likely
2012-03-17 16:03         ` Arnd Bergmann
2012-03-18  9:08           ` Grant Likely
2012-03-15 10:27     ` Thierry Reding
2012-03-17 10:47       ` Grant Likely
2012-03-18  9:22         ` Thierry Reding
2012-03-18 15:10           ` Arnd Bergmann
2012-03-18 18:22           ` Grant Likely
2012-03-19 13:02         ` Mark Brown
2012-03-19 15:01           ` Arnd Bergmann
2012-03-19 15:07             ` Stephen Warren
2012-03-19 15:45               ` Arnd Bergmann
2012-03-19 16:54                 ` Stephen Warren
2012-03-15 16:30     ` Cousson, Benoit
2012-03-15 19:57       ` Russell King - ARM Linux
2012-03-15 20:41         ` Arnd Bergmann
2012-03-15 21:39           ` Cousson, Benoit
2012-03-15 21:55             ` Russell King - ARM Linux
2012-03-16  9:56               ` Arnd Bergmann
2012-03-20 14:02             ` Matt Porter
2012-03-15 23:45         ` Nicolas Pitre
2012-03-16 10:03   ` Arnd Bergmann
2012-03-16 11:19     ` Cousson, Benoit
2012-03-16 12:04       ` Arnd Bergmann
2012-03-16 13:28         ` Cousson, Benoit
2012-03-16 13:36           ` Nicolas Ferre
2012-03-17  9:40   ` Grant Likely
2012-03-18 20:13     ` Arnd Bergmann [this message]
2012-03-18 20:44       ` Grant Likely
2012-03-18 21:58         ` Arnd Bergmann
2012-03-18 22:12           ` Arnd Bergmann
2012-03-19 13:37       ` Nicolas Ferre
2012-03-19 15:20         ` Russell King - ARM Linux
2012-03-19 15:58           ` Cousson, Benoit
2012-03-19 13:30     ` Nicolas Ferre
2012-03-19 14:06       ` Arnd Bergmann
2012-03-19 15:33         ` Russell King - ARM Linux
2012-03-19 16:11           ` Arnd Bergmann
2012-03-19 18:06             ` Jassi Brar
2012-03-19 16:31           ` Nicolas Ferre
2012-03-19 17:49             ` Cousson, Benoit
2012-03-19 14:45       ` Grant Likely
2012-03-20 14:54         ` Nicolas Ferre
2012-03-20 10:13   ` [PATCH v2 1/2] " Nicolas Ferre
2012-03-20 10:13     ` [PATCH 2/2] of: selftest/dma: Add selftest for new DT DMA request helpers Nicolas Ferre
2012-03-20 14:16       ` Grant Likely
2012-03-20 10:17     ` [PATCH] of: dma/fixup Nicolas Ferre
2012-03-20 13:03     ` [PATCH v2 1/2] of: Add generic device tree DMA helpers Arnd Bergmann
2012-03-20 15:38     ` Stephen Warren

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=201203182013.22790.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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