Claude review: drm/amd/display: dmub_cmd.h: correct typos and spellos

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

Patch Review

**Status: Good to merge.**

This patch fixes 20+ spelling errors identified by codespell and a handful found manually. All corrections are straightforward and obviously correct:

- `alighment` → `alignment` (1x)
- `sequeunce` → `sequence` (1x)
- `optimzations` → `optimizations` (3x)
- `isntance` → `instance` (16x)
- `re-use` → `reuse` (1x)
- `dicated` → `dictated` (7x)
- `afftet` → `after` (1x)

The `afftet` → `after` fix deserves a note. The resulting comment reads:
```c
/*
 * Use FSFT after pixel clk
 */
uint32_t pix_clk_100hz;
```
This is grammatically terse but plausible in context — the adjacent field `sink_pix_clk_100hz` has the comment "Use Original pixel clock", so "after" likely means "after FSFT adjustment". The original `afftet` was clearly garbled, and `after` is the best reasonable interpretation.

Randy's open questions about pre-existing comment/field mismatches are well-spotted:
- **(a)** `dark_pos_gain` with comment "Dark negative gain" — "pos" and "negative" contradict each other.
- **(b)/(c)** `min_frame_rate` has comment "Maximum frame rate" and `max_frame_rate` has "Minimum frame rate" — the comments are clearly swapped.

These are real bugs in the existing documentation but are correctly left out of this patch, as they require AMD domain knowledge to resolve which name (field vs comment) is correct. A follow-up fix from the AMD display team would be appropriate.

One very minor nit: the double period at the end of this comment was not fixed:
```c
 * 16-bit value dictated by driver that indicates the vtotal in PSR active requirement when screen idle..
```
The trailing `..` should probably be a single `.`, but that's pre-existing and doesn't affect the correctness of this patch.

---
Generated by Claude Code Patch Reviewer