[Bug 87049] [915] querying Randr enables LVDS output. Spurious TV detection?!

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jun 4 08:01:17 PDT 2015


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

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #9 from Chris Wilson <chris at chris-wilson.co.uk> ---
There is still the issue that S-Video fluctuates between unknown and
disconnected which causes the undesired behaviour, i.e. it would be fixed by:

diff --git a/drivers/gpu/drm/i915/intel_tv.c b/drivers/gpu/drm/i915/intel_tv.c
index 8b9d325bda3c..f15683a489fb 100644
--- a/drivers/gpu/drm/i915/intel_tv.c
+++ b/drivers/gpu/drm/i915/intel_tv.c
@@ -1337,12 +1337,12 @@ intel_tv_detect(struct drm_connector *connector, bool
force)
                                connector_status_disconnected :
                                connector_status_connected;
                } else
-                       status = connector_status_unknown;
+                       status = connector->status;

                drm_modeset_drop_locks(&ctx);
                drm_modeset_acquire_fini(&ctx);
        } else
-               return connector->status;
+               status = connector->status;

        if (status != connector_status_connected)
                return status;

There's just a small debate over what is the correct status value to return
when the output detection is forced but we are unable to do so. I think not
wilfully converting to unknown is beneficial.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150604/ce7eb4cd/attachment-0001.html>


More information about the intel-gfx-bugs mailing list