- New device tree binding documentation at
Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml
Signed-off-by: syyang <syyang@lontium.com>
---
.../display/bridge/lontium,lt9611c.yaml | 123 ++++++++++++++++++
1 file changed, 123 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..e8f204c71a95
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml
@@ -0,0 +1,123 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/bridge/lontium,lt9611.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
+ - lontium,lt9611uxd
+
+ 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>;
+ dsi-lanes = <4>;
+ 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
On Wed, Sep 03, 2025 at 05:38:24AM -0700, syyang wrote: > - New device tree binding documentation at > Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml > > Signed-off-by: syyang <syyang@lontium.com> Please fix your Git setup and use your full name in SoB tag and author metadata. > --- > .../display/bridge/lontium,lt9611c.yaml | 123 ++++++++++++++++++ > 1 file changed, 123 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..e8f204c71a95 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml > @@ -0,0 +1,123 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/display/bridge/lontium,lt9611.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Lontium LT9611C 2 Port MIPI to HDMI Bridge > + > +maintainers: > + - Rob Herring <robh@kernel.org> Are you sure? > + > +description: | > + The LT9611C are bridge devices which convert DSI to HDMI Can't you extend the existing lontium,lt9611.yaml? > + > +properties: > + compatible: > + enum: > + - lontium,lt9611c > + - lontium,lt9611uxd > + > + 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 All of this totally looks like lontium,lt9611.yaml, except the vdd-supply voltage difference. > + > +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>; > + dsi-lanes = <4>; > + 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 > -- With best wishes Dmitry
On Wed, 03 Sep 2025 05:38:24 -0700, syyang wrote: > - New device tree binding documentation at > Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml > > Signed-off-by: syyang <syyang@lontium.com> > --- > .../display/bridge/lontium,lt9611c.yaml | 123 ++++++++++++++++++ > 1 file changed, 123 insertions(+) > create mode 100644 Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml > My bot found errors running 'make dt_binding_check' on your patch: yamllint warnings/errors: dtschema/dtc warnings/errors: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml: warning: ignoring duplicate '$id' value 'http://devicetree.org/schemas/display/bridge/lontium,lt9611.yaml#' /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml: $id: Cannot determine base path from $id, relative path/filename doesn't match actual path or filename $id: http://devicetree.org/schemas/display/bridge/lontium,lt9611.yaml file: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.yaml Documentation/devicetree/bindings/display/bridge/lontium,lt9611c.example.dtb: /example-0/i2c10/hdmi-bridge@41: failed to match any schema with compatible: ['lontium,lt9611c'] doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250903123825.1721443-2-syyang@lontium.com The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.
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
On 04/09/2025 04:25, syyang wrote: > Fix device tree binding validation errors reported by Rob Herring. > > v2: That's not the place where you put changelog. > - Fixed $id field to match actual filename (lontium,lt9611c.yaml) > - build pass > > Thanks to Rob Herring for the review and feedback. Please carefully read submitting patches. Do not attach (thread) your patchsets to some other threads (unrelated or older versions). This buries them deep in the mailbox and might interfere with applying entire sets. See also: https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830 Please use subject prefixes matching the subsystem. You can get them for example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory your patch is touching. For bindings, the preferred subjects are explained here: https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters > > 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> No, how so? > + > +description: | Do not need '|' unless you need to preserve formatting. > + The LT9611C are bridge devices which convert DSI to HDMI Why this cannot be added to lt9611 binding? Commit msg should clearly answer that. > + > +properties: > + compatible: > + enum: > + - lontium,lt9611c > + > + reg: > + maxItems: 1 > + > + "#sound-dai-cells": Missing dai-common ref. > + 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"; Nope, drop. Best regards, Krzysztof
Krzysztof Kozlowski <krzk@kernel.org> 于2025年9月4日周四 13:49写道: > > On 04/09/2025 04:25, syyang wrote: > > Fix device tree binding validation errors reported by Rob Herring. > > > > v2: > > That's not the place where you put changelog. > I'm currently learning what to do. Thank you > > - Fixed $id field to match actual filename (lontium,lt9611c.yaml) > > - build pass > > > > Thanks to Rob Herring for the review and feedback. > > Please carefully read submitting patches. > I'm currently learning what to do. Thank you > Do not attach (thread) your patchsets to some other threads (unrelated > or older versions). This buries them deep in the mailbox and might > interfere with applying entire sets. See also: > https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830 > > Please use subject prefixes matching the subsystem. You can get them for > example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory > your patch is touching. For bindings, the preferred subjects are > explained here: > https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters > I'm currently learning what to do. Thank you. > > > > 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> > > No, how so? > I will change it to the email address I use when working at the company. (syyang@lontium.com) > > + > > +description: | > > Do not need '|' unless you need to preserve formatting. > Both lontium,lt9211.yaml and lontium,lt9611.yaml use "|", so please confirm if they need to be removed. > > + The LT9611C are bridge devices which convert DSI to HDMI > > Why this cannot be added to lt9611 binding? Commit msg should clearly > answer that. > The lt9611 and lt9611c are chips of different specifications, and their related parameters are different. The VDD-supply of lt9611c is 1.2V; the vdd-supply of lt9611uxc is also 1.2V, while the vdd-supply of lt9611 is 1.8V. Now lt9611 and lt9611uxc are connected together. I'm not sure if this is a problem. If this lt9611c can also be bound to lt9611, and if you think it's okay, then I have no problem. > > + > > +properties: > > + compatible: > > + enum: > > + - lontium,lt9611c > > + > > + reg: > > + maxItems: 1 > > + > > + "#sound-dai-cells": > > Missing dai-common ref. > I don't understand . I referred to: Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml > > + 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"; > > Nope, drop. > remove status = "okay" ? > > > Best regards, > Krzysztof
On Thu, Sep 04, 2025 at 04:08:30PM +0800, 杨孙运 wrote: > > > + > > > +description: | > > > > Do not need '|' unless you need to preserve formatting. > > > Both lontium,lt9211.yaml and lontium,lt9611.yaml use "|", so please > confirm if they need to be removed. Add code which is needed, not code which you found somewhere. Why '|' is needed here? > > > > + The LT9611C are bridge devices which convert DSI to HDMI > > > > Why this cannot be added to lt9611 binding? Commit msg should clearly > > answer that. > > > The lt9611 and lt9611c are chips of different specifications, and > their related parameters are different. > The VDD-supply of lt9611c is 1.2V; the vdd-supply of lt9611uxc is also > 1.2V, while the vdd-supply of lt9611 is 1.8V. > Now lt9611 and lt9611uxc are connected together. I'm not sure if this > is a problem. > If this lt9611c can also be bound to lt9611, and if you think it's > okay, then I have no problem. It is not a problem. > > > > + > > > +properties: > > > + compatible: > > > + enum: > > > + - lontium,lt9611c > > > + > > > + reg: > > > + maxItems: 1 > > > + > > > + "#sound-dai-cells": > > > > Missing dai-common ref. > > > I don't understand . I referred to: > Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml > Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml > You call this device a DAI, so your binding should reference dai-common schema, like every other one. You can check simple codecs for examples. > > > + 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"; > > > > Nope, drop. > > > remove status = "okay" ? Yes. Instead of asking me, you can try to think about possibilities. Ask yourself yourself - why do you need it here? What changes if you have it? What changes if you drop it? Why reviewer asks for it - maybe there is something behind. That way you will learn more about this. I suggest to go through the slides of my OSSE25 talk about DT for beginners. Best regards, Krzysztof
Krzysztof Kozlowski <krzk@kernel.org> 于2025年9月4日周四 16:26写道: > > On Thu, Sep 04, 2025 at 04:08:30PM +0800, 杨孙运 wrote: > > > > + > > > > +description: | > > > > > > Do not need '|' unless you need to preserve formatting. > > > > > Both lontium,lt9211.yaml and lontium,lt9611.yaml use "|", so please > > confirm if they need to be removed. > > Add code which is needed, not code which you found somewhere. Why '|' is > needed here? > '|' It feels more comfortable to me to write the description text after a line break. '|' When there's only one line of description text, it can be omitted. > > > > > > + The LT9611C are bridge devices which convert DSI to HDMI > > > > > > Why this cannot be added to lt9611 binding? Commit msg should clearly > > > answer that. > > > > > The lt9611 and lt9611c are chips of different specifications, and > > their related parameters are different. > > The VDD-supply of lt9611c is 1.2V; the vdd-supply of lt9611uxc is also > > 1.2V, while the vdd-supply of lt9611 is 1.8V. > > Now lt9611 and lt9611uxc are connected together. I'm not sure if this > > is a problem. > > If this lt9611c can also be bound to lt9611, and if you think it's > > okay, then I have no problem. > > It is not a problem. > Do you think it can be merged with lt9611 and lt9611uxc? > > > > > > + > > > > +properties: > > > > + compatible: > > > > + enum: > > > > + - lontium,lt9611c > > > > + > > > > + reg: > > > > + maxItems: 1 > > > > + > > > > + "#sound-dai-cells": > > > > > > Missing dai-common ref. > > > > > I don't understand . I referred to: > > Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml > > Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml > > > > > You call this device a DAI, so your binding should reference dai-common > schema, like every other one. You can check simple codecs for examples. > i will fix , thks > > > > + 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"; > > > > > > Nope, drop. > > > > > remove status = "okay" ? > > Yes. Instead of asking me, you can try to think about possibilities. > Ask yourself yourself - why do you need it here? What changes if you > have it? What changes if you drop it? Why reviewer asks for it - maybe > there is something behind. That way you will learn more about this. > > I suggest to go through the slides of my OSSE25 talk about DT for > beginners. > thanks, > Best regards, > Krzysztof >
On Wed, Sep 03, 2025 at 07:25:24PM -0700, syyang wrote: > 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. Read Documentation/process/submitting-patches.rst > > 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 > -- With best wishes Dmitry
© 2016 - 2025 Red Hat, Inc.