Claude review: Re: [PATCH 5/6] arm64: dts: qcom: qcs6490-radxa-dragon-q6a: Enable GPU and display pipeline

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

**Issue 1 — `dp-connector` used as a bridge.** The `hdmi-bridge` node uses `compatible = "dp-connector"`:

```dts
+	hdmi-bridge {
+		compatible = "dp-connector";
+		label = "hdmi";
+		type = "full-size";
```

The `dp-connector` binding (Documentation/devicetree/bindings/display/connector/dp-connector.yaml) represents a *physical DP connector* — the port where you plug in a DP cable. The RA620 is not a DP connector; it's a DP-to-HDMI bridge. Using `dp-connector` to model a bridge is semantically incorrect.

Furthermore, the `dp-connector` binding defines port@1 as "Connection to controller providing AUX signals." This patch uses port@1 as an output to the HDMI connector, which doesn't match the binding:

```dts
+			port@1 {
+				reg = <1>;
+				hdmi_bridge_out: endpoint {
+					remote-endpoint = <&hdmi_connector_in>;
+				};
+			};
```

**Issue 2 — Naming confusion.** The node is called `hdmi-bridge` but uses `dp-connector` compatible. The label is "hdmi" but it's a DP endpoint. This will confuse future readers.

**Issue 3 — pinctrl on "connector" node.** The `dp_hot_plug_det` pinctrl is attached to the `hdmi-bridge` (dp-connector) node. HPD pinctrl would more typically belong on the DP controller node (`&mdss_dp`).

The GPU enable parts (`gpucc`, `gmu`, `dispcc`, `mdss` status = "okay") and the disabling of DSI/eDP interfaces are all fine.

---

---
Generated by Claude Code Patch Reviewer