From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel <alsa-devel@alsa-project.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: ASoC: renesas,rsnd: Add r8a7742 support
Date: Wed, 27 May 2020 12:32:28 +0100 [thread overview]
Message-ID: <CA+V-a8v0i71MCTNTPVD3XHuyGZiVjzuCkCUnvoUczeMr416ouQ@mail.gmail.com> (raw)
In-Reply-To: <20200527112548.GD5308@sirena.org.uk>
Hi Mark,
Thank you for the review.
On Wed, May 27, 2020 at 12:25 PM Mark Brown <broonie@kernel.org> wrote:
>
> On Tue, May 26, 2020 at 10:01:43PM +0100, Lad Prabhakar wrote:
>
> > Examples with soctypes are:
> > + - "renesas,rcar_sound-r8a7742" (RZ/G1H)
> > - "renesas,rcar_sound-r8a7743" (RZ/G1M)
> > - "renesas,rcar_sound-r8a7744" (RZ/G1N)
> > - "renesas,rcar_sound-r8a7745" (RZ/G1E)
>
> I'd expect a matching patch adding this compatible to the driver.
The Renesas R-Car sound for RZ/G1H is identical to the R-Car Gen2
family. So no driver change is needed and the fallback compatible
value "renesas,rcar_sound-gen2" will be used in the SOC DT.
Cheers,
--Prabhakar Lad
next prev parent reply other threads:[~2020-05-27 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 21:01 [PATCH 0/2] RZ/G1H enable sound support Lad Prabhakar
2020-05-26 21:01 ` [PATCH 1/2] dt-bindings: ASoC: renesas,rsnd: Add r8a7742 support Lad Prabhakar
2020-05-27 7:38 ` Geert Uytterhoeven
2020-05-27 11:25 ` Mark Brown
2020-05-27 11:32 ` Lad, Prabhakar [this message]
2020-05-27 11:54 ` Mark Brown
2020-05-29 17:50 ` Rob Herring
2020-05-26 21:01 ` [PATCH 2/2] ARM: dts: r8a7742: Add audio support Lad Prabhakar
2020-05-27 7:52 ` Geert Uytterhoeven
2020-05-27 23:24 ` Kuninori Morimoto
2020-05-29 21:05 ` [PATCH 0/2] RZ/G1H enable sound support Mark Brown
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=CA+V-a8v0i71MCTNTPVD3XHuyGZiVjzuCkCUnvoUczeMr416ouQ@mail.gmail.com \
--to=prabhakar.csengg@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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).