SUPERH platform development
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3 v3][RFC] dmaengine: rcar-audmapp: calculate chcr via src/dst addr
Date: Mon, 16 Feb 2015 19:47:00 +0000	[thread overview]
Message-ID: <7874620.5qCoKeFt9V@wuerfel> (raw)
In-Reply-To: <87mw4xey70.wl%kuninori.morimoto.gx@renesas.com>

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.

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

  parent reply	other threads:[~2015-02-16 19:47 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 [this message]
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

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=7874620.5qCoKeFt9V@wuerfel \
    --to=arnd@arndb.de \
    --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