On 4/22/21 10:43 AM, Jagan Teki wrote:
[...]
diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
new file mode 100644
index 000000000000..42d11b46a1eb
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
@@ -0,0 +1,134 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/bridge/ti,sn65dsi83.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: SN65DSI83 and SN65DSI84 DSI to LVDS bridge chip
Can it possible to wait for my v4 to have dual-link LVDS supported
which is quite discussing points on previous versions?
This driver already has the dual-link LVDS support on DSI84 and it is
tested on real hardware. So is the single-link LVDS on DSI83, on
multiple hardware instances.
In addition to that, this driver has proper regmap support and constant
time calculation of DSI83/84 clock register settings.
Note that I did wait for your v4 for over two weeks already, it just
didn't materialize, so I determined it might be a good idea to restart
work on this driver instead.
Maybe you can test this driver and check what is missing for your usecase?
