mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org, Dave Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel.vetter@intel.com>,
	Eric Anholt <eric@anholt.net>
Subject: [GIT PULL] drm-vc4-next-2016-12-09
Date: Fri,  9 Dec 2016 16:10:45 -0800	[thread overview]
Message-ID: <20161210001045.28309-1-eric@anholt.net> (raw)

I just got the ack on the DT bindings for VEC, so I'd like to get it
pulled if we can.  If it's too late for 4.10, I'm fine waiting.

Adding VEC support should have a low chance of regressions because it
doesn't get a mode configured by default.  This is due to it reporting
unknown connector state (the HW doesn't have hotplug detect).

I'd say the only dubious change here is the DRM_MODE_SUBCONNECTOR_xx
enum.  I would have left it for danvet to pull, but the TV connector
states patch ends up depending on it and he suggested I pull that one.


The following changes since commit c778cc5df944291dcdb1ca7a6bb781fbc22550c5:

  drm/vc4: Add fragment shader threading support (2016-11-16 13:25:26 -0800)

are available in the git repository at:

  https://github.com/anholt/linux tags/drm-vc4-next-2016-12-09

for you to fetch changes up to c167df443b4a8d97d25a8e69bd9f490a1e3fe646:

  drm/vc4: Don't use drm_put_dev (2016-12-09 15:28:42 -0800)

----------------------------------------------------------------
This pull request brings in VEC (TV-out) support for vc4, along with a
pageflipping race fix.

----------------------------------------------------------------
Boris Brezillon (5):
      drm/vc4: Fix ->clock_select setting for the VEC encoder
      drm: Turn DRM_MODE_SUBCONNECTOR_xx definitions into an enum
      drm: Add TV connector states to drm_connector_state
      drm/vc4: Add support for the VEC (Video Encoder) IP
      drm/vc4: Document VEC DT binding

Daniel Vetter (1):
      drm/vc4: Don't use drm_put_dev

Derek Foreman (1):
      drm/vc4: Fix race between page flip completion event and clean-up

 .../devicetree/bindings/display/brcm,bcm-vc4.txt   |  14 +
 drivers/gpu/drm/drm_atomic.c                       |  50 ++
 drivers/gpu/drm/vc4/Makefile                       |   1 +
 drivers/gpu/drm/vc4/vc4_crtc.c                     |  46 +-
 drivers/gpu/drm/vc4/vc4_debugfs.c                  |   1 +
 drivers/gpu/drm/vc4/vc4_drv.c                      |   5 +-
 drivers/gpu/drm/vc4/vc4_drv.h                      |   7 +
 drivers/gpu/drm/vc4/vc4_kms.c                      |  33 +-
 drivers/gpu/drm/vc4/vc4_regs.h                     |   3 +-
 drivers/gpu/drm/vc4/vc4_vec.c                      | 657 +++++++++++++++++++++
 include/drm/drm_connector.h                        |  32 +
 include/uapi/drm/drm_mode.h                        |  18 +-
 12 files changed, 834 insertions(+), 33 deletions(-)
 create mode 100644 drivers/gpu/drm/vc4/vc4_vec.c

                 reply	other threads:[~2016-12-10  0:10 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=20161210001045.28309-1-eric@anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®