Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PULL] topic
Date: Fri, 25 Apr 2014 09:44:31 +0200	[thread overview]
Message-ID: <20140425074431.GA25677@phenom.ffwll.local> (raw)

Hi Dave,

Figured I might as well flush out my queue of random drm patches while I
throw drm-next pull requests at you ;-)

Mostly just polish for Matt Roper's primary planes work (nothing for
-fixes, that patch is already in Thierry's tree), plus two other things.
All nicely reviewed and also tested in drm-intel-nightly for a while by
now.

Cheers, Daniel


The following changes since commit a798c10faf62a505d24e5f6213fbaf904a39623f:

  Linux 3.15-rc2 (2014-04-20 11:08:50 -0700)

are available in the git repository at:

  git://anongit.freedesktop.org/drm-intel topic/core-stuff

for you to fetch changes up to 1e08bbeae1002fe6649667b89b614e89dd01a9e1:

  drm: Handle ->disable_plane failures correctly (2014-04-23 17:40:07 +0200)

----------------------------------------------------------------
Andrzej Hajda (1):
      drm: make mode_valid callback optional

Daniel Vetter (4):
      drm/plane_helper: don't disable plane in destroy function
      drm/crtc-helper: gc usless connector loop in disable_unused_functions
      drm: Simplify fb refcounting rules around ->update_plane
      drm: Handle ->disable_plane failures correctly

Matt Roper (1):
      drm/plane-helper: Fix primary plane scaling check

Vandana Kannan (1):
      drm/edid: Fill PAR in AVI infoframe based on CEA mode list

 Documentation/DocBook/drm.tmpl             |  6 +++---
 drivers/gpu/drm/ast/ast_mode.c             |  7 -------
 drivers/gpu/drm/bridge/ptn3460.c           |  7 -------
 drivers/gpu/drm/cirrus/cirrus_mode.c       |  8 --------
 drivers/gpu/drm/drm_crtc.c                 | 27 +++++++++++++++++----------
 drivers/gpu/drm/drm_crtc_helper.c          |  6 ------
 drivers/gpu/drm/drm_edid.c                 | 22 ++++++++++++++++++++++
 drivers/gpu/drm/drm_plane_helper.c         | 13 +++----------
 drivers/gpu/drm/drm_probe_helper.c         |  2 +-
 drivers/gpu/drm/exynos/exynos_dp_core.c    |  7 -------
 drivers/gpu/drm/exynos/exynos_drm_dpi.c    |  7 -------
 drivers/gpu/drm/exynos/exynos_drm_vidi.c   |  7 -------
 drivers/gpu/drm/rcar-du/rcar_du_lvdscon.c  |  7 -------
 drivers/gpu/drm/rcar-du/rcar_du_vgacon.c   |  7 -------
 drivers/gpu/drm/shmobile/shmob_drm_crtc.c  |  7 -------
 drivers/staging/imx-drm/imx-drm-core.c     |  7 -------
 drivers/staging/imx-drm/imx-drm.h          |  2 --
 drivers/staging/imx-drm/imx-hdmi.c         |  1 -
 drivers/staging/imx-drm/imx-ldb.c          |  1 -
 drivers/staging/imx-drm/imx-tve.c          |  4 ----
 drivers/staging/imx-drm/parallel-display.c |  1 -
 include/drm/drm_crtc.h                     |  1 +
 include/drm/drm_crtc_helper.h              |  2 +-
 23 files changed, 48 insertions(+), 111 deletions(-)

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

                 reply	other threads:[~2014-04-25  7:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140425074431.GA25677@phenom.ffwll.local \
    --to=daniel.vetter@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox