diff options
author | 2025-06-25 17:14:35 +0200 | |
---|---|---|
committer | 2025-07-16 17:24:51 +0200 | |
commit | 2bf85c45db96d83e082daa2903fd2a3019b7ad18 (patch) | |
tree | da6f45d49b33a4d0040cbba76b8ad1667a6df4e9 /tools/perf/scripts/python | |
parent | drm/panel/boe-himax8279d: Use refcounted allocation in place of devm_kzalloc() (diff) | |
download | wireguard-linux-2bf85c45db96d83e082daa2903fd2a3019b7ad18.tar.xz wireguard-linux-2bf85c45db96d83e082daa2903fd2a3019b7ad18.zip |
drm/tests: edid: Fix monitor range limits
For some reason, some EDIDs used by kunit had Monitor Range Limits
making no sense, and not matching the edid-decode output in the comment.
While they were in the comments as:
Display Range Limits:
Monitor ranges (GTF): 50-70 Hz V, 30-70 kHz H, max dotclock 150 MHz
They were actually:
Display Range Limits:
Monitor ranges (GTF): 50-70 Hz V, 0-0 kHz H, max dotclock 1960 MHz
Fix that section of the EDIDs to match the expected edid-decode output.
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Link: https://lore.kernel.org/r/20250625-drm-update-edid-v1-1-2d963743ab9e@kernel.org
Signed-off-by: Maxime Ripard <mripard@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions