From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Cc: horms@verge.net.au, geert@linux-m68k.org, hans.verkuil@cisco.com,
niklas.soderlund@ragnatech.se, linux-media@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, magnus.damm@gmail.com
Subject: Re: [PATCH 1/3] ARM: dts: r8a7793: Enable VIN0, VIN1
Date: Fri, 30 Sep 2016 14:08:53 +0300 [thread overview]
Message-ID: <2139972.htm5G2lxOE@avalon> (raw)
In-Reply-To: <1961479.Ly4IFObGfR@avalon>
Hi Ulrich,
On Friday 30 Sep 2016 13:55:50 Laurent Pinchart wrote:
> On Friday 16 Sep 2016 15:09:33 Ulrich Hecht wrote:
> > Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> > ---
> >
> > arch/arm/boot/dts/r8a7793.dtsi | 20 ++++++++++++++++++++
> > 1 file changed, 20 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/r8a7793.dtsi
> > b/arch/arm/boot/dts/r8a7793.dtsi index 8d02aac..0898668 100644
> > --- a/arch/arm/boot/dts/r8a7793.dtsi
> > +++ b/arch/arm/boot/dts/r8a7793.dtsi
> > @@ -30,6 +30,8 @@
> > i2c7 = &i2c7;
> > i2c8 = &i2c8;
> > spi0 = &qspi;
> > + vin0 = &vin0;
> > + vin1 = &vin1;
>
> Why is this needed ?
>
> > };
> >
> > cpus {
> > @@ -852,6 +854,24 @@
> > status = "disabled";
> > };
> >
> > + vin0: video@e6ef0000 {
> > + compatible = "renesas,vin-r8a7793";
Additionally, should this be
compatiable = "renesas,vin-r8a7793", "renesas,rcar-gen2-vin";
?
> > + reg = <0 0xe6ef0000 0 0x1000>;
> > + interrupts = <GIC_SPI 188 IRQ_TYPE_LEVEL_HIGH>;
> > + clocks = <&mstp8_clks R8A7793_CLK_VIN0>;
> > + power-domains = <&sysc R8A7793_PD_ALWAYS_ON>;
> > + status = "disabled";
> > + };
> > +
> > + vin1: video@e6ef1000 {
> > + compatible = "renesas,vin-r8a7793";
> > + reg = <0 0xe6ef1000 0 0x1000>;
> > + interrupts = <GIC_SPI 189 IRQ_TYPE_LEVEL_HIGH>;
> > + clocks = <&mstp8_clks R8A7793_CLK_VIN1>;
> > + power-domains = <&sysc R8A7793_PD_ALWAYS_ON>;
> > + status = "disabled";
> > + };
> > +
>
> As Geert mentioned, you should add vin2 here.
>
> > qspi: spi@e6b10000 {
> >
> > compatible = "renesas,qspi-r8a7793", "renesas,qspi";
> > reg = <0 0xe6b10000 0 0x2c>;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-09-30 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:09 [PATCH 0/3] r8a7793 Gose video input support Ulrich Hecht
2016-09-16 13:09 ` [PATCH 1/3] ARM: dts: r8a7793: Enable VIN0, VIN1 Ulrich Hecht
2016-09-19 7:17 ` Geert Uytterhoeven
2016-09-30 10:55 ` Laurent Pinchart
2016-09-30 11:08 ` Laurent Pinchart [this message]
2016-09-16 13:09 ` [PATCH 2/3] ARM: dts: gose: add HDMI input Ulrich Hecht
2016-09-30 12:40 ` Laurent Pinchart
2016-09-30 13:00 ` Geert Uytterhoeven
2016-09-30 13:32 ` Laurent Pinchart
2016-10-01 9:19 ` Niklas Söderlund
2016-10-03 10:16 ` Laurent Pinchart
2016-09-16 13:09 ` [PATCH 3/3] ARM: dts: gose: add composite video input Ulrich Hecht
2016-09-30 12:42 ` Laurent Pinchart
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=2139972.htm5G2lxOE@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert@linux-m68k.org \
--cc=hans.verkuil@cisco.com \
--cc=horms@verge.net.au \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=ulrich.hecht+renesas@gmail.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).