From: syyang <syyang@lontium.com>
To: robh@kernel.org
Cc: Laurent.pinchart@ideasonboard.com, andrzej.hajda@intel.com,
conor+dt@kernel.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, jernej.skrabec@gmail.com,
jonas@kwiboo.se, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, neil.armstrong@linaro.org,
rfoss@kernel.org, syyang@lontium.com, yangsunyun1993@gmail.com
Subject: [PATCH v2 1/2] This patch adds a new device tree binding documentation.
Date: Wed, 3 Sep 2025 19:25:24 -0700 [thread overview]
Message-ID: <20250904022524.1748587-1-syyang@lontium.com> (raw)
In-Reply-To: <175691717884.2393851.6340903042726389490.robh@kernel.org>
Fix device tree binding validation errors reported by Rob Herring.
v2:
- Fixed $id field to match actual filename (lontium,lt9611c.yaml)
- build pass
Thanks to Rob Herring for the review and feedback.
Signed-off-by: syyang <syyang@lontium.com>
---
.../display/bridge/lontium,lt9611c.yaml | 121 ++++++++++++++++++
1 file changed, 121 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml
diff --git a/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml b/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml
new file mode 100644
index 000000000000..712644da4f1d
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml
@@ -0,0 +1,121 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/bridge/lontium,lt9611c.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Lontium LT9611C 2 Port MIPI to HDMI Bridge
+
+maintainers:
+ - Rob Herring <robh@kernel.org>
+
+description: |
+ The LT9611C are bridge devices which convert DSI to HDMI
+
+properties:
+ compatible:
+ enum:
+ - lontium,lt9611c
+
+ reg:
+ maxItems: 1
+
+ "#sound-dai-cells":
+ const: 0
+
+ interrupts:
+ maxItems: 1
+
+ reset-gpios:
+ maxItems: 1
+ description: GPIO connected to active high RESET pin.
+
+ vdd-supply:
+ description: Regulator for 1.2V MIPI phy power.
+
+ vcc-supply:
+ description: Regulator for 3.3V IO power.
+
+ ports:
+ $ref: /schemas/graph.yaml#/properties/ports
+
+ properties:
+ port@0:
+ $ref: /schemas/graph.yaml#/properties/port
+ description:
+ Primary MIPI port-1 for MIPI input
+
+ port@1:
+ $ref: /schemas/graph.yaml#/properties/port
+ description:
+ Additional MIPI port-2 for MIPI input, used in combination
+ with primary MIPI port-1 to drive higher resolution displays
+
+ port@2:
+ $ref: /schemas/graph.yaml#/properties/port
+ description:
+ HDMI port for HDMI output
+
+ required:
+ - port@0
+ - port@2
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - vdd-supply
+ - vcc-supply
+ - ports
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ i2c10 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ hdmi-bridge@41 {
+ compatible = "lontium,lt9611c";
+ reg = <0x41>;
+ #sound-dai-cells = <0>;
+ interrupts-extended = <&pio 128 GPIO_ACTIVE_HIGH>;
+ reset-gpios = <&pio 127 GPIO_ACTIVE_HIGH>;
+ vdd-supply = <<9611_1v2>;
+ vcc-supply = <<9611_3v3>;
+ status = "okay";
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port@0 {
+ reg = <0>;
+ lt9611_a: endpoint {
+ remote-endpoint = <&dsi0_out>;
+ };
+ };
+
+ port@1 {
+ reg = <1>;
+ lt9611_b: endpoint {
+ remote-endpoint = <&dsi1_out>;
+ };
+ };
+
+ port@2 {
+ reg = <2>;
+ lt9611_out: endpoint {
+ remote-endpoint = <&hdmi_con>;
+ };
+ };
+ };
+ };
+ };
+
+...
+
--
2.25.1
next prev parent reply other threads:[~2025-09-04 2:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 12:38 [PATCH v1 0/2] Add LT9611C DRM bridge driver and device tree binding syyang
2025-09-03 12:38 ` [PATCH v1 1/2] This patch adds a new device tree binding documentation syyang
2025-09-03 16:33 ` Rob Herring (Arm)
2025-09-04 2:25 ` syyang [this message]
2025-09-04 2:53 ` [PATCH v2 " Dmitry Baryshkov
2025-09-04 5:49 ` Krzysztof Kozlowski
2025-09-04 8:08 ` 杨孙运
2025-09-04 8:26 ` Krzysztof Kozlowski
2025-09-04 11:27 ` 杨孙运
2025-09-04 2:21 ` [PATCH v1 " Dmitry Baryshkov
[not found] ` <CAFQXuNYKcGHyWLD5hjj24CrbaXzkaKsLU4R2vmhYaryQArA_yQ@mail.gmail.com>
2025-09-04 2:56 ` Dmitry Baryshkov
2025-09-03 12:38 ` [PATCH v1 2/2] This patch adds a new DRM bridge driver for the Lontium LT9611C chip syyang
2025-09-04 2:52 ` Dmitry Baryshkov
2025-09-04 10:48 ` 杨孙运
2025-09-04 11:04 ` Krzysztof Kozlowski
2025-09-04 11:17 ` 杨孙运
2025-09-04 14:39 ` Dmitry Baryshkov
2025-09-05 2:55 ` 杨孙运
2025-09-05 8:10 ` neil.armstrong
2025-09-05 8:58 ` 杨孙运
2025-09-05 14:24 ` Dmitry Baryshkov
2025-09-08 1:14 ` 杨孙运
2025-09-08 10:17 ` Dmitry Baryshkov
2025-09-05 14:10 ` Dmitry Baryshkov
2025-09-08 11:03 ` Jani Nikula
2025-09-08 11:07 ` Jani Nikula
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=20250904022524.1748587-1-syyang@lontium.com \
--to=syyang@lontium.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=yangsunyun1993@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
all inboxes | Powered by JetHome®