From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: <horms@verge.net.au>
Cc: Jiada Wang <jiada_wang@mentor.com>, <magnus.damm@gmail.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>, <geert@linux-m68k.org>,
<linux-renesas-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 5/5] ASoC: rsnd: dma: use extended audio dmac registers when available
Date: 13 Mar 2019 15:57:25 +0900 [thread overview]
Message-ID: <87d0mvgtnc.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <eb7ac3a6-e386-09e8-54b0-2e0eda90ad66@mentor.com>
Hi Simon
> > 2nd, in my understanding, our conclusion at Renesas-ML
> > is that we don't need to think about basic/extend DMAC register.
> > Because extend area is 100% covering basic area.
> > In other words, it is compatible.
> > Driver side don't need to think about it.
> >
> I am a little confused,
> because latest comment received from simon, suggests to let driver to
> decide which register set to use.
>
> for me, I think it's not necessary, if extended register set is available,
> driver shall always use it.
I can agree to have both basic/extend register
if driver need to switch its behavior.
But this case, there is nothing to do on driver side.
In other words, SoC always need to use extend
register if it has.
I don't know why datasheet is indicating both area.
Maybe it is because for Gen3 all-in ? I'm not sure.
Anyway, Simon, can you agree about it ?
Having both basic/extend register is just noise for driver.
Best regards
---
Kuninori Morimoto
next prev parent reply other threads:[~2019-03-13 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 5:58 [PATCH 5/5] ASoC: rsnd: dma: use extended audio dmac registers when available Jiada Wang
2019-03-13 6:23 ` Kuninori Morimoto
2019-03-13 6:33 ` Kuninori Morimoto
2019-03-13 6:36 ` Jiada Wang
2019-03-13 6:34 ` Jiada Wang
2019-03-13 6:57 ` Kuninori Morimoto [this message]
2019-03-13 8:52 ` Geert Uytterhoeven
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=87d0mvgtnc.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=jiada_wang@mentor.com \
--cc=lgirdwood@gmail.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=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).