All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <simon@horms.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: renesas: salvator-common: Remove extra LVDS port label
Date: Sat, 29 Jul 2017 23:05:50 +0300	[thread overview]
Message-ID: <2519562.g0Iit6Qbpy@avalon> (raw)
In-Reply-To: <CAMuHMdUaZZc+WXhmEif6kBgAV7jfREtk78nn67W3=SwvkVxhPg@mail.gmail.com>

Hi Simon,

On Monday 17 Jul 2017 10:07:33 Geert Uytterhoeven wrote:
> On Thu, Jul 13, 2017 at 2:17 PM, Laurent Pinchart wrote:
> > The DU LVDS output is on port 3 on R8A7795 but on port 2 on R8A7796. The
> > lvds_connector label thus can't be defined in salvator-common.dtsi,
> > common to the two SoCs.
> > 
> > The lvds_connector label is meant for convience to be referenced from
> > panel device tree files, such as r8a77xx-aa104xd12-panel.dtsi or
> > r8a77xx-aa121td01-panel.dtsi.  As those files are not included in any
> > device tree source, and the label never used elsewhere, we can simply
> > remove it. Out-of-tree patches that include panel device tree files can
> > then add a
> > 
> >         #define lvds_connector du_out_lvds0
> > 
> > before including the panel device tree file.
> > 
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> 
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Could you please pick this patch up for v4.14 ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2017-07-29 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 12:17 [PATCH] arm64: dts: renesas: salvator-common: Remove extra LVDS port label Laurent Pinchart
2017-07-17  8:07 ` Geert Uytterhoeven
2017-07-29 20:05   ` Laurent Pinchart [this message]
2017-07-31 14:55     ` Simon Horman

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=2519562.g0Iit6Qbpy@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=simon@horms.net \
    /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.