✗ CI.checkpatch: warning for i915: Fix HBLANK Expansion Quirk Causing Modeset Failure on Dell WD19TB Dock at 3440x1440 at 100Hz
Patchwork
patchwork at emeril.freedesktop.org
Mon Sep 30 20:08:57 UTC 2024
== Series Details ==
Series: i915: Fix HBLANK Expansion Quirk Causing Modeset Failure on Dell WD19TB Dock at 3440x1440 at 100Hz
URL : https://patchwork.freedesktop.org/series/139320/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 0183e57c4a01abfa678bd1b6a9c0cd8cf22386cb
Author: Benjamin Hoefs <bendhoefs at gmail.com>
Date: Wed Sep 25 19:25:34 2024 -0500
i915: Fix HBLANK Expansion Quirk Causing Modeset Failure on Dell WD19TB Dock at 3440x1440 at 100Hz
Hello,
I am using a Dell WD19TB dock with a 3440x1440 monitor. Using it at
100Hz used to work but recently I tried it again and discovered it no longer
did, specifically the modeset seems to silently fail with no error message in
userspace utilities like kscreen-doctor and xrandr and no output in dmesg.
I found the problematic commit using git bisect to be
55eaef164174480df6827edeac15620f3cbcd52b "Handle the Synaptics HBlank
expansion quirk".
I found the issue to be the hblank_expasion_quirk_needs_dsc function which uses
the following comparison in the current kernel tree:
if (mode_hblank_period_ns(adjusted_mode) > hblank_limit)
return false;
with hblank_limit being earlier set as
int hblank_limit = is_uhbr_sink ? 500 : 300;
However, my monitor's HBLANK period in the 3440x1440 at 100Hz mode is
exactly 300 ns as verified by this printk immediately before the
problematic comparison.
printk(KERN_INFO "Hello, kernel world! %i\n",
mode_hblank_period_ns(adjusted_mode));
[ 38.429839] Hello, kernel world! 300
With the attached change the modeset works as expected at 100Hz. Would it be
acceptable to modify the comparison from > to >= here?
I'll do my best to provide any additional details you may need although
that printk and '=' sign is the only kernel code I've written, so my best may
not be great :).
Signed-off-by: Benjamin D. Hoefs <bendhoefs at gmail.com>
+ /mt/dim checkpatch 4e4d7873ac763aa0bd9207ea9ec2b89bb52a6fe1 drm-intel
0183e57c4a01 i915: Fix HBLANK Expansion Quirk Causing Modeset Failure on Dell WD19TB Dock at 3440x1440 at 100Hz
-:10: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#10:
100Hz used to work but recently I tried it again and discovered it no longer
-:14: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 55eaef164174 ("drm/i915/dp_mst: Handle the Synaptics HBlank expansion quirk")'
#14:
55eaef164174480df6827edeac15620f3cbcd52b "Handle the Synaptics HBlank
-:56: WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email name mismatch: 'From: Benjamin Hoefs <bendhoefs at gmail.com>' != 'Signed-off-by: Benjamin D. Hoefs <bendhoefs at gmail.com>'
total: 1 errors, 2 warnings, 0 checks, 8 lines checked
More information about the Intel-xe
mailing list