diff options
author | Linus Walleij <linus.walleij@linaro.org> | 2021-06-09 00:33:18 +0300 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2021-06-09 15:03:29 +0300 |
commit | c8a570443943304cac2e4186dbce6989b6c2b8b5 (patch) | |
tree | 99769f54f2aae951c32c233ef9494df399943425 /fs/sysv | |
parent | b436acd1cf7fac0ba987abd22955d98025c80c2b (diff) | |
download | linux-c8a570443943304cac2e4186dbce6989b6c2b8b5.tar.xz |
drm/mcde: Fix off by 10^3 in calculation
The calclulation of how many bytes we stuff into the
DSI pipeline for video mode panels is off by three
orders of magnitude because we did not account for the
fact that the DRM mode clock is in kilohertz rather
than hertz.
This used to be:
drm_mode_vrefresh(mode) * mode->htotal * mode->vtotal
which would become for example for s6e63m0:
60 x 514 x 831 = 25628040 Hz, but mode->clock is
25628 as it is in kHz.
This affects only the Samsung GT-I8190 "Golden" phone
right now since it is the only MCDE device with a video
mode display.
Curiously some specimen work with this code and wild
settings in the EOL and empty packets at the end of the
display, but I have noticed an eeire flicker until now.
Others were not so lucky and got black screens.
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reported-by: Stephan Gerhold <stephan@gerhold.net>
Fixes: 920dd1b1425b ("drm/mcde: Use mode->clock instead of reverse calculating it from the vrefresh")
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Tested-by: Stephan Gerhold <stephan@gerhold.net>
Reviewed-by: Stephan Gerhold <stephan@gerhold.net>
Link: https://patchwork.freedesktop.org/patch/msgid/20210608213318.3897858-1-linus.walleij@linaro.org
Diffstat (limited to 'fs/sysv')
0 files changed, 0 insertions, 0 deletions