public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org, Dave Airlie <airlied@redhat.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Take modeset locks around intel_modeset_setup_hw_state()
Date: Mon, 02 Dec 2013 19:01:54 +0100	[thread overview]
Message-ID: <1386007314.9830.2.camel@x41.thuisdomein> (raw)
In-Reply-To: <20131202121219.GN10036@intel.com>

On Mon, 2013-12-02 at 14:12 +0200, Ville Syrjälä wrote:
> On Mon, Dec 02, 2013 at 11:00:29AM +0100, Paul Bolle wrote: 
> > I assume I need to test this, on top of 7c063c725987 ("drm/i915: take
> > mode config lock around crtc disable at suspend"), to see if this makes
> > the WARNING that I currently see at boot go away?
> 
> Yeah that would be nice.

A grand total of one boot suggests that this patch really makes the
v3.13+ WARNING go away at boot too. Should I test more thoroughly?


Paul Bolle

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

  reply	other threads:[~2013-12-02 18:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 20:38 [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector Paul Bolle
2013-12-01  9:58 ` Daniel Vetter
2013-12-01 16:57   ` Paul Bolle
2013-12-02  7:33     ` Daniel Vetter
2013-12-02  9:08       ` [PATCH] drm/i915: Take modeset locks around intel_modeset_setup_hw_state() ville.syrjala
2013-12-02 10:00         ` Paul Bolle
2013-12-02 12:12           ` Ville Syrjälä
2013-12-02 18:01             ` Paul Bolle [this message]
2013-12-02  9:53       ` [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector Paul Bolle
2013-12-02 14:23         ` Daniel Vetter
2013-12-02 18:05           ` Paul Bolle
2013-12-03 15:19             ` Daniel Vetter
2013-12-03 22:03               ` Paul Bolle
2013-12-03 22:13                 ` Daniel Vetter

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=1386007314.9830.2.camel@x41.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.com \
    /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