From: dkos@cadence.com (Damian Kos)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/6] dt-bindings: drm/bridge: Document Cadence MHDP bridge bindings
Date: Mon, 8 Oct 2018 22:42:09 +0100 [thread overview]
Message-ID: <1539034953-11274-4-git-send-email-dkos@cadence.com> (raw)
In-Reply-To: <1539034953-11274-1-git-send-email-dkos@cadence.com>
From: Quentin Schulz <quentin.schulz@free-electrons.com>
Document the bindings used for the Cadence MHDP DPI/DP bridge.
Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
Signed-off-by: Damian Kos <dkos@cadence.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../bindings/display/bridge/cdns,mhdp.txt | 43 +++++++++++++++++++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/bridge/cdns,mhdp.txt
diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,mhdp.txt b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp.txt
new file mode 100644
index 000000000000..f8334c520b98
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/cdns,mhdp.txt
@@ -0,0 +1,43 @@
+Cadence MHDP bridge
+==========================
+
+The Cadence MHDP bridge is a DPI to DP bridge.
+
+Required properties:
+- compatible: should be "cdns,mhdp8546",
+- reg: physical base address and length of the controller's registers,
+- clocks: DP bridge clock, it's used by the IP to know how to translate
+ a number of clock cycles into a time (which is used to comply
+ with DP standard timings and delays),
+
+Required subnodes:
+- ports: Ports as described in Documentation/devictree/bindings/graph.txt
+ Port 0 - input port representing the DP bridge input
+ Port 1 - output port representing the DP bridge output
+
+Example:
+
+ mhdp: dp-bridge at f0fb000000 {
+ compatible = "cdns,mhdp8546";
+ reg = <0xf0 0xfb000000 0x0 0x1000000>;
+ clocks = <&mhdp_clock>;
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port at 0 {
+ reg = <0>;
+ dp_bridge_input: endpoint {
+ remote-endpoint = <&xxx_dpi_output>;
+ };
+ };
+
+ port at 1 {
+ reg = <1>;
+ dp_bridge_output: endpoint {
+ remote-endpoint = <&xxx_dp_connector_input>;
+ };
+ };
+ };
+ };
--
2.17.1
next prev parent reply other threads:[~2018-10-08 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 21:42 [PATCH v6 0/6] drm: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-10-08 21:42 ` [PATCH v6 1/6] drm/rockchip: prepare common code for cdns and rk dpi/dp driver Damian Kos
2018-10-08 21:42 ` [PATCH v6 2/6] drm/dp: fix link probing for devices supporting DP 1.4+ Damian Kos
2018-10-08 21:42 ` Damian Kos [this message]
2018-10-08 21:42 ` [PATCH v6 4/6] drm: bridge: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-11-05 13:10 ` Andrzej Hajda
2018-10-08 21:42 ` [PATCH v6 5/6] drm/bridge: add support for MST in mhdp8546 driver Damian Kos
2018-11-07 11:40 ` Andrzej Hajda
2018-11-08 14:53 ` Damian Kos
2018-10-08 21:42 ` [PATCH v6 6/6] drm/bridge: add PHY initialization " Damian Kos
2018-11-07 11:49 ` Andrzej Hajda
2018-11-05 9:44 ` [PATCH v6 0/6] drm: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-11-05 10:30 ` Laurent Pinchart
2018-11-05 10:33 ` Damian Kos
2018-11-05 11:09 ` Andrzej Hajda
2018-11-05 11:34 ` Damian Kos
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=1539034953-11274-4-git-send-email-dkos@cadence.com \
--to=dkos@cadence.com \
--cc=linux-arm-kernel@lists.infradead.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).