diff options
| author | Mitul Golani <mitulkumar.ajitkumar.golani@intel.com> | 2026-07-30 16:29:14 +0530 |
|---|---|---|
| committer | Suraj Kandpal <suraj.kandpal@intel.com> | 2026-08-03 10:32:43 +0530 |
| commit | 9083322aa83d680daca956c5c63a5912f8e11f9c (patch) | |
| tree | 362f2a0784e2606548cf0485970d41ee9d8efaeb /tools/perf/scripts/python/stackcollapse.py | |
| parent | 39ca58943e4666c49eb568cf9c5c6b19e5042eb8 (diff) | |
| download | linux-9083322aa83d680daca956c5c63a5912f8e11f9c.tar.gz linux-9083322aa83d680daca956c5c63a5912f8e11f9c.zip | |
drm/i915/vrr: Latch CMRR ratio via atomic commit on debugfs write
Writing the per-CRTC "intel_vrr_target_refresh_rate" debugfs file only
updates crtc->force_cmrr, a side channel that is not tracked by the
atomic state. The requested ratio therefore does not reach the hardware
until some unrelated commit recomputes the pipe config.
Kick an internal atomic commit for the CRTC from the debugfs write and
mark the CRTC mode as changed so the pipe config is recomputed.
Note that this commit may or may not be downgraded to a fastset,
depending on whether the computed vblank value (with LRR disabled)
changes, so it is not characterised as a fastset.
If the commit fails, restore the previous numerator/denominator so that
force_cmrr does not hold on to bad values, which would otherwise make
all subsequent commits fail.
--v2:
- Commit message and code comment update (Chaitanya)
- Commit header update
- Restore to old known debugfs values when commit fails
(Chaitanya)
Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Link: https://patch.msgid.link/20260730105919.3913412-8-mitulkumar.ajitkumar.golani@intel.com
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
