From: Peter Rosin <peda@axentia.se>
To: linux-kernel@vger.kernel.org
Cc: Peter Rosin <peda@axentia.se>, David Airlie <airlied@linux.ie>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] dt-bindings: display: bridge: lvds-transmitter: add ti,ds90c185
Date: Mon, 9 Apr 2018 12:59:14 +0200 [thread overview]
Message-ID: <20180409105918.20792-2-peda@axentia.se> (raw)
In-Reply-To: <20180409105918.20792-1-peda@axentia.se>
Start list of actual chips compatible with "lvds-encoder".
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Peter Rosin <peda@axentia.se>
---
.../devicetree/bindings/display/bridge/lvds-transmitter.txt | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt b/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt
index fd39ad34c383..50220190c203 100644
--- a/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt
+++ b/Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt
@@ -22,7 +22,13 @@ among others.
Required properties:
-- compatible: Must be "lvds-encoder"
+- compatible: Must be one or more of the following
+ - "ti,ds90c185" for the TI DS90C185 FPD-Link Serializer
+ - "lvds-encoder" for a generic LVDS encoder device
+
+ When compatible with the generic version, nodes must list the
+ device-specific version corresponding to the device first
+ followed by the generic version.
Required nodes:
--
2.11.0
next prev parent reply other threads:[~2018-04-09 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:59 [PATCH 0/5] Add tda998x (HDMI) support to atmel-hlcdc Peter Rosin
2018-04-09 10:59 ` Peter Rosin [this message]
2018-04-13 17:39 ` [PATCH 1/5] dt-bindings: display: bridge: lvds-transmitter: add ti,ds90c185 Rob Herring
2018-04-09 10:59 ` [PATCH 2/5] dt-bindings: display: atmel: add optional output-mode property Peter Rosin
2018-04-13 17:46 ` Rob Herring
2018-04-14 13:54 ` Peter Rosin
2018-04-16 14:22 ` Rob Herring
2018-04-09 10:59 ` [PATCH 3/5] drm/atmel-hlcdc: allow overriding the output mode Peter Rosin
2018-04-09 10:59 ` [PATCH 4/5] drm/atmel-hlcdc: add support for connecting to tda998x HDMI encoder Peter Rosin
2018-04-09 10:59 ` [PATCH 5/5] drm/atmel-hlcdc: fix broken release date Peter Rosin
2018-04-09 11:17 ` [PATCH 0/5] Add tda998x (HDMI) support to atmel-hlcdc Russell King - ARM Linux
2018-04-09 11:44 ` Peter Rosin
2018-04-09 12:02 ` Russell King - ARM Linux
2018-04-09 12:12 ` Peter Rosin
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=20180409105918.20792-2-peda@axentia.se \
--to=peda@axentia.se \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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).