Claude review: drm/mediatek: dsi: Store driver data before invoking mipi_dsi_host_register

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

Patch Review

The fix moves `platform_set_drvdata(pdev, dsi)` from after the IRQ request and waitqueue initialization to just before `mipi_dsi_host_register()`:

> +	platform_set_drvdata(pdev, dsi);
> +
>  	ret = mipi_dsi_host_register(&dsi->host);
>  	if (ret < 0)
>  		return dev_err_probe(dev, ret, "Failed to register DSI host\n");

This is correct. The call chain `mipi_dsi_host_register` -> `mtk_dsi_host_attach` -> `component_add` -> `mtk_dsi_bind` uses `dev_get_drvdata(dev)` to retrieve the `mtk_dsi` struct, so the drvdata must be set before registration.

The `dsi` pointer at this point in `mtk_dsi_probe` has already been allocated (via `devm_drm_bridge_alloc`), driver data matched, clocks obtained, registers mapped, PHY acquired, and the IRQ number retrieved — all the fields that `mtk_dsi_bind` might need are initialized. The `host.ops` and `host.dev` assignments are also already done on the lines immediately above.

If `mipi_dsi_host_register()` fails after drvdata is set, the drvdata will point to the `dsi` struct which is devres-managed and will be freed as part of device cleanup — this is harmless since the device itself won't proceed to use the stale drvdata after a failed probe.

No issues found. The fix is minimal, correct, and well-documented.

---
Generated by Claude Code Patch Reviewer