From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: re-add locking around hw state readout
Date: Mon, 24 Feb 2014 13:27:26 +0200 [thread overview]
Message-ID: <20140224112726.GM3852@intel.com> (raw)
In-Reply-To: <1393017219-2121-1-git-send-email-jbarnes@virtuousgeek.org>
On Fri, Feb 21, 2014 at 01:13:39PM -0800, Jesse Barnes wrote:
> To silence locking complaints. This was a rebase failure on my part in
>
> commit fa9fa083d0606cb323f6105c17702460ea0a6780
> Author: Jesse Barnes <jbarnes@virtuousgeek.org>
> Date: Tue Feb 11 15:28:56 2014 -0800
>
> drm/i915: read out hw state earlier v2
>
> Reported-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 13ad064..69cade7 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -11282,7 +11282,9 @@ void intel_modeset_init(struct drm_device *dev)
> /* Just in case the BIOS is doing something questionable. */
> intel_disable_fbc(dev);
>
> + mutex_lock(&dev->mode_config.mutex);
> intel_modeset_setup_hw_state(dev, false);
> + mutex_unlock(&dev->mode_config.mutex);
>
> list_for_each_entry(crtc, &dev->mode_config.crtc_list,
> base.head) {
> --
> 1.7.9.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-02-24 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 21:13 [PATCH] drm/i915: re-add locking around hw state readout Jesse Barnes
2014-02-24 11:27 ` Ville Syrjälä [this message]
2014-03-04 18:16 ` 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=20140224112726.GM3852@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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.