From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, airlied@redhat.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: [git pull] vmwgfx-next
Date: Wed, 5 Dec 2018 11:35:54 +0100 [thread overview]
Message-ID: <20181205103554.3675-1-thellstrom@vmware.com> (raw)
Hi Dave,
The vmwgfx -next changes for 4.21:
Page flip with damage by Deepak and others,
Various vmwgfx minor fixes anc cleanups.
The following changes since commit 818182dd1097fdc492aaef9b08755ea13274352d:
Merge tag 'imx-drm-next-2018-12-03' of git://git.pengutronix.de/git/pza/linux into drm-next (2018-12-05 15:00:14 +1000)
are available in the Git repository at:
git://people.freedesktop.org/~thomash/linux tags/vmwgfx-next-2018-12-05
for you to fetch changes up to 9a01135b98b9d5a7033c544245da7aad0d886758:
drm/vmwgfx: Use the standard atomic helpers for page-flip (2018-12-05 10:09:55 +0100)
----------------------------------------------------------------
Pull request of 2018-12-05
----------------------------------------------------------------
Colin Ian King (1):
drm/vmwgfx: remove redundant return ret statement
Deepak Rawat (16):
drm: Add a new helper to validate damage during atomic_check
drm: Add helper iterator functions for plane fb_damage_clips blob
drm/selftest: Add drm damage helper selftest
drm/vmwgfx: Add a new interface for plane update on a display unit
drm/vmwgfx: Implement STDU plane update for surface backed fb
drm/vmwgfx: Implement STDU plane update for BO backed fb
drm/vmwgfx: Use the new interface for STDU plane update
drm/vmwgfx: Update comments for stdu plane update
drm/vmwgfx: Enable FB_DAMAGE_CLIPS property for STDU primary plane
drm/vmwgfx: Implement SOU plane update for surface backed fb
drm/vmwgfx: Implement SOU plane update for BO backed fb
drm/vmwgfx: Use the new interface for SOU plane update
drm/vmwgfx: Update comments for sou plane update function
drm/vmwgfx: Enable FB_DAMAGE_CLIPS property for SOU primary plane
drm/vmwgfx: Use atomic helper function for dirty fb IOCTL
drm/vmwgfx: Don't clear mode::type anymore
Lukasz Spintzyk (1):
drm: Add a new plane property to send damage during plane update
Rob Clark (1):
drm: Add helper to implement legacy dirtyfb
Sinclair Yeh (1):
MAINTAINERS: Update vmwgfx maintainers
Thomas Hellstrom (3):
drm/vmwgfx: Fix up the implicit display unit handling
drm/vmwgfx: Fix a layout race condition
drm/vmwgfx: Use the standard atomic helpers for page-flip
YueHaibing (1):
drm/vmwgfx: Remove set but not used variable 'file_priv'
Documentation/gpu/drm-kms.rst | 12 +
MAINTAINERS | 2 -
drivers/gpu/drm/Makefile | 2 +-
drivers/gpu/drm/drm_atomic.c | 22 +
drivers/gpu/drm/drm_atomic_helper.c | 3 +
drivers/gpu/drm/drm_atomic_uapi.c | 13 +
drivers/gpu/drm/drm_damage_helper.c | 334 +++++++++
drivers/gpu/drm/drm_mode_config.c | 6 +
drivers/gpu/drm/selftests/Makefile | 3 +-
drivers/gpu/drm/selftests/drm_modeset_selftests.h | 21 +
drivers/gpu/drm/selftests/test-drm_damage_helper.c | 811 +++++++++++++++++++++
.../gpu/drm/selftests/test-drm_modeset_common.h | 21 +
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 1 -
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 11 -
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 2 -
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 3 -
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 569 +++++++--------
drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 150 +++-
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 11 +-
drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 359 +++++++--
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 561 ++++++++++----
include/drm/drm_damage_helper.h | 99 +++
include/drm/drm_mode_config.h | 9 +
include/drm/drm_plane.h | 42 ++
include/uapi/drm/drm_mode.h | 19 +
25 files changed, 2521 insertions(+), 565 deletions(-)
create mode 100644 drivers/gpu/drm/drm_damage_helper.c
create mode 100644 drivers/gpu/drm/selftests/test-drm_damage_helper.c
create mode 100644 include/drm/drm_damage_helper.h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-12-05 10:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 10:35 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-16 9:29 [git pull] vmwgfx-next Thomas Hellström (VMware)
2020-01-20 21:09 ` Dave Airlie
2020-01-20 21:42 ` Thomas Hellström (VMware)
2020-01-21 9:49 ` Thomas Hellström (VMware)
2019-11-14 13:17 Thomas Hellström (VMware)
2019-08-15 7:15 Thomas Hellström (VMware)
[not found] <20190814073152.3120-1-thomas@shipmail.org>
2019-08-14 17:35 ` Thomas Hellström (VMware)
2019-06-19 7:25 Thomas Hellström (VMware)
2018-09-28 13:11 Thomas Hellstrom
2017-08-28 20:22 [Git PULL] vmwgfx-next Sinclair Yeh
2017-08-28 20:35 ` Dave Airlie
2017-08-28 20:39 ` Sinclair Yeh
2017-04-21 17:18 [git pull] vmwgfx-next Sinclair Yeh
2017-03-31 23:32 Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter
2017-04-03 19:00 ` Sinclair Yeh
2017-01-30 19:46 Sinclair Yeh
2015-11-06 15:29 Thomas Hellstrom
2015-11-02 8:23 Thomas Hellstrom
2015-08-06 12:54 Thomas Hellstrom
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=20181205103554.3675-1-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@vmware.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