All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2 v2] dmaengine: remove Renesas Audio DMAC peri peri
Date: Wed, 18 Mar 2015 11:32:27 +0000	[thread overview]
Message-ID: <20150318112027.GK32683@intel.com> (raw)
In-Reply-To: <87oanzf3r1.wl%kuninori.morimoto.gx@renesas.com>

On Thu, Mar 12, 2015 at 12:39:49AM +0000, Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> 
> Renesas R-Car sound (= rsnd) needs 2 DMAC which are called as
> Audio DMAC (= 1st DMAC) and Audio DMAC peri peri (2nd DMAC).
> And rsnd had assumed that 1st / 2nd DMACs are implemented as DMAEngine.
> But, in result of DMA ML discussion, 2nd DMAC was concluded that it is
> not a general purpose DMAC (2nd DMAC is for Device to Device inside
> sound system). Additionally, current DMAEngine can't support Device to
> Device, and we don't have correct DT bindings for it at this point.
> So the easiest solution for it is that move it from DMAEngine to rsnd
> driver.
> Audio DMAC peri peri on DMAEngine is no longer needed. remove it.
Applied, thanks

-- 
~Vinod

WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v2] dmaengine: remove Renesas Audio DMAC peri peri
Date: Wed, 18 Mar 2015 16:50:27 +0530	[thread overview]
Message-ID: <20150318112027.GK32683@intel.com> (raw)
In-Reply-To: <87oanzf3r1.wl%kuninori.morimoto.gx@renesas.com>

On Thu, Mar 12, 2015 at 12:39:49AM +0000, Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> 
> Renesas R-Car sound (= rsnd) needs 2 DMAC which are called as
> Audio DMAC (= 1st DMAC) and Audio DMAC peri peri (2nd DMAC).
> And rsnd had assumed that 1st / 2nd DMACs are implemented as DMAEngine.
> But, in result of DMA ML discussion, 2nd DMAC was concluded that it is
> not a general purpose DMAC (2nd DMAC is for Device to Device inside
> sound system). Additionally, current DMAEngine can't support Device to
> Device, and we don't have correct DT bindings for it at this point.
> So the easiest solution for it is that move it from DMAEngine to rsnd
> driver.
> Audio DMAC peri peri on DMAEngine is no longer needed. remove it.
Applied, thanks

-- 
~Vinod

  parent reply	other threads:[~2015-03-18 11:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  0:39 [PATCH 0/2 v2] dmaengine: remove Renesas Audio DMAC peri peri Kuninori Morimoto
2015-03-12  0:39 ` Kuninori Morimoto
2015-03-12  0:39 ` [PATCH 1/2 " Kuninori Morimoto
2015-03-12  0:39   ` Kuninori Morimoto
2015-03-12  8:54   ` Arnd Bergmann
2015-03-12  8:54     ` Arnd Bergmann
2015-03-18 11:20   ` Vinod Koul [this message]
2015-03-18 11:32     ` Vinod Koul
2015-03-12  0:40 ` [PATCH 2/2 v2] ARM: configs: remove all CONFIG_RCAR_AUDMAC_PP from ARM defconfigs Kuninori Morimoto
2015-03-12  0:40   ` Kuninori Morimoto
2015-03-18 11:21   ` Vinod Koul
2015-03-18 11:33     ` Vinod Koul
2015-03-18 23:54     ` Kuninori Morimoto
2015-03-18 23:54       ` Kuninori Morimoto
2015-03-19  1:25       ` Simon Horman
2015-03-19  1:25         ` Simon Horman
2015-03-19  5:03         ` Kuninori Morimoto
2015-03-19  5:03           ` Kuninori Morimoto

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=20150318112027.GK32683@intel.com \
    --to=vinod.koul@intel.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.