From: Jiada Wang <jiada_wang@mentor.com>
To: <horms@verge.net.au>, <magnus.damm@gmail.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-renesas-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<kuninori.morimoto.gx@renesas.com>, <geert@linux-m68k.org>,
<jiada_wang@mentor.com>
Subject: [PATCH v3 2/3] arm64: dts: renesas: r8a7796: use extended audio dmac register
Date: Tue, 19 Mar 2019 14:57:04 +0900 [thread overview]
Message-ID: <20190319055705.24115-3-jiada_wang@mentor.com> (raw)
In-Reply-To: <20190319055705.24115-1-jiada_wang@mentor.com>
Basic audio dmac register only supports busif from 0 to 3,
in order to use busif4 ~ busif7, extended audio dmac register
need to be used
Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
---
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/renesas/r8a7796.dtsi b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
index cdf784899cf8..13c6b5b3e8e0 100644
--- a/arch/arm64/boot/dts/renesas/r8a7796.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
@@ -1775,7 +1775,7 @@
<0 0xec5a0000 0 0x100>, /* ADG */
<0 0xec540000 0 0x1000>, /* SSIU */
<0 0xec541000 0 0x280>, /* SSI */
- <0 0xec740000 0 0x200>; /* Audio DMAC peri peri*/
+ <0 0xec760000 0 0x200>; /* Audio DMAC peri peri*/
reg-names = "scu", "adg", "ssiu", "ssi", "audmapp";
clocks = <&cpg CPG_MOD 1005>,
--
2.19.2
next prev parent reply other threads:[~2019-03-19 5:57 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 ` Jiada Wang [this message]
2019-03-19 5:57 ` [PATCH v3 3/3] arm64: dts: renesas: r8a77965: " Jiada Wang
2019-03-19 6:07 ` [PATCH v3 0/3] rsnd: dts: change to " Kuninori Morimoto
2019-03-19 12:06 ` 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=20190319055705.24115-3-jiada_wang@mentor.com \
--to=jiada_wang@mentor.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.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;
as well as URLs for NNTP newsgroup(s).