On 12-08-2025 19:58, Conor Dooley wrote:
On Tue, Aug 12, 2025 at 04:51:34PM +0200, Mike Looijmans wrote:
Add DT binding document for TI TMDS181 and SN65DP159 HDMI retimers.
Signed-off-by: Mike Looijmans <mike.looijm...@topic.nl>
---
.../bindings/display/bridge/ti,tmds181.yaml | 104 ++++++++++++++++++
1 file changed, 104 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/bridge/ti,tmds181.yaml
diff --git a/Documentation/devicetree/bindings/display/bridge/ti,tmds181.yaml
b/Documentation/devicetree/bindings/display/bridge/ti,tmds181.yaml
new file mode 100644
index 000000000000..87ffb556c4ad
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/ti,tmds181.yaml
@@ -0,0 +1,104 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/bridge/ti,tmds181.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: TMDS181 and SN65DP159 HDMI retimer/redriver chips
+
+maintainers:
+ - Mike Looijmans <mike.looijm...@topic.nl>
+
+description: |
+ Texas Instruments TMDS181 and SN65DP159 retimer and redriver chips.
+ https://www.ti.com/product/TMDS181
+ https://www.ti.com/product/TMDS181
These two links are the same.
Will fix in v3
+
+properties:
+ compatible:
+ enum:
+ - ti,tmds181
+ - ti,sn65dp159
The driver contains:
+ { .compatible = "ti,tmds181", },
+ { .compatible = "ti,sn65dp159", },
+ {}
so why is a fallback compatible not suitable here?
I don't understand the question. The two are slightly different chips,
so it makes sense to describe that in the DT.
--
Mike Looijmans
