From: Vinod Koul <vinod.koul@intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3 v3][RFC] dmaengine: rcar-audmapp: calculate chcr via src/dst addr
Date: Wed, 18 Feb 2015 13:43:50 +0000 [thread overview]
Message-ID: <20150218133150.GV21387@intel.com> (raw)
In-Reply-To: <87mw4xey70.wl%kuninori.morimoto.gx@renesas.com>
On Mon, Feb 16, 2015 at 08:47:00PM +0100, Arnd Bergmann wrote:
> On Monday 09 February 2015 01:37:41 Kuninori Morimoto wrote:
> >
> > Hi Vinod, Arnd
> >
> > Can I have feedback from you about below mail, and this patch ?
> >
> > http://thread.gmane.org/gmane.linux.ports.sh.devel/41063/focusC372
>
> I had the chance to discuss this in more depth with Laurent last
> week. What it basically comes down to is that you try to do something
> that the existing DT binding and slave API does not support: we
> only really do DMA_DEV_TO_MEM or DMA_MEM_TO_DEV, but not DMA_DEV_TO_DEV.
For the record, device_prep_slave_sg() can do DMA_DEV_TO_DEV. That is the
sole reason why dma_slave_config has both the directions for every field.
HTH
--
~Vinod
> To properly support this with the dmaengine API, we would likely first
> need to extend the generic DT binding, and then implement the driver
> to use that extended binding.
>
> The easiest way out however seems to be to move the audmapp
> implementation into the rcar audio driver itself. As Laurent pointed
> out, it is not really a general-purpose dmaengine anyway and it
> only ever gets used by one driver, so we could not find any downsides.
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
prev parent reply other threads:[~2015-02-18 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 4:25 [PATCH 0/3 v3][RFC] dmaengine: rcar-audmapp: calculate chcr via src/dst addr Kuninori Morimoto
2015-02-09 1:37 ` Kuninori Morimoto
2015-02-16 19:47 ` Arnd Bergmann
2015-02-17 0:10 ` Kuninori Morimoto
2015-02-17 14:09 ` Arnd Bergmann
2015-02-17 18:20 ` Nicolin Chen
2015-02-18 0:41 ` Kuninori Morimoto
2015-02-18 13:43 ` Vinod Koul [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=20150218133150.GV21387@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).