From: Frank Rowand <frowand.list@gmail.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
dri-devel@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 3/4 - variant 1] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes
Date: Thu, 1 Mar 2018 18:06:36 -0800 [thread overview]
Message-ID: <b04c2436-7e4c-847c-3288-93fb768bbff6@gmail.com> (raw)
In-Reply-To: <20180301220540.11959-4-laurent.pinchart+renesas@ideasonboard.com>
On 03/01/18 14:05, Laurent Pinchart wrote:
> The internal LVDS encoders now have their own DT bindings. Before
> switching the driver infrastructure to those new bindings, implement
> backward-compatibility through live DT patching.
>
> Patching is disabled and will be enabled along with support for the new
> DT bindings in the DU driver.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
Reviewed-by: Frank Rowand <frank.rowand@sony.com>
next prev parent reply other threads:[~2018-03-02 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 22:05 [PATCH v7 0/4] R-Car DU: Convert LVDS code to bridge driver Laurent Pinchart
2018-03-01 22:05 ` [PATCH v7 1/4] dt-bindings: display: renesas: Add R-Car LVDS encoder DT bindings Laurent Pinchart
2018-03-01 22:05 ` [PATCH v7 2/4] dt-bindings: display: renesas: Deprecate LVDS support in the DU bindings Laurent Pinchart
2018-03-01 22:05 ` [PATCH v7 3/4 - variant 1] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes Laurent Pinchart
2018-03-02 0:42 ` Niklas Söderlund
2018-03-02 13:02 ` Laurent Pinchart
2018-03-02 2:06 ` Frank Rowand [this message]
2018-03-01 22:05 ` [PATCH v7 3/4 - variant 2] " Laurent Pinchart
2018-03-02 2:17 ` Frank Rowand
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=b04c2436-7e4c-847c-3288-93fb768bbff6@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@vger.kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.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).