dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/8] prepare for preparing for atomic (v2)
Date: Mon, 2 Jun 2014 10:11:28 +0200	[thread overview]
Message-ID: <20140602081128.GF19050@phenom.ffwll.local> (raw)
In-Reply-To: <1401469930-32750-1-git-send-email-robdclark@gmail.com>

On Fri, May 30, 2014 at 01:12:02PM -0400, Rob Clark wrote:
> As suggested by Daniel, splitting out ww_mutex conversion and a few
> other bits out.  Updated connection_mutex which fixes a few things,
> plus split up addition of extended property types from adding object
> property and pull in addition of _restore_fbdev_mode_unlocked() as
> it does not depend on atomic.

Just a quick note for merging: I prefer we don't pull this into 3.16, at
least not the locking changes. Due to the rushed merge window I didn't
have any chances yet to give the connection_mutex patch a real spin in
drm-intel-nightly, and none of the other drm driver maintainers have
chimed in about it yet either.
-Daniel

> 
> Can be found at:
> 
>   http://cgit.freedesktop.org/~robclark/linux/log/?h=atomic-prep
>   git://people.freedesktop.org/~robclark/linux atomic-prep
> 
> Daniel Vetter (1):
>   drm: Split connection_mutex out of mode_config.mutex (v3)
> 
> Rob Clark (7):
>   drm: helpers to find mode objects
>   drm: add extended property types
>   drm: add object property type
>   drm: add signed-range property type
>   drm: spiff out FB refcnting traces
>   drm: convert crtc and connection_mutex to ww_mutex (v3)
>   drm: add drm_fb_helper_restore_fbdev_mode_unlocked()
> 
>  drivers/gpu/drm/Makefile                   |   2 +-
>  drivers/gpu/drm/armada/armada_fbdev.c      |   4 +-
>  drivers/gpu/drm/drm_crtc.c                 | 295 +++++++++++++++++++----------
>  drivers/gpu/drm/drm_crtc_helper.c          |   1 +
>  drivers/gpu/drm/drm_edid.c                 |   2 +
>  drivers/gpu/drm/drm_fb_cma_helper.c        |   9 +-
>  drivers/gpu/drm/drm_fb_helper.c            |  55 ++++--
>  drivers/gpu/drm/drm_modeset_lock.c         | 179 +++++++++++++++++
>  drivers/gpu/drm/drm_plane_helper.c         |   7 +
>  drivers/gpu/drm/exynos/exynos_drm_fbdev.c  |   4 +-
>  drivers/gpu/drm/gma500/psb_drv.c           |   4 +-
>  drivers/gpu/drm/i915/i915_debugfs.c        |   4 +-
>  drivers/gpu/drm/i915/i915_drv.c            |   4 +-
>  drivers/gpu/drm/i915/intel_crt.c           |   5 +-
>  drivers/gpu/drm/i915/intel_display.c       |  60 ++++--
>  drivers/gpu/drm/i915/intel_dp.c            |  15 +-
>  drivers/gpu/drm/i915/intel_drv.h           |   6 +-
>  drivers/gpu/drm/i915/intel_fbdev.c         |   6 +-
>  drivers/gpu/drm/i915/intel_opregion.c      |   4 +-
>  drivers/gpu/drm/i915/intel_overlay.c       |   4 +-
>  drivers/gpu/drm/i915/intel_panel.c         |   8 +-
>  drivers/gpu/drm/i915/intel_sprite.c        |   2 +-
>  drivers/gpu/drm/i915/intel_tv.c            |   5 +-
>  drivers/gpu/drm/msm/msm_drv.c              |   7 +-
>  drivers/gpu/drm/omapdrm/omap_crtc.c        |  10 +-
>  drivers/gpu/drm/omapdrm/omap_drv.c         |   4 +-
>  drivers/gpu/drm/omapdrm/omap_fb.c          |   1 +
>  drivers/gpu/drm/radeon/radeon_connectors.c |   1 +
>  drivers/gpu/drm/tegra/fb.c                 |   7 +-
>  drivers/gpu/drm/vmwgfx/vmwgfx_kms.c        |   8 +-
>  include/drm/drmP.h                         |   5 -
>  include/drm/drm_crtc.h                     |  81 +++++++-
>  include/drm/drm_fb_helper.h                |   1 +
>  include/drm/drm_modeset_lock.h             | 103 ++++++++++
>  include/uapi/drm/drm_mode.h                |  15 ++
>  35 files changed, 716 insertions(+), 212 deletions(-)
>  create mode 100644 drivers/gpu/drm/drm_modeset_lock.c
>  create mode 100644 include/drm/drm_modeset_lock.h
> 
> -- 
> 1.9.3
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  parent reply	other threads:[~2014-06-02  8:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 17:12 [PATCH 0/8] prepare for preparing for atomic (v2) Rob Clark
2014-05-30 17:12 ` [PATCH 1/8] drm: helpers to find mode objects Rob Clark
2014-06-03 13:22   ` Daniel Vetter
2014-05-30 17:12 ` [PATCH 2/8] drm: add extended property types Rob Clark
2014-06-03 13:25   ` Daniel Vetter
2014-05-30 17:12 ` [PATCH 3/8] drm: add object property type Rob Clark
2014-06-03 13:24   ` Daniel Vetter
2014-05-30 17:12 ` [PATCH 4/8] drm: add signed-range " Rob Clark
2014-05-30 17:12 ` [PATCH 5/8] drm: spiff out FB refcnting traces Rob Clark
2014-05-30 17:12 ` [PATCH 6/8] drm: Split connection_mutex out of mode_config.mutex (v3) Rob Clark
2014-05-30 17:12 ` [PATCH 7/8] drm: convert crtc and connection_mutex to ww_mutex (v3) Rob Clark
2014-06-03 13:29   ` Daniel Vetter
2014-06-04  3:38     ` Dave Airlie
2014-06-04  9:21       ` Daniel Vetter
2014-05-30 17:12 ` [PATCH 8/8] drm: add drm_fb_helper_restore_fbdev_mode_unlocked() Rob Clark
2014-06-03 13:33   ` Daniel Vetter
2014-06-03 14:44     ` Rob Clark
2014-06-02  8:11 ` Daniel Vetter [this message]
2014-06-02 15:33   ` [PATCH 0/8] prepare for preparing for atomic (v2) Rob Clark

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=20140602081128.GF19050@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robdclark@gmail.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