Claude review: drm/v3d: Reduce PM runtime autosuspend delay

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

Patch Review

**Purpose:** With the cache/MMU bugs fixed, the inflated 100ms autosuspend delay is no longer needed. Reduce to 50ms.

**Code change in `v3d_drv.c:423`:**
```c
pm_runtime_set_autosuspend_delay(dev, 50);
```

**Analysis:**
- The rationale is well explained in the commit message: 100ms was a workaround for the bugs fixed in patches 1-3.
- This patch has no `Fixes:` tag, which is correct — it's a tuning change, not a bugfix.
- No `Cc: stable@` either, which is correct — this should not be backported independently of the series.

**Question:** Is 50ms the right value? The commit message says "a more reasonable value" but doesn't cite benchmarks or power measurements. For a desktop/embedded system like RPi4, the difference between 50ms and 100ms is unlikely to matter for power savings but could theoretically increase suspend/resume cycle frequency. This is a judgment call for the maintainers — the value seems reasonable, but some data or a reference to what other GPU drivers use would strengthen the justification. Not a blocker.

**Verdict: Fine as-is; the maintainers can adjust the value at merge time if they prefer a different number.**

---
Generated by Claude Code Patch Reviewer