diff options
| author | Marijn Suijten <marijn.suijten@somainline.org> | 2021-04-07 00:47:24 +0300 |
|---|---|---|
| committer | Rob Clark <robdclark@chromium.org> | 2021-04-09 22:02:35 +0300 |
| commit | 2ad52bdb220de5ab348098e3482b01235d15a842 (patch) | |
| tree | a63a7ae72b1f6cc179d5d2ec243b090912c9eef2 /lib/memory-notifier-error-inject.c | |
| parent | dc8a4973fd6916c050898d803a8e1d7b8fc59f70 (diff) | |
| download | linux-2ad52bdb220de5ab348098e3482b01235d15a842.tar.xz | |
drm/msm/mdp5: Configure PP_SYNC_HEIGHT to double the vtotal
Leaving this at a close-to-maximum register value 0xFFF0 means it takes
very long for the MDSS to generate a software vsync interrupt when the
hardware TE interrupt doesn't arrive. Configuring this to double the
vtotal (like some downstream kernels) leads to a frame to take at most
twice before the vsync signal, until hardware TE comes up.
In this case the hardware interrupt responsible for providing this
signal - "disp-te" gpio - is not hooked up to the mdp5 vsync/pp logic at
all. This solves severe panel update issues observed on at least the
Xperia Loire and Tone series, until said gpio is properly hooked up to
an irq.
Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Signed-off-by: Marijn Suijten <marijn.suijten@somainline.org>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Link: https://lore.kernel.org/r/20210406214726.131534-2-marijn.suijten@somainline.org
Signed-off-by: Rob Clark <robdclark@chromium.org>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions