From: Alibek Omarov <a1ba.omarov@gmail.com>
To: linux-rockchip@lists.infradead.org
Cc: Alibek Omarov <a1ba.omarov@gmail.com>
Subject: [RFC PATCH 3/3] dt-bindings: display: rockchip-lvds: add compatible string for RK3568
Date: Fri, 23 Sep 2022 19:01:15 +0300 [thread overview]
Message-ID: <20220923160115.2946615-4-a1ba.omarov@gmail.com> (raw)
In-Reply-To: <20220923160115.2946615-1-a1ba.omarov@gmail.com>
RK3568 SoCs have a single LVDS output, that use PHY shared by two display
pipelines: LVDS and MIPI DSI.
Signed-off-by: Alibek Omarov <a1ba.omarov@gmail.com>
---
.../devicetree/bindings/display/rockchip/rockchip-lvds.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip-lvds.txt b/Documentation/devicetree/bindings/display/rockchip/rockchip-lvds.txt
index aaf8c44cf90f..ec8a8d05368a 100644
--- a/Documentation/devicetree/bindings/display/rockchip/rockchip-lvds.txt
+++ b/Documentation/devicetree/bindings/display/rockchip/rockchip-lvds.txt
@@ -5,6 +5,7 @@ Required properties:
- compatible: matching the soc type, one of
- "rockchip,rk3288-lvds";
- "rockchip,px30-lvds";
+ - "rockchip,rk3568-lvds";
- reg: physical base address of the controller and length
of memory mapped region.
--
2.25.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2022-09-23 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 16:01 [RFC PATCH 0/3] rockchip-lvds for rk3568 Alibek Omarov
2022-09-23 16:01 ` [RFC PATCH 1/3] drm/rockchip: lvds: add rk3568 support Alibek Omarov
2022-09-23 16:01 ` [RFC PATCH 2/3] arm64: dts: rockchip: rk356x: add LVDS bindings Alibek Omarov
2022-11-16 13:19 ` Sverdlin, Alexander
2022-11-16 15:09 ` Alibek Omarov
2022-11-18 18:06 ` Sverdlin, Alexander
2022-11-18 18:52 ` Alibek Omarov
2023-01-31 13:33 ` Johan Jonker
2023-01-31 18:21 ` Alibek Omarov
2022-09-23 16:01 ` Alibek Omarov [this message]
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=20220923160115.2946615-4-a1ba.omarov@gmail.com \
--to=a1ba.omarov@gmail.com \
--cc=linux-rockchip@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