Hi Morimoto-san,
On Wed, Mar 13, 2019 at 7:57 AM Kuninori Morimoto
<kuninori.morimoto.gx@xxxxxxxxxxx> wrote:
> > > 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.
I can follow your rationale of only describing the extended register set,
if available.
However:
1) The DT bindings should state clearly that the AUDMAPP register
block should point to the extended register set, if available,
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?
Thanks!
P.S. The binding doc seems to need some love.
I came up with the following a while ago, but got interrupted.
Feel free to steal ;-)
--- a/Documentation/devicetree/bindings/sound/renesas,rsnd.txt
+++ b/Documentation/devicetree/bindings/sound/renesas,rsnd.txt
@@ -338,9 +338,9 @@ Required properties:
=============================================
- compatible : "renesas,rcar_sound-<soctype>", fallbacks
- "renesas,rcar_sound-gen1" if generation1, and
- "renesas,rcar_sound-gen2" if
generation2 (or RZ/G1)
- "renesas,rcar_sound-gen3" if
generation3 (or RZ/G2)
+ "renesas,rcar_sound-gen1" if R-Car Gen1, and
+ "renesas,rcar_sound-gen2" if R-Car
Gen2 or RZ/G1
+ "renesas,rcar_sound-gen3" if R-Car
Gen3 or RZ/G2
Examples with soctypes are:
- "renesas,rcar_sound-r8a7743" (RZ/G1M)
- "renesas,rcar_sound-r8a7745" (RZ/G1E)
@@ -357,8 +357,10 @@ Required properties:
- "renesas,rcar_sound-r8a77990" (R-Car E3)
- reg : Should contain the register physical address.
required register is
- SRU/ADG/SSI if generation1
- SRU/ADG/SSIU/SSI if generation2
+ SRU/ADG/SSI if R-Car Gen1
+ SCU/ADG/SSIU/SSI/AUDMAPP if R-Car Gen2,
+ R-Car Gen3, RZ/G1, or RZ/G2.
+- reg-names = "scu", "adg", "ssiu", "ssi", "audmapp";
- rcar_sound,ssi : Should contain SSI feature.
The number of SSI subnode should be
same as HW.
see below for detail.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
