All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	Jiada Wang <jiada_wang@mentor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH 5/5] ASoC: rsnd: dma: use extended audio dmac registers when available
Date: 18 Mar 2019 14:22:56 +0900	[thread overview]
Message-ID: <87ef74ydhi.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <CAMuHMdUHeh6YDY1gTkSgnJm1xG0XtyaQ-zs_3bvFx1+mz6LHTg@mail.gmail.com>


Hi Geert

> > 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.
> 
> I can follow your rationale of only describing the extended register set,
> if available.

Thank you

> However:
>   1) The DT bindings should state clearly that the AUDMAPP register
>      block should point to the extended register set, if available,

Yes, indeed.
I re-used your sample patch, and posted.

>   2) Can the driver distinguish between an old DTB describing the basic
>      register set, and a new DTB describing the extended register set?
>      I.e. will the driver avoid using busif4-7 when using an old DTB
>      describing the basic register set, to maintain backwards compatibility?

The situation which need to use busif4-7 is
TDM 16ch Split mode. It is very rare case.
And it is not yet supported on driver.
This means, there is zero chance to access to busif4-7 under old DTB.

Best regards
---
Kuninori Morimoto

      reply	other threads:[~2019-03-18  5:22 UTC|newest]

Thread overview: 15+ 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  5:58 ` Jiada Wang
2019-03-13  6:23 ` Kuninori Morimoto
2019-03-13  6:23   ` Kuninori Morimoto
2019-03-13  6:33   ` Kuninori Morimoto
2019-03-13  6:33     ` Kuninori Morimoto
2019-03-13  6:36     ` Jiada Wang
2019-03-13  6:36       ` Jiada Wang
2019-03-13  6:34   ` Jiada Wang
2019-03-13  6:34     ` Jiada Wang
2019-03-13  6:57     ` Kuninori Morimoto
2019-03-13  6:57       ` Kuninori Morimoto
2019-03-13  8:52       ` Geert Uytterhoeven
2019-03-13  8:52         ` Geert Uytterhoeven
2019-03-18  5:22         ` Kuninori Morimoto [this message]

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=87ef74ydhi.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.