dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, etnaviv@lists.freedesktop.org,
	kernel@pengutronix.de
Subject: [GIT PULL] etnaviv-next for 6.6
Date: Wed, 16 Aug 2023 17:24:13 +0200	[thread overview]
Message-ID: <f40c65f7ecfde2e61f1a6d7fd463f6f739bc0dd1.camel@pengutronix.de> (raw)

Hi Dave, Daniel,

please pull the following etnaviv changes for the next merge window. 

This time mostly cleanups around the runtime power management handling
and slightly improved GPU hang handling. Also some additions to the
HWDB to get the driver working properly on more NXP i.MX8MP IP cores.

Sorry for being late, vacation got in the way, all changes have been
soaking in linux-next for more than 3 weeks.

Regards,
Lucas

The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:

  Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)

are available in the Git repository at:

  https://git.pengutronix.de/git/lst/linux etnaviv/next

for you to fetch changes up to 88c31d2dd191ab78e9ba9ff967845018aa7ee214:

  drm/etnaviv: fix error code in event_alloc() (2023-07-19 12:36:25 +0200)

----------------------------------------------------------------
Dan Carpenter (1):
      drm/etnaviv: fix error code in event_alloc()

Lucas Stach (12):
      drm/etnaviv: slow down FE idle polling
      drm/etnaviv: fix dumping of active MMU context
      drm/etnaviv: add HWDB entry for VIP8000 Nano r8002
      drm/etnaviv: add HWDB entry for GC520 r5341 c204
      drm/etnaviv: move down etnaviv_gpu_recover_hang() in file
      drm/etnaviv: free events the usual way in recover worker
      drm/etnaviv: move runtime PM handling to events
      drm/etnaviv: make clock handling symetric between runtime resume and suspend
      drm/etnaviv: avoid runtime PM usage in etnaviv_gpu_bind
      drm/etnaviv: better track GPU state
      drm/etnaviv: drop GPU initialized property
      drm/etnaviv: expedited MMU fault handling

Rob Herring (1):
      drm: etnaviv: Replace of_platform.h with explicit includes

 drivers/gpu/drm/etnaviv/etnaviv_buffer.c     |  11 +--
 drivers/gpu/drm/etnaviv/etnaviv_cmdbuf.c     |   3 +
 drivers/gpu/drm/etnaviv/etnaviv_drv.c        |   4 +-
 drivers/gpu/drm/etnaviv/etnaviv_dump.c       |  14 ++--
 drivers/gpu/drm/etnaviv/etnaviv_gem.h        |   1 -
 drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c |   3 -
 drivers/gpu/drm/etnaviv/etnaviv_gpu.c        | 188 ++++++++++++++++++++++++---------------------
 drivers/gpu/drm/etnaviv/etnaviv_gpu.h        |  13 +++-
 drivers/gpu/drm/etnaviv/etnaviv_hwdb.c       |  63 +++++++++++++++
 drivers/gpu/drm/etnaviv/etnaviv_mmu.c        |   3 +
 drivers/gpu/drm/etnaviv/etnaviv_sched.c      |   5 +-
 11 files changed, 201 insertions(+), 107 deletions(-)

                 reply	other threads:[~2023-08-16 15:24 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=f40c65f7ecfde2e61f1a6d7fd463f6f739bc0dd1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).