From: Jiada Wang <jiada_wang@mentor.com>
To: <horms@verge.net.au>, <magnus.damm@gmail.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<kuninori.morimoto.gx@renesas.com>
Cc: <linux-renesas-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <jiada_wang@mentor.com>
Subject: [PATCH v4 0/1] rsnd: dts: change to use extended audio dmac register
Date: Tue, 26 Mar 2019 18:58:25 +0900 [thread overview]
Message-ID: <20190326095826.4987-1-jiada_wang@mentor.com> (raw)
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.
---
v4: use a single patch to update
v3: update H3 (= r8a7795), M3-W (= r8a7796) and M3-N (=r8a77965) to point
point to extended audio dmac register set in DT
v2: update rsnd driver to use extended register set when available
rename R-CAR E3 audio dmac regisetr
v1: initial version
Jiada Wang (1):
arm64: dts: renesas: use extended audio dmac register
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 2 +-
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 2 +-
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.19.2
next reply other threads:[~2019-03-26 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 9:58 Jiada Wang [this message]
2019-03-26 9:58 ` [PATCH v4 1/1] arm64: dts: renesas: use extended audio dmac register Jiada Wang
2019-03-26 10:09 ` Geert Uytterhoeven
2019-03-27 11:16 ` 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=20190326095826.4987-1-jiada_wang@mentor.com \
--to=jiada_wang@mentor.com \
--cc=devicetree@vger.kernel.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).