From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH] drm/i915: Add lock on drm_helper_resume_force_mode Date: Fri, 23 Mar 2012 12:57:43 +0000 Message-ID: References: <1332507178-2830-1-git-send-email-seanpaul@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id 932229E821 for ; Fri, 23 Mar 2012 05:57:48 -0700 (PDT) In-Reply-To: <1332507178-2830-1-git-send-email-seanpaul@chromium.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Sean Paul , dri-devel@lists.freedesktop.org Cc: marcheu@chromium.org List-Id: dri-devel@lists.freedesktop.org On Fri, 23 Mar 2012 08:52:58 -0400, Sean Paul wrote: > i915_drm_thaw was not locking the mode_config lock when calling > drm_helper_resume_force_mode. When there were multiple wake sources, > this caused FDI training failure on SNB which in turn corrupted the > display. > > Signed-off-by: Sean Paul Reviewed-by: Chris Wilson Cc: stable@kernel.org -Chris -- Chris Wilson, Intel Open Source Technology Centre