public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Jiada Wang <jiada_wang@mentor.com>
Cc: horms@verge.net.au, magnus.damm@gmail.com, robh+dt@kernel.org,
	mark.rutland@arm.com, linux-renesas-soc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	geert@linux-m68k.org
Subject: Re: [PATCH v3 0/3] rsnd: dts: change to use extended audio dmac register
Date: 19 Mar 2019 15:07:15 +0900	[thread overview]
Message-ID: <87va0fs92d.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20190319055705.24115-1-jiada_wang@mentor.com>


Hi Jiada

> According to user reference manual for R-CAR H3, M3-W and M3-N SoCs,
> in order to access busif4 ~ busif7, extended audio dmac registers
> (PDMASAREn, PDMADAREn, PDMACHCREn)
> need to be used, rather than basic audio dmac registers
> (PDMASARn, PDMADARn, PDMACHCRn)
> 
> Now DT bindings has stated that extended Audio dmac register set need
> to be used when available with patch
> https://patchwork.kernel.org/patch/10856905/
> 
> This patch set updates H3 (= r8a7795), M3-W (= r8a7796) and M3-N (=r8a77965)
> to use extended audio dmac register set.

For all patches

Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>

  parent reply	other threads:[~2019-03-19  6:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  5:57 [PATCH v3 0/3] rsnd: dts: change to use extended audio dmac register Jiada Wang
2019-03-19  5:57 ` [PATCH v3 1/3] arm64: dts: renesas: r8a7795: " Jiada Wang
2019-03-19  5:57 ` [PATCH v3 2/3] arm64: dts: renesas: r8a7796: " Jiada Wang
2019-03-19  5:57 ` [PATCH v3 3/3] arm64: dts: renesas: r8a77965: " Jiada Wang
2019-03-19  6:07 ` Kuninori Morimoto [this message]
2019-03-19 12:06   ` [PATCH v3 0/3] rsnd: dts: change to " 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=87va0fs92d.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=jiada_wang@mentor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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