From: Alexandru Dadu <alexandru.dadu@imgtec.com>
To: Frank Binns <frank.binns@imgtec.com>,
Matt Coster <matt.coster@imgtec.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: <linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
"Alessio Belle" <alessio.belle@imgtec.com>,
Brajesh Gupta <brajesh.gupta@imgtec.com>,
Alexandru Dadu <alexandru.dadu@imgtec.com>,
Sarah Walker <sarah.walker@imgtec.com>
Subject: [PATCH v2 0/3] drm/imagination: Firmware handling of context reset notification
Date: Thu, 12 Mar 2026 13:40:52 +0200 [thread overview]
Message-ID: <20260312-b4-firmware-context-reset-notification-handling-v2-0-aec5a64cb06f@imgtec.com> (raw)
- patch 1: Adds missing context reset reasons.
- patch 2: Fixes the reset_reason from enum to u32 in the fwif.
- patch 3: Adds the implementation of the context reset notification.
Signed-off-by: Alexandru Dadu <alexandru.dadu@imgtec.com>
---
Changes in v2:
- enum rogue_context_reset_reason update moved to a separate commit;
- pvr_context_reset_notification() renamed to pvr_dump_context_reset_notification();
- added handling for PVR_FWIF_DM_TDM;
- update include order in pvr_dump.c;
- fixed enum type ambiguilty in fwif headers for the reset_reason struct field;
- small QOL and nits fixed.
- Link to v1: https://lore.kernel.org/r/20260305-b4-firmware-context-reset-notification-handling-v1-1-46e2ce8d46ef@imgtec.com
---
Alexandru Dadu (3):
drm/imagination: Add missing rogue context reset reasons
drm/imagination: Switch reset_reason fields from enum to u32
drm/imagination: Implement handling of context reset notification
drivers/gpu/drm/imagination/Makefile | 1 +
drivers/gpu/drm/imagination/pvr_ccb.c | 5 +
drivers/gpu/drm/imagination/pvr_dump.c | 113 +++++++++++++++++++++
drivers/gpu/drm/imagination/pvr_dump.h | 17 ++++
drivers/gpu/drm/imagination/pvr_rogue_fwif.h | 8 +-
.../gpu/drm/imagination/pvr_rogue_fwif_shared.h | 18 +++-
6 files changed, 159 insertions(+), 3 deletions(-)
---
base-commit: d2e20c8951e4bb5f4a828aed39813599980353b6
change-id: 20260305-b4-firmware-context-reset-notification-handling-694a1b5e6b8c
Best regards,
--
Alexandru Dadu <alexandru.dadu@imgtec.com>
next reply other threads:[~2026-03-12 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 11:40 Alexandru Dadu [this message]
2026-03-12 11:40 ` [PATCH v2 1/3] drm/imagination: Add missing rogue context reset reasons Alexandru Dadu
2026-03-13 4:16 ` Claude review: " Claude Code Review Bot
2026-03-12 11:40 ` [PATCH v2 2/3] drm/imagination: Switch reset_reason fields from enum to u32 Alexandru Dadu
2026-03-13 4:16 ` Claude review: " Claude Code Review Bot
2026-03-12 11:40 ` [PATCH v2 3/3] drm/imagination: Implement handling of context reset notification Alexandru Dadu
2026-03-13 4:16 ` Claude review: " Claude Code Review Bot
2026-03-13 4:16 ` Claude review: drm/imagination: Firmware " Claude Code Review Bot
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=20260312-b4-firmware-context-reset-notification-handling-v2-0-aec5a64cb06f@imgtec.com \
--to=alexandru.dadu@imgtec.com \
--cc=airlied@gmail.com \
--cc=alessio.belle@imgtec.com \
--cc=brajesh.gupta@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.binns@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matt.coster@imgtec.com \
--cc=mripard@kernel.org \
--cc=sarah.walker@imgtec.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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