diff options
| author | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2019-09-24 16:17:02 +0300 |
|---|---|---|
| committer | Andrzej Hajda <a.hajda@samsung.com> | 2019-10-10 11:15:45 +0200 |
| commit | fd70c7755bf0172ddd33b558aef69c322de3b5cf (patch) | |
| tree | e9ae6d95bc8117c8f4038a1e21b2e9ddb87f8ba2 /lib/debug_locks.c | |
| parent | cc635be34eb672a30a4936db30987b7c2e91fb61 (diff) | |
drm/bridge: tc358767: fix max_tu_symbol valuedrm-misc-fixes-2019-10-10
max_tu_symbol was programmed to TU_SIZE_RECOMMENDED - 1, which is not
what the spec says. The spec says:
roundup ((input active video bandwidth in bytes/output active video
bandwidth in bytes) * tu_size)
It is not quite clear what the above means, but calculating
max_tu_symbol = (input Bps / output Bps) * tu_size seems to work and
fixes the issues seen.
This fixes artifacts in some videomodes (e.g. 1024x768@60 on 2-lanes &
1.62Gbps was pretty bad for me).
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Tested-by: Jyri Sarha <jsarha@ti.com>
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190924131702.9988-1-tomi.valkeinen@ti.com
Diffstat (limited to 'lib/debug_locks.c')
0 files changed, 0 insertions, 0 deletions