From: jiada <jiada_wang@mentor.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] rsnd: dts: change to use extended audio dmac register
Date: Fri, 22 Feb 2019 12:05:02 +0900 [thread overview]
Message-ID: <021012f9-f522-0efd-4bb2-c56917623266@mentor.com> (raw)
In-Reply-To: <871s427ux5.wl-kuninori.morimoto.gx@renesas.com>
Hi Geert
On 2019/02/20 17:10, Kuninori Morimoto wrote:
>
> Hi Geert
>
>>> According to user reference manual for R-CAR H3 and M3-W 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)
>>>
>>> This patch set updates H3 (= r8a7795) and M3-W (= r8a7796)
>>> to use extended audio dmac registers
>>
>> The same change should be applied for M3-N and RZ/G2M, right?
>>
Currently only H3 and M3-W support to use busif other than busif0,
I feel currently it's only necessary to use extended audio dmac register
for these SoCs
>> R-Car E3 and RZ/G2E already use the extended register set, as they do not
>> have the basic set.
>>
>> For SoCs having both, this feels a bit like describing software policy, instead
>> of hardware, to me. Would it make sense to extend the audio bindings, and
>> allow describing both the basic and extended register sets, and let the driver
>> make the decision which one to use?
>
> I don't think we need to use basic register.
> This means extended register only is very enough.
> I'm not sure why datasheet is indicating basic...
>
Extended audio dmac registers covers all function of basic ones,
so there is no need to use basic registers
Thanks,
Jiada
> Best regards
> ---
> Kuninori Morimoto
>
next prev parent reply other threads:[~2019-02-22 3:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 5:24 Jiada Wang
2019-02-20 5:24 ` [PATCH v1 1/2] arm64: dts: renesas: r8a7795: " Jiada Wang
2019-02-20 8:04 ` Geert Uytterhoeven
2019-02-20 5:24 ` [PATCH v1 2/2] arm64: dts: renesas: r8a7796: " Jiada Wang
2019-02-20 8:05 ` Geert Uytterhoeven
2019-02-20 8:04 ` [PATCH v1 0/2] rsnd: dts: change to " Geert Uytterhoeven
[not found] ` <871s427ux5.wl-kuninori.morimoto.gx@renesas.com>
2019-02-22 3:05 ` jiada [this message]
2019-02-25 9:23 ` 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=021012f9-f522-0efd-4bb2-c56917623266@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
all inboxes | Powered by JetHome®