All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39696] dual head: different vert refresh freq, applications sync to the wrong one
Date: Tue,  9 Aug 2011 08:56:35 -0700 (PDT)	[thread overview]
Message-ID: <20110809155635.C3321130168@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39696-502@http.bugs.freedesktop.org/>

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

--- Comment #6 from Alex Deucher <agd5f@yahoo.com> 2011-08-09 08:56:34 PDT ---
(In reply to comment #5)
> 
> Doesn't work the way we would like it:
> * All outputs can be connected to all CRTC's.
> * Default is LVDS:0, DP: 1
> * Even if the mode is exactly the same: As soon as I connect the DP to CRTC 0
> using xrandr, xrandr automatically reconnects LVDS to CRTC 1 (and if I
> reconnect the LVDS, DP is also switched). Hence, they can exchange CRTC's, but
> running both from the same CRTC seems to be impossible.
> 
> However, according to xrandr -- verbose they are not clones. 
> How do I set them to clone mode?

We disable cloning of certain encoders in the driver.  At the hardware level,
you can source multiple encoders to the same crtc, but there are too many
encoder specific limitations in most cases that make it hard to support cloning
from the same crtc.  DP and LVDS are not possible for example as they use
different clocking for the encoders.  LVDS is direct clocked from the PPLL
while DP uses fixed clock derived from the DCPLL, so you can't drive both off
the same crtc easily, at least not the way the driver is currently structured.

> 
> Currently both Xv and GL sync to LVDS by default,
> no matter which output is primary,
> and no matter which CRTC they use: 
> Even if DP is primary and CRTC 0, sync is on LVDS.

You might try assigning primary flag to the DP output.
xrandr --output DisplayPort-0 --primary

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-08-09 15:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 17:02 [Bug 39696] New: dual head: different vert refresh freq, applications sync to the wrong one bugzilla-daemon
2011-08-09 10:54 ` [Bug 39696] " bugzilla-daemon
2011-08-09 12:29 ` bugzilla-daemon
2011-08-09 12:47 ` bugzilla-daemon
2011-08-09 13:39 ` bugzilla-daemon
2011-08-09 14:28 ` bugzilla-daemon
2011-08-09 15:56 ` bugzilla-daemon [this message]
2011-08-09 16:07 ` bugzilla-daemon
2011-08-09 16:13 ` bugzilla-daemon
2011-08-09 17:20 ` bugzilla-daemon
2011-08-09 19:17 ` bugzilla-daemon
2011-08-10  9:50 ` bugzilla-daemon
2011-08-10 10:45 ` bugzilla-daemon
2011-08-10 13:45 ` bugzilla-daemon
2011-08-10 16:23 ` 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=20110809155635.C3321130168@annarchy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.