From: Kevin Tang <kevin3.tang@gmail.com>
To: airlied@linux.ie, daniel@ffwll.ch, robh+dt@kernel.org,
mark.rutland@arm.com, kevin3.tang@gmail.com
Cc: orsonzhai@gmail.com, baolin.wang@linaro.org,
zhang.lyra@gmail.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: [PATCH RFC v1 1/6] dt-bindings: display: add Unisoc's drm master bindings
Date: Mon, 16 Dec 2019 19:40:14 +0800 [thread overview]
Message-ID: <1576496419-12409-2-git-send-email-kevin3.tang@gmail.com> (raw)
In-Reply-To: <1576496419-12409-1-git-send-email-kevin3.tang@gmail.com>
From: Kevin Tang <kevin.tang@unisoc.com>
The Unisoc DRM master device is a virtual device needed to list all
DPU devices or other display interface nodes that comprise the
graphics subsystem
Cc: Orson Zhai <orsonzhai@gmail.com>
Cc: Baolin Wang <baolin.wang@linaro.org>
Cc: Chunyan Zhang <zhang.lyra@gmail.com>
Signed-off-by: Kevin Tang <kevin.tang@unisoc.com>
---
.../devicetree/bindings/display/sprd/drm.yaml | 38 ++++++++++++++++++++++
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/sprd/drm.yaml
diff --git a/Documentation/devicetree/bindings/display/sprd/drm.yaml b/Documentation/devicetree/bindings/display/sprd/drm.yaml
new file mode 100644
index 0000000..1614ca6
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/sprd/drm.yaml
@@ -0,0 +1,38 @@
+# SPDX-License-Identifier: GPL-2.0
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/sprd/drm.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Unisoc DRM master device
+
+maintainers:
+ - David Airlie <airlied@linux.ie>
+ - Daniel Vetter <daniel@ffwll.ch>
+ - Rob Herring <robh+dt@kernel.org>
+ - Mark Rutland <mark.rutland@arm.com>
+
+description: |
+ The Unisoc DRM master device is a virtual device needed to list all
+ DPU devices or other display interface nodes that comprise the
+ graphics subsystem.
+
+properties:
+ compatible:
+ const: sprd,display-subsystem
+
+ ports:
+ description:
+ Should contain a list of phandles pointing to display interface port
+ of DPU devices.
+
+required:
+ - compatible
+ - ports
+
+examples:
+ - |
+ display-subsystem {
+ compatible = "sprd,display-subsystem";
+ ports = <&dpu_out>;
+ };
\ No newline at end of file
--
2.7.4
next prev parent reply other threads:[~2019-12-16 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 11:40 [PATCH RFC v1 0/6] Add Unisoc's drm kms module Kevin Tang
2019-12-16 11:40 ` Kevin Tang [this message]
2019-12-16 11:40 ` [PATCH RFC v1 2/6] drm/sprd: add Unisoc's drm kms master Kevin Tang
2020-01-06 10:11 ` Thomas Zimmermann
2020-01-06 10:17 ` Thomas Zimmermann
[not found] ` <CAFPSGXbNqZ+GmSdfDnzobxYAx8yQaw+S1N3R3wAQF+GFNTcjZg@mail.gmail.com>
2020-01-07 12:22 ` Thomas Zimmermann
2019-12-16 11:40 ` [PATCH RFC v1 3/6] dt-bindings: display: add Unisoc's dpu bindings Kevin Tang
2019-12-16 11:40 ` [PATCH RFC v1 4/6] drm/sprd: add Unisoc's drm display controller driver Kevin Tang
2019-12-16 11:40 ` [PATCH RFC v1 5/6] dt-bindings: display: add Unisoc's mipi dsi&dphy bindings Kevin Tang
2019-12-16 11:40 ` [PATCH RFC v1 6/6] drm/sprd: add Unisoc's drm mipi dsi&dphy driver Kevin Tang
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=1576496419-12409-2-git-send-email-kevin3.tang@gmail.com \
--to=kevin3.tang@gmail.com \
--cc=airlied@linux.ie \
--cc=baolin.wang@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=zhang.lyra@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;
as well as URLs for NNTP newsgroup(s).