From: Linus Walleij <linus.walleij@linaro.org>
To: Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Liviu Dudau <liviu.dudau@arm.com>,
devicetree@vger.kernel.org
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
dri-devel@lists.freedesktop.org,
Ryan Harkin <ryan.harkin@linaro.org>,
robh+dt@kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] drm/bridge: Add virtual display DT bindings
Date: Fri, 24 Aug 2018 14:23:08 +0200 [thread overview]
Message-ID: <20180824122308.3092-1-linus.walleij@linaro.org> (raw)
This adds bindings for a virtual display to be used with displays
inside entirely virtual environments which do not emulate things
like monitors but just need timing information to be supplied to
its display controller.
This is inspired by earlier work by Liviu Dudau.
Cc: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Ryan Harkin <ryan.harkin@linaro.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
.../display/bridge/virtual-display-bridge.txt | 62 +++++++++++++++++++
1 file changed, 62 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/bridge/virtual-display-bridge.txt
diff --git a/Documentation/devicetree/bindings/display/bridge/virtual-display-bridge.txt b/Documentation/devicetree/bindings/display/bridge/virtual-display-bridge.txt
new file mode 100644
index 000000000000..ea4f5a91ab94
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/virtual-display-bridge.txt
@@ -0,0 +1,62 @@
+Virtual Display Bridge
+
+This represents a display that is contained within an emulated
+environment.
+
+This means that the display engine mainly expects some timing
+parameters to be written into it, and after that the emulator will
+respond by creating a virtual display with the requested
+resolution characteristics.
+
+As the operating system cannot "detect" such a display, rather the
+emulator will respond to what the controller outputs, a
+chicken-and-egg problem needs to be solved: the resolution and
+timing characteristics need to be defined and set up somewhere.
+
+The virtual display bridge solves this by defining a bridge with
+all timing characteristics encoded into the device tree node.
+
+Required properies:
+- compatible: shall be "virtual-display-bridge"
+
+Required subnodes:
+- display-timings: contains in turn a display timing node
+ see display-timing.txt
+- ports: contains the display ports, see media/video-interfaces.txt
+
+Example:
+
+bridge {
+ compatible = "virtual-display-bridge";
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ display-timings {
+ /* Some standard VGA timing */
+ timing0 {
+ clock-frequency = <23750>;
+ hactive = <640>;
+ vactive = <480>;
+ hfront-porch = <48>;
+ hback-porch = <16>;
+ hsync-len = <96>;
+ vfront-porch = <33>;
+ vback-porch = <9>;
+ vsync-len = <3>;
+ vrefresh = <60>;
+ };
+ };
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port@0 {
+ reg = <0>;
+
+ display_bridge_in: endpoint {
+ remote-endpoint = <&foo>;
+ };
+ };
+ };
+};
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-08-24 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180824122324epcas3p2922f3e5415dacf4c89cfb136fa5c77b2@epcas3p2.samsung.com>
2018-08-24 12:23 ` Linus Walleij [this message]
2018-08-27 11:53 ` [PATCH 1/2] drm/bridge: Add virtual display DT bindings Andrzej Hajda
2018-08-28 13:45 ` Linus Walleij
2018-08-29 9:58 ` Andrzej Hajda
2018-08-29 10:01 ` Liviu Dudau
2018-08-29 10:23 ` Andrzej Hajda
2018-08-29 11:00 ` Liviu Dudau
2018-08-29 12:16 ` Andrzej Hajda
2018-10-16 9:40 ` Linus Walleij
2018-10-16 9:33 ` Linus Walleij
2018-08-28 14:35 ` Liviu Dudau
2018-08-29 8:16 ` Andrzej Hajda
2018-08-29 8:51 ` Liviu Dudau
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=20180824122308.3092-1-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=architt@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=ryan.harkin@linaro.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).