Claude review: drm/msm/dsi: Add support for RGB101010 pixel format

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

Patch Review

**Critical dependency issue:** This patch references `MIPI_DSI_FMT_RGB101010`, `VID_DST_FORMAT_RGB101010`, and `CMD_DST_FORMAT_RGB101010`. The latter two are added by the dsi.xml changes in this patch, but `MIPI_DSI_FMT_RGB101010` is not defined anywhere in the current kernel's `include/drm/drm_mipi_dsi.h`. This series will not compile without a prerequisite patch adding that enum value. The cover letter should state this dependency.

**Register definition change:**

```xml
-		<bitfield name="DST_FORMAT" low="4" high="5" type="dsi_vid_dst_format"/>
+		<!-- high was 5 before DSI 6G 2.1.0 -->
+		<bitfield name="DST_FORMAT" low="4" high="6" type="dsi_vid_dst_format"/>
```

Extending VID_CFG0 DST_FORMAT from 2 bits (high=5) to 3 bits (high=6) is necessary to encode value 4 (`RGB101010`). The comment noting this changed in DSI 6G 2.1.0 is helpful. However, this means on older hardware (< V2.1.0), writing value 4 would spill into bit 6 which could be problematic — but the version guard in `dsi_host_attach` prevents `RGB101010` from being used on older hardware, so this is safe.

**Guard logic is correct:**

```c
+	if (dsi->format == MIPI_DSI_FMT_RGB101010 &&
+	    !msm_dsi_host_version_ge(msm_host, MSM_DSI_VER_MAJOR_6G,
+				     MSM_DSI_6G_VER_MINOR_V2_1_0)) {
```

This correctly rejects RGB101010 on controllers older than V2.1.0. Note this also rejects non-6G controllers (major != 0x03) which is appropriate.

**Minor observation:** The `default:` case in both `dsi_get_vid_fmt` and `dsi_get_cmd_fmt` silently returns `RGB888`/`RGB888` for any unknown format. This was already the behavior and is unchanged, so not a concern introduced by this patch.

---
Generated by Claude Code Patch Reviewer