From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/i915: atomic_cdclk_freq fixes
Date: Wed, 23 Nov 2016 22:27:12 +0200 [thread overview]
Message-ID: <20161123202712.GP31595@intel.com> (raw)
In-Reply-To: <1479141311-11904-1-git-send-email-ville.syrjala@linux.intel.com>
On Mon, Nov 14, 2016 at 06:35:08PM +0200, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> My little fix for populating intel_state->cdclk with
> dev_priv->atomic_cdclk_freq became a little meatier after I realized
> that we really need to protect it with what is essentially a crtc
> rwlock. That is, writers need to hold all the crtc locks, whereas
> readers need to hold at least one.
>
> Ville Syrjälä (3):
> drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things
> drm/i915: Protect dev_priv->atomic_cdclk_freq with all the crtc locks
> drm/i915: Simplify error handling in intel_modeset_all_pipes()
Entire series pushed to dinq. Thanks for the reviews.
>
> drivers/gpu/drm/i915/i915_drv.h | 9 +++++-
> drivers/gpu/drm/i915/intel_display.c | 60 ++++++++++++++++++++++++++++--------
> 2 files changed, 55 insertions(+), 14 deletions(-)
>
> --
> 2.7.4
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-11-23 20:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 16:35 [PATCH 0/3] drm/i915: atomic_cdclk_freq fixes ville.syrjala
2016-11-14 16:35 ` [PATCH v2 1/3] drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things ville.syrjala
2016-11-14 16:35 ` ville.syrjala
2016-11-15 10:15 ` Maarten Lankhorst
2016-11-17 8:17 ` Paul Bolle
2016-11-17 14:55 ` Joseph Yasi
2016-11-14 16:35 ` [PATCH 2/3] drm/i915: Protect dev_priv->atomic_cdclk_freq with all the crtc locks ville.syrjala
2016-11-15 9:08 ` Daniel Vetter
2016-11-15 9:18 ` Daniel Vetter
2016-11-15 9:52 ` Ville Syrjälä
2016-11-15 10:14 ` Maarten Lankhorst
2016-11-15 13:41 ` Ville Syrjälä
2016-11-15 13:53 ` Maarten Lankhorst
2016-11-17 15:06 ` Ville Syrjälä
2016-11-18 10:26 ` Maarten Lankhorst
2016-11-18 12:27 ` Ville Syrjälä
2016-11-14 16:35 ` [PATCH 3/3] drm/i915: Simplify error handling in intel_modeset_all_pipes() ville.syrjala
2016-11-15 9:19 ` Daniel Vetter
2016-11-14 17:16 ` ✓ Fi.CI.BAT: success for drm/i915: atomic_cdclk_freq fixes Patchwork
2016-11-23 20:27 ` Ville Syrjälä [this message]
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=20161123202712.GP31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@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 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.