From: Anatolij Gustschin <agust@denx.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 1/2] dmaengine: mpc512x_dma: use generic DMA DT bindings
Date: Tue, 9 Apr 2013 13:42:36 +0200 [thread overview]
Message-ID: <20130409134236.4d1bffa6@crub> (raw)
In-Reply-To: <5162A017.8010102@metafoo.de>
On Mon, 08 Apr 2013 12:46:47 +0200
Lars-Peter Clausen <lars@metafoo.de> wrote:
...
> > +static struct dma_chan *mpc_dma_xlate(struct of_phandle_args *dma_spec,
> > + struct of_dma *ofdma)
> > +{
> > + int count = dma_spec->args_count;
> > + struct mpc_dma *mdma = ofdma->of_dma_data;
> > + struct mpc_dma_filter_args fargs;
> > + dma_cap_mask_t cap;
> > +
> > + if (!mdma)
> > + return NULL;
> > +
> > + if (count != 1)
> > + return NULL;
> > +
> > + fargs.mdma = mdma;
> > + fargs.chan_id = dma_spec->args[0];
> > +
> > + dma_cap_zero(cap);
> > + dma_cap_set(DMA_SLAVE, cap);
> > +
> > + return dma_request_channel(cap, mpc_dma_filter, &fargs);
> > +}
> > +
>
> This is more or less the same as the generic of_dma_xlate_by_chan_id
> function I posted about two weeks ago:
> https://patchwork.kernel.org/patch/2331091/
Thanks. I can use the generic of_dma_xlate_by_chan_id() when above patch
will be accepted.
Anatolij
prev parent reply other threads:[~2013-04-09 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 16:17 [PATCH 1/2] dmaengine: mpc512x_dma: use generic DMA DT bindings Anatolij Gustschin
2013-03-31 16:18 ` [PATCH 2/2] dmaengine: mpc512x: add slave sg and device control operations Anatolij Gustschin
2013-05-16 13:04 ` [2/2] " Alexander Popov
[not found] ` <1364746680-6564-1-git-send-email-agust-ynQEQJNshbs@public.gmane.org>
2013-04-02 18:22 ` [PATCH 1/2] dmaengine: mpc512x_dma: use generic DMA DT bindings Vinod Koul
2013-04-02 19:01 ` Arnd Bergmann
2013-04-08 10:46 ` Lars-Peter Clausen
2013-04-09 11:42 ` Anatolij Gustschin [this message]
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=20130409134236.4d1bffa6@crub \
--to=agust@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--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).