Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Magnus <magnus.damm@gmail.com>, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 0/4] ARM/ARM64: renesas: Tidyup Audio-DMAC channel for DVC
Date: Tue, 7 Mar 2017 07:52:08 +0100	[thread overview]
Message-ID: <20170307065207.GE14208@verge.net.au> (raw)
In-Reply-To: <878toh8xru.wl%kuninori.morimoto.gx@renesas.com>

On Tue, Mar 07, 2017 at 05:27:47AM +0000, Kuninori Morimoto wrote:
> 
> Hi Simon
> 
> These fixup DVC Audio-DMAC channel assignment
> which was not same as SRC/SSI policy.
> Because of this (is a little bit excessive),
> current Playback/Capture on each platform
> (= Lager/Koelsch/Gose/Salvator) are using same
> Audio-DMAC0. Playback/Capture uses different
> Audio-DMAC is more make sense for me.

Thanks Morimoto-san,

I have queued these up with the minor tweak to the subject of the last
patch mentioned below.

> Kuninori Morimoto (4):
>   ARM: dts: r8a7790: Tidyup Audio-DMAC channel for DVC
>   ARM: dts: r8a7791: Tidyup Audio-DMAC channel for DVC
>   ARM: dts: r8a7793: Tidyup Audio-DMAC channel for DVC
>   arm64: renesas: r8a7795: Tidyup Audio-DMAC channel for DVC

s/renesas/dts/

  parent reply	other threads:[~2017-03-07  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  5:27 [PATCH 0/4] ARM/ARM64: renesas: Tidyup Audio-DMAC channel for DVC Kuninori Morimoto
2017-03-07  5:28 ` [PATCH 1/4] ARM: dts: r8a7790: " Kuninori Morimoto
2017-03-07  5:29 ` [PATCH 2/4] ARM: dts: r8a7791: " Kuninori Morimoto
2017-03-07  5:29 ` [PATCH 3/4] ARM: dts: r8a7793: " Kuninori Morimoto
2017-03-07  5:30 ` [PATCH 4/4] arm64: renesas: r8a7795: " Kuninori Morimoto
2017-03-07  6:52 ` Simon Horman [this message]
2017-03-08  6:18   ` [PATCH 0/4] ARM/ARM64: renesas: " Kuninori Morimoto
2017-03-10  9:24     ` Simon Horman

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=20170307065207.GE14208@verge.net.au \
    --to=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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