From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Dave Airlie <airlied@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
kernel@pengutronix.de, etnaviv@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [GIT PULL] etnaviv-next for 6.11
Date: Fri, 5 Jul 2024 11:35:55 +0200 [thread overview]
Message-ID: <Zoe-e6VZOAj_eRrp@phenom.ffwll.local> (raw)
In-Reply-To: <e8b91e2f18e6eaa722569dd21f559009064b1730.camel@pengutronix.de>
On Fri, Jun 28, 2024 at 12:39:33PM +0200, Lucas Stach wrote:
> Hi Dave, hi Sima,
>
> please pull the following changes for the next merge window. Mostly
> fixes, but as they concern new hardware support there's no need to rush
> them into the current -rc.
>
> Regards,
> Lucas
>
> The following changes since commit e67572cd2204894179d89bd7b984072f19313b03:
>
> Linux 6.9-rc6 (2024-04-28 13:47:24 -0700)
>
> are available in the Git repository at:
>
> https://git.pengutronix.de/git/lst/linux tags/drm-etnaviv-next-2024-06-28
>
> for you to fetch changes up to 704d3d60fec451f37706368d9d3e320322978986:
>
> drm/etnaviv: don't block scheduler when GPU is still active (2024-06-26 15:33:25 +0200)
Pulled, thanks.
-Sima
>
> ----------------------------------------------------------------
> - fix i.MX8MP NPU clock gating
> - workaround FE register cdc issues on some cores
> - fix DMA sync handling for cached buffers
> - fix job timeout handling
> - keep TS enabled on MMUv2 cores for improved performance
>
> ----------------------------------------------------------------
> Derek Foreman (1):
> drm/etnaviv: Read some FE registers twice
>
> Krzysztof Kozlowski (1):
> drm/etnaviv: drop driver owner assignment
>
> Lucas Stach (5):
> drm/etnaviv: don't disable TS on MMUv2 core when moving the linear window
> drm/etnaviv: switch devcoredump allocations to GFP_NOWAIT
> drm/etnaviv: fix DMA direction handling for cached RW buffers
> drm/etnaviv: reduce number of ktime_get calls in IRQ handler
> drm/etnaviv: don't block scheduler when GPU is still active
>
> Philipp Zabel (3):
> drm/etnaviv: Update hardware headers from rnndb
> drm/etnaviv: Turn etnaviv_is_model_rev() into a function
> drm/etnaviv: Disable SH_EU clock gating on VIPNano-Si+
>
> drivers/gpu/drm/etnaviv/cmdstream.xml.h | 52 +++++++++++++++++++++++--
> drivers/gpu/drm/etnaviv/common.xml.h | 12 +++---
> drivers/gpu/drm/etnaviv/etnaviv_dump.c | 5 +--
> drivers/gpu/drm/etnaviv/etnaviv_gem.c | 6 ++-
> drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 83 ++++++++++++++++++++++------------------
> drivers/gpu/drm/etnaviv/etnaviv_gpu.h | 8 ++++
> drivers/gpu/drm/etnaviv/etnaviv_sched.c | 9 ++---
> drivers/gpu/drm/etnaviv/state.xml.h | 103 ++++++++++++++++++++++++++++++++++++++++++--------
> drivers/gpu/drm/etnaviv/state_blt.xml.h | 22 +++++------
> drivers/gpu/drm/etnaviv/state_hi.xml.h | 30 +++++++++------
> 10 files changed, 238 insertions(+), 92 deletions(-)
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2024-07-05 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 10:39 [GIT PULL] etnaviv-next for 6.11 Lucas Stach
2024-07-05 9:35 ` Daniel Vetter [this message]
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=Zoe-e6VZOAj_eRrp@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox