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 67043] Atombios stuck in a look during resume
Date: Thu, 18 Jul 2013 21:32:43 +0000	[thread overview]
Message-ID: <bug-67043-502-S9UXfvUYfk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67043-502@http.bugs.freedesktop.org/>


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

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

--- Comment #7 from Parag <parag.warudkar@gmail.com> ---
After a not-so-clean git bisect (compilation failures in vgacon.c, some TI
driver I didn't need) this was the result - at least it is related to drm.

git bisect good
372835a8527f85b3eff20a18c2c339e827dfd4e4 is the first bad commit
commit 372835a8527f85b3eff20a18c2c339e827dfd4e4
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Sat Jun 15 00:13:13 2013 +0200

    drm/crtc-helper: explicit DPMS on after modeset

    Atm the crtc helper implementation of set_config has really
    inconsisten semantics: If just an fb update is good enough, dpms state
    will be left as-is, but if we do a full modeset we force everything to
    dpms on.

    This change has already been applied to the i915 modeset code in

    commit e3de42b68478a8c95dd27520e9adead2af9477a5
    Author: Imre Deak <imre.deak@intel.com>
    Date:   Fri May 3 19:44:07 2013 +0200

        drm/i915: force full modeset if the connector is in DPMS OFF mode

    which according to Greg KH seems to aim for a new record in most
    Bugzilla: links in a commit message.

    The history of this dpms forcing is pretty interesting. This patch
    here is an almost-revert of

    commit 811aaa55ba21ab37407018cfc01770d6b037d3fb
    Author: Keith Packard <keithp@keithp.com>
    Date:   Thu Feb 3 16:57:28 2011 -0800

        drm: Only set DPMS ON when actually configuring a mode

    which fixed the bug of trying to dpms on disabled outputs, but
    introduced the new discrepancy between an fb update only and full
    modesets. The actual introduction of this goes back to

    commit bf9dc102e284a5aa78c73fc9d72e11d5ccd8669f
    Author: Keith Packard <keithp@keithp.com>
    Date:   Fri Nov 26 10:45:58 2010 -0800

        drm: Set connector DPMS status to ON in drm_crtc_helper_set_config

    And if you'd dig around in the i915 driver code there's even more fun
    around forcing dpms on and losing our heads and temper of the
    resulting inconsistencies. Especially the DP re-training code had tons
    of funny stuff in it.

    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Signed-off-by: Dave Airlie <airlied@redhat.com>

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

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

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

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

  parent reply	other threads:[~2013-07-18 21:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 13:17 [Bug 67043] New: Atombios stuck in a look during resume bugzilla-daemon
2013-07-18 13:29 ` [Bug 67043] " bugzilla-daemon
2013-07-18 14:33 ` bugzilla-daemon
2013-07-18 15:00 ` bugzilla-daemon
2013-07-18 15:02 ` bugzilla-daemon
2013-07-18 15:20 ` bugzilla-daemon
2013-07-18 15:23 ` bugzilla-daemon
2013-07-18 21:32 ` bugzilla-daemon [this message]
2013-07-18 21:59 ` bugzilla-daemon
2013-07-19 17:02 ` bugzilla-daemon
2013-07-19 19:10 ` bugzilla-daemon
2013-07-20  0:51 ` [Bug 67043] Atombios stuck in a loop " bugzilla-daemon
2013-07-22 21:04 ` bugzilla-daemon
2013-08-03 13:17 ` bugzilla-daemon
2013-08-03 13:19 ` bugzilla-daemon
2013-08-03 13:46 ` bugzilla-daemon
2013-08-03 13:53 ` bugzilla-daemon
2013-08-03 13:55 ` 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-67043-502-S9UXfvUYfk@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