Claude review: drm/msm: add missing MODULE_DEVICE_ID definitions

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

Patch Review

**Correctness**: All five `MODULE_DEVICE_TABLE` additions reference the correct array names for their respective files. Each array is a `static const struct of_device_id[]` properly terminated with `{}`, as expected.

**Minor observation — generic table name in dsi.c**: The DSI driver uses the generic name `dt_match`:

```c
MODULE_DEVICE_TABLE(of, dt_match);
```

This stands out because `adreno/adreno_device.c` also has a `static const struct of_device_id dt_match[]` (without `MODULE_DEVICE_TABLE`). The `MODULE_DEVICE_TABLE` macro creates a global alias symbol `__mod_of__dt_match_device_table`. Currently this works fine since only `dsi.c` generates that alias. However, if a `MODULE_DEVICE_TABLE(of, dt_match)` were ever added to `adreno_device.c`, it would cause a duplicate symbol at link time. All the other tables use descriptive prefixed names (`msm_dp_dt_match`, `dsi_phy_dt_match`, `msm_hdmi_dt_match`, `msm_hdmi_phy_dt_match`), so `dt_match` is inconsistent. This is a pre-existing naming issue though, not something introduced by this patch, so it's not a blocker.

**Fixes tag**: The tag references `060530f1ea67 ("drm/msm: use componentised device support")`, which introduced the component-based driver model requiring module autoloading for sub-devices. The author's note explains the v2 dropped the GPU chunk (presumably already in `msm-fixes`). The commit message still says "only MDSS (subsystem), KMS devices and GPU have corresponding MODULE_DEVICE_ID tables" — this is slightly misleading post-rebase since the GPU `MODULE_DEVICE_TABLE` doesn't appear to be present in the tree. A minor commit message clarity issue, not a code concern.

**No other issues found.** The placement of each `MODULE_DEVICE_TABLE` immediately after its corresponding match table's closing brace is consistent with kernel conventions.

---
Generated by Claude Code Patch Reviewer