From: Lucas Stach <l.stach@pengutronix.de>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: kernel@pengutronix.de, etnaviv@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: [GIT PULL] etnaviv-next for 5.17
Date: Thu, 23 Dec 2021 20:36:29 +0100 [thread overview]
Message-ID: <59619f8e9eb1d7ed7ea72cbead1f0aabc49f4e68.camel@pengutronix.de> (raw)
Hi Dave, hi Daniel,
please pull the following etnaviv changes for the next merge window:
- make etnaviv work on IOMMU enabled systems
- fix mapping of command buffers on systems with more than 4GB RAM
- close a DoS vector
- fix spurious GPU resets
Regards,
Lucas
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
https://git.pengutronix.de/git/lst/linux etnaviv/next
for you to fetch changes up to cdd156955f946beaa5f3a00d8ccf90e5a197becc:
drm/etnaviv: consider completed fence seqno in hang check (2021-12-23 20:21:33 +0100)
----------------------------------------------------------------
Lucas Stach (2):
drm/etnaviv: limit submit sizes
drm/etnaviv: consider completed fence seqno in hang check
Michael Walle (3):
drm/etnaviv: use PLATFORM_DEVID_NONE
drm/etnaviv: fix dma configuration of the virtual device
drm/etnaviv: use a 32 bit mask as coherent DMA mask
Rikard Falkeborn (1):
drm/etnaviv: constify static struct cooling_ops
drivers/gpu/drm/etnaviv/etnaviv_drv.c | 41 +++++++++++++++++++++++++++++++----------
drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c | 6 ++++++
drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 2 +-
drivers/gpu/drm/etnaviv/etnaviv_gpu.h | 1 +
drivers/gpu/drm/etnaviv/etnaviv_sched.c | 4 +++-
5 files changed, 42 insertions(+), 12 deletions(-)
reply other threads:[~2021-12-23 19:36 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=59619f8e9eb1d7ed7ea72cbead1f0aabc49f4e68.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.