Devicetree
 help / color / mirror / Atom feed
From: "Maíra Canal" <mcanal@igalia.com>
To: Melissa Wen <mwen@igalia.com>, Iago Toral <itoral@igalia.com>,
	 Jose Maria Casanova Crespo <jmcasanova@igalia.com>
Cc: dri-devel@lists.freedesktop.org, kernel-dev@igalia.com,
	stable@vger.kernel.org, "Maíra Canal" <mcanal@igalia.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
	devicetree@vger.kernel.org
Subject: [PATCH 0/6] drm/v3d: Fix GPU reset issues on the Raspberry Pi 5
Date: Wed, 26 Feb 2025 16:58:58 -0300	[thread overview]
Message-ID: <20250226-v3d-gpu-reset-fixes-v1-0-83a969fdd9c1@igalia.com> (raw)

This series addresses GPU reset issues reported in [1], where running a
long compute job would trigger repeated GPU resets, leading to a UI
freeze.

Patches #1 and #2 prevent the same faulty job from being resubmitted in a
loop, mitigating the first cause of the issue.

However, the issue isn't entirely solved. Even with only a single GPU
reset, the UI still freezes on the Raspberry Pi 5, indicating a GPU hang.
Patches #3 to #5 address this by properly configuring the V3D_SMS
registers, which are required for power management and resets in V3D 7.1.

Patch #6 updates the DT maintainership, replacing Emma with the current
v3d driver maintainer.

[1] https://github.com/raspberrypi/linux/issues/6660

Best Regards,
- Maíra

---
Maíra Canal (6):
      drm/v3d: Don't run jobs that have errors flagged in its fence
      drm/v3d: Set job pointer to NULL when the job's fence has an error
      drm/v3d: Associate a V3D tech revision to all supported devices
      dt-bindings: gpu: v3d: Add SMS to the registers' list
      drm/v3d: Use V3D_SMS registers for power on/off and reset on V3D 7.x
      dt-bindings: gpu: Add V3D driver maintainer as DT maintainer

 .../devicetree/bindings/gpu/brcm,bcm-v3d.yaml      |  8 +--
 drivers/gpu/drm/v3d/v3d_drv.c                      | 58 ++++++++++++++++++++--
 drivers/gpu/drm/v3d/v3d_drv.h                      | 18 +++++++
 drivers/gpu/drm/v3d/v3d_gem.c                      | 17 +++++++
 drivers/gpu/drm/v3d/v3d_regs.h                     | 26 ++++++++++
 drivers/gpu/drm/v3d/v3d_sched.c                    | 23 +++++++--
 6 files changed, 140 insertions(+), 10 deletions(-)
---
base-commit: 099b79f94366f3110783301e20d8136d762247f8
change-id: 20250224-v3d-gpu-reset-fixes-2d21fc70711d


             reply	other threads:[~2025-02-26 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 19:58 Maíra Canal [this message]
2025-02-26 19:59 ` [PATCH 4/6] dt-bindings: gpu: v3d: Add SMS to the registers' list Maíra Canal
2025-02-28 19:07   ` Conor Dooley
2025-02-26 19:59 ` [PATCH 6/6] dt-bindings: gpu: Add V3D driver maintainer as DT maintainer Maíra Canal
2025-03-03 14:05   ` Rob Herring (Arm)
2025-02-27  7:55 ` [PATCH 0/6] drm/v3d: Fix GPU reset issues on the Raspberry Pi 5 Iago Toral

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=20250226-v3d-gpu-reset-fixes-v1-0-83a969fdd9c1@igalia.com \
    --to=mcanal@igalia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=itoral@igalia.com \
    --cc=jmcasanova@igalia.com \
    --cc=kernel-dev@igalia.com \
    --cc=krzk+dt@kernel.org \
    --cc=mwen@igalia.com \
    --cc=nsaenz@kernel.org \
    --cc=stable@vger.kernel.org \
    /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