public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: stout: Convert to new LVDS DT bindings
Date: Wed, 05 Dec 2018 07:41:36 +0200	[thread overview]
Message-ID: <6335524.oXJRfKre9U@avalon> (raw)
In-Reply-To: <9715f969-2487-6699-70af-3e3c4d176f72@gmail.com>

Hi Marek,

On Wednesday, 5 December 2018 03:10:18 EET Marek Vasut wrote:
> On 12/03/2018 11:48 PM, Laurent Pinchart wrote:
> > On Tuesday, 4 December 2018 00:24:32 EET Marek Vasut wrote:
> >> On 12/03/2018 10:48 PM, Laurent Pinchart wrote:
> >>> On Monday, 3 December 2018 17:12:41 EET Geert Uytterhoeven wrote:
> >>>> As of commit 6d2ca85279becdff ("dt-bindings: display: renesas:
> >>>> Deprecate LVDS support in the DU bindings"), the internal LVDS encoder
> >>>> has DT bindings separate from the DU.  The Lager device tree was ported
> >>>> over to the new model, but the Stout device tree was forgotten.
> >>>> 
> >>>> Fixes: 15a1ff30d8f9bd83 ("ARM: dts: r8a7790: Convert to new LVDS DT
> >>>> bindings") Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >>>> ---
> >>>> Compile-tested only.
> >>> 
> >>> I can't test the patch either but it looks fine to me.
> >>> 
> >>> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >>> 
> >>> I assume you will send this directly to Simon, so I don't plan to take
> >>> the patch in my tree.
> >> 
> >> I have a Stout if you need me to test something.
> > 
> > Could you test HDMI output ? We just need to ensure that everything is
> > probed correctly, so display anything on the HDMI output will do.
> 
> Sure, can you push me a branch somewhere, so I don't have to hunt down
> patches ?

Only this patch should be needed. You can get it from https://
patchwork.kernel.org/patch/10709781/ and apply it on top of v4.19. Please 
don't use v4.20-rc is there's one missing regression fix there (it has been 
merged in the media tree and should make it to the final release).

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2018-12-05  5:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 15:12 [PATCH 0/2] arm: dts: renesas: Convert remaining boards to new LVDS DT bindings Geert Uytterhoeven
2018-12-03 15:12 ` [PATCH 1/2] ARM: dts: stout: Convert " Geert Uytterhoeven
2018-12-03 21:48   ` Laurent Pinchart
2018-12-03 22:24     ` Marek Vasut
2018-12-03 22:48       ` Laurent Pinchart
2018-12-05  1:10         ` Marek Vasut
2018-12-05  5:41           ` Laurent Pinchart [this message]
2018-12-07 18:36             ` Marek Vasut
2018-12-10 12:03               ` Simon Horman
2018-12-03 15:12 ` [PATCH 2/2] arm64: dts: renesas: r8a7796: salvator-xs: " Geert Uytterhoeven
2018-12-03 21:51   ` Laurent Pinchart
2018-12-10 12:04     ` 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=6335524.oXJRfKre9U@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=marek.vasut@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