dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110671] Regression: DP outputs out of sync on dual-DP tiled 5k screen
Date: Thu, 08 Aug 2019 20:41:59 +0000	[thread overview]
Message-ID: <bug-110671-502-8FZQzuJhHC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110671-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1095 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110671

--- Comment #10 from Denys <d.budelkov@gmail.com> ---
Just added some debug to rc3 and tried to check what happens(in context of
5fc0cbfad4564856ee0f323d3f88a7cff19cc3f1).

So in program_timing_sync() there is preparing of groups of pipes for sync. 
And looks like(in my case) pipe_set[j]->plane_state is always true, 
and all elements > 0 is removed from the pipe_set in this case, 
hence group_size == 1 and dc->hwss.enable_timing_synchronization() newer
called.

Contrary with old check
!pipe_set[j]->stream_res.tg->funcs->is_blanked(pipe_set[j]->stream_res.tg) is
always false and we have our sync.

Maybe it should be !pipe_set[j]->plane_state instead of
pipe_set[j]->plane_state ?
I applied this change to my 5.3.0-rc3 build and so far everything looks ok.

I do not understand the purpose of is_blanked or plane_state, maybe with mst
hubs or other stuff it may be a different story, but in my simple config it
looks like just a typo.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1924 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-08-08 20:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 11:04 [Bug 110671] Regression: DP outputs out of sync on dual-DP tiled 5k screen bugzilla-daemon
2019-05-13 13:25 ` bugzilla-daemon
2019-05-13 19:22 ` bugzilla-daemon
2019-05-13 19:23 ` bugzilla-daemon
2019-05-13 19:38 ` bugzilla-daemon
2019-05-18 12:31 ` bugzilla-daemon
2019-05-18 12:33 ` bugzilla-daemon
2019-05-20 20:23 ` bugzilla-daemon
2019-05-20 21:12 ` bugzilla-daemon
2019-06-15 21:06 ` bugzilla-daemon
2019-07-22 20:30 ` bugzilla-daemon
2019-08-08 20:41 ` bugzilla-daemon [this message]
2019-08-08 20:48 ` bugzilla-daemon
2019-11-19  9:26 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-110671-502-8FZQzuJhHC@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox