devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: devicetree-discuss@lists.ozlabs.org
Cc: Padmavathi Venna <padma.v@samsung.com>,
	padma.kvr@gmail.com, linux-samsung-soc@vger.kernel.org,
	alsa-devel@alsa-project.org, jassisinghbrar@gmail.com,
	kgene.kim@samsung.com, swarren@nvidia.com,
	boojin.kim@samsung.com, sbkim73@samsung.com,
	broonie@opensource.wolfsonmicro.com, vinod.koul@intel.com
Subject: Re: [PATCH 1/4] DMA: PL330: Add xlate function
Date: Mon, 28 Jan 2013 14:58:15 +0000	[thread overview]
Message-ID: <201301281458.15219.arnd@arndb.de> (raw)
In-Reply-To: <1358508824-20352-2-git-send-email-padma.v@samsung.com>

On Friday 18 January 2013, Padmavathi Venna wrote:
> +struct dma_chan *of_dma_pl330_xlate(struct of_phandle_args *dma_spec,
> +                                               struct of_dma *ofdma)
> +{
> +       int count = dma_spec->args_count;
> +       struct of_dma_filter_info *info = ofdma->of_dma_data;
> +
> +       if (!info || !info->filter_fn)
> +               return NULL;
> +
> +       if (count != 1)
> +               return NULL;
> +
> +       return dma_request_channel(info->dma_cap, info->filter_fn, dma_spec);
> +}
> +EXPORT_SYMBOL_GPL(of_dma_pl330_xlate);

It seems a little sad that we still have to use dma_request_channel()
to implement this, when that function will go off searching all channels
and pass them tino the filter, which then has to look for the device node
and match it with each channel. We already know the controller and should
just be able to get a channel for it, although I don't exactly know how
that is done.

Further, your function is almost identical to the of_dma_simple_xlate
function. Can't you use that one instead?

	Arnd

  reply	other threads:[~2013-01-28 14:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 11:33 [PATCH 0/4] Add generic DMA DT binding support Padmavathi Venna
2013-01-18 11:33 ` [PATCH 1/4] DMA: PL330: Add xlate function Padmavathi Venna
2013-01-28 14:58   ` Arnd Bergmann [this message]
2013-01-29  9:03     ` Padma Venkat
2013-01-29 10:27       ` Arnd Bergmann
2013-01-18 11:33 ` [PATCH 2/4] DMA: PL330: Register the DMA controller with the generic DMA helpers Padmavathi Venna
2013-01-28 14:51   ` Arnd Bergmann
2013-01-28 17:54     ` Jon Hunter
2013-01-28 18:01       ` Arnd Bergmann
2013-01-28 21:11         ` Jon Hunter
2013-01-18 11:33 ` [PATCH 3/4] ARM: dts: Add #dma-cells for generic dma binding support Padmavathi Venna
2013-01-28 14:47   ` Arnd Bergmann
2013-01-29  8:53     ` Padma Venkat
2013-01-18 11:33 ` [PATCH 4/4] DMA: PL330: Modify pl330 filter based on new generic dma dt bindings Padmavathi Venna
2013-01-28 13:43 ` [PATCH 0/4] Add generic DMA DT binding support Vinod Koul
2013-01-28 15:16   ` Arnd Bergmann

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=201301281458.15219.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=boojin.kim@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=padma.kvr@gmail.com \
    --cc=padma.v@samsung.com \
    --cc=sbkim73@samsung.com \
    --cc=swarren@nvidia.com \
    --cc=vinod.koul@intel.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).