From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: [GIT PULL FOR v4.13] Renesas R-Car DU driver changes
Date: Sat, 10 Jun 2017 11:30:53 +0300 [thread overview]
Message-ID: <3610138.aMAhgRn3Pg@avalon> (raw)
Hi Dave,
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
git://linuxtv.org/pinchartl/media.git drm/next/du
for you to fetch changes up to fa5b4114202de0c1a7a64fd407af0b81ca529419:
drm: rcar-du: Map memory through the VSP device (2017-06-09 12:25:38 +0100)
The series interleaves DRM and V4L2 patches due to dependencies between the R-
Car DU and VSP drivers. Mauro has acked all the V4L2 patches to go through
your tree, and they don't conflict with anything queued for v4.13 in his tree.
If I need to send any conflicting patches through Mauro's tree for v4.13, I'll
make sure to base them on this branch.
----------------------------------------------------------------
Kieran Bingham (3):
v4l: vsp1: Postpone frame end handling in event of display list race
v4l: vsp1: Extend VSP1 module API to allow DRM callbacks
drm: rcar-du: Register a completion callback with VSP1
Laurent Pinchart (5):
drm: rcar-du: Arm the page flip event after queuing the page flip
v4l: rcar-fcp: Don't get/put module reference
v4l: rcar-fcp: Add an API to retrieve the FCP device
v4l: vsp1: Add API to map and unmap DRM buffers through the VSP
drm: rcar-du: Map memory through the VSP device
Magnus Damm (1):
v4l: vsp1: Map the DL and video buffers through the proper bus master
drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 30 ++++++++-------
drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 1 +
drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 83 ++++++++++++++++++++++++++++---
drivers/gpu/drm/rcar-du/rcar_du_vsp.h | 2 +
drivers/media/platform/rcar-fcp.c | 17 ++++----
drivers/media/platform/vsp1/vsp1.h | 1 +
drivers/media/platform/vsp1/vsp1_dl.c | 23 +++++++++--
drivers/media/platform/vsp1/vsp1_dl.h | 2 +-
drivers/media/platform/vsp1/vsp1_drm.c | 41 ++++++++++++++++++++
drivers/media/platform/vsp1/vsp1_drm.h | 11 ++++++
drivers/media/platform/vsp1/vsp1_drv.c | 9 +++++
drivers/media/platform/vsp1/vsp1_pipe.c | 13 ++++++-
drivers/media/platform/vsp1/vsp1_video.c | 2 +-
include/media/rcar-fcp.h | 5 +++
include/media/vsp1.h | 10 +++++
15 files changed, 215 insertions(+), 35 deletions(-)
--
Regards,
Laurent Pinchart
reply other threads:[~2017-06-10 8:30 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=3610138.aMAhgRn3Pg@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@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