From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: horms@verge.net.au, magnus.damm@gmail.com, geert@linux-m68k.org,
niklas.soderlund@ragnatech.se,
sergei.shtylyov@cogentembedded.com,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] arm64: dts: renesas: eagle: Enable DU
Date: Fri, 06 Apr 2018 16:47:23 +0300 [thread overview]
Message-ID: <1607257.kzKzzg5gBe@avalon> (raw)
In-Reply-To: <35431593.B1LTs037XF@avalon>
Hi again,
On Friday, 6 April 2018 16:45:16 EEST Laurent Pinchart wrote:
> On Friday, 6 April 2018 16:08:10 EEST Jacopo Mondi wrote:
> > Enable DU for Renesas R-Car V3M Eagle board.
> >
> > Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> > ---
> >
> > arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> > b/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts index 3c5f598..144b847
> > 100644
> > --- a/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> > +++ b/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
> > @@ -76,6 +76,11 @@
> >
> > function = "i2c0";
> >
> > };
> >
> > + du_pins: du {
> > + groups = "du_rgb666", "du_sync", "du_oddf", "du_clk_out";
> > + function = "du";
> > + };
>
> As far as I can tell the DU parallel output isn't used on the Eagle board,
> but is used on the Eagle expansion board. I would move this to patch 7/7 in
> this series.
My bad, patch 7/7 describes the on-board HDMI encoder, not the one on the
expansion board. I would thus drop pinmux completely for now until we add
support for the expansion board.
> > scif0_pins: scif0 {
> >
> > groups = "scif0_data";
> > function = "scif0";
> >
> > @@ -93,3 +98,9 @@
> >
> > status = "okay";
> >
> > };
> >
> > +
> > +&du {
> > + pinctrl-0 = <&du_pins>;
> > + pinctrl-names = "default";
>
> These two properties should be moved to patch 7/7 too.
So this should be removed.
> > + status = "okay";
> > +};
>
> There's little use for enabling the DU in DT if you have no output port
> described. I'd move this to patch 6/7.
And I'd merge the status attribute and patches 6/7 and 7/7 all together.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-04-06 13:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 13:08 [PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge Jacopo Mondi
2018-04-06 13:08 ` [PATCH 1/7] arm64: dts: renesas: r8a77970: add FCPVD support Jacopo Mondi
2018-04-06 13:28 ` Laurent Pinchart
2018-04-09 12:19 ` Simon Horman
2018-04-06 13:08 ` [PATCH 2/7] arm64: dts: renesas: r8a77970: add VSPD support Jacopo Mondi
2018-04-06 13:33 ` Laurent Pinchart
2018-04-09 12:21 ` Simon Horman
2018-04-06 13:08 ` [PATCH 3/7] arm64: dts: renesas: r8a77970: add DU support Jacopo Mondi
2018-04-06 13:36 ` Laurent Pinchart
2018-04-06 13:08 ` [PATCH 4/7] arm64: dts: renesas: r8a77970: add the LVDS instance Jacopo Mondi
2018-04-06 13:38 ` Laurent Pinchart
2018-04-06 13:08 ` [PATCH 5/7] arm64: dts: renesas: eagle: Enable DU Jacopo Mondi
2018-04-06 13:45 ` Laurent Pinchart
2018-04-06 13:47 ` Laurent Pinchart [this message]
2018-04-06 13:08 ` [PATCH 6/7] arm64: dts: renesas: eagle: Add LVDS decoder Jacopo Mondi
2018-04-06 13:49 ` Laurent Pinchart
2018-04-06 13:08 ` [PATCH 7/7] arm64: dts: renesas: eagle: Add ADV7511W and HDMI output Jacopo Mondi
2018-04-06 13:51 ` Laurent Pinchart
2018-04-06 14:16 ` jacopo mondi
2018-04-06 13:17 ` [PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge jacopo mondi
2018-04-06 13:53 ` Laurent Pinchart
2018-04-06 14:13 ` jacopo mondi
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=1607257.kzKzzg5gBe@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=sergei.shtylyov@cogentembedded.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