From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Boris Brezillon" <boris.brezillon@collabora.com>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: dri-devel@lists.freedesktop.org, kernel@collabora.com
Subject: Re: [PATCH v3 0/5] drm/panthor: Be robust against failures in the resume path
Date: Wed, 11 Dec 2024 11:10:11 +0100 [thread overview]
Message-ID: <20241211111011.22a24c64@collabora.com> (raw)
In-Reply-To: <20241211075419.2333731-1-boris.brezillon@collabora.com>
On Wed, 11 Dec 2024 08:54:14 +0100
Boris Brezillon <boris.brezillon@collabora.com> wrote:
> Hello,
>
> Here's a collection of patches improving robustness to failures in
> the device resume/suspend path. Those failures are pretty hard to
> reproduce (happens once in a while on a deqp-vk run), so I used a
> mechanism to fake them.
>
> Faking a FW boot failure is kinda tricky though, which means the
> last patch has only been partially tested:
> - the fast reset path is well tested because that's the default on
> a device suspend
> - the slow reset has been tested with a hack replacing fast resets
> by slow resets
> - the fast -> slow reset fallback has been tested by faking boot
> failures after a fast reset, but these are not real, which means
> we can't really validate if the MCU recovers fine after a slow
> reset
>
> On the other hand, this implementation doesn't look like it could
> do more harm than the current one (the only difference is the
> extra GPU soft-reset that happens between the fast and slow FW
> boot).
>
> Nothing major changed in v3. Each patch contains a changelog, if
> you're interested.
>
> Regards,
>
> Boris
>
> Boris Brezillon (5):
> drm/panthor: Preserve the result returned by panthor_fw_resume()
> drm/panthor: Be robust against runtime PM resume failures in the
> suspend path
> drm/panthor: Ignore devfreq_{suspend,resume}_device() failures
> drm/panthor: Be robust against resume failures
> drm/panthor: Fix the fast-reset logic
Queued to drm-misc-next.
>
> drivers/gpu/drm/panthor/panthor_devfreq.c | 12 ++--
> drivers/gpu/drm/panthor/panthor_devfreq.h | 4 +-
> drivers/gpu/drm/panthor/panthor_device.c | 68 ++++++++++-------------
> drivers/gpu/drm/panthor/panthor_device.h | 37 ++++++++++++
> drivers/gpu/drm/panthor/panthor_drv.c | 2 +-
> drivers/gpu/drm/panthor/panthor_fw.c | 68 +++++++----------------
> drivers/gpu/drm/panthor/panthor_gpu.c | 14 +++--
> drivers/gpu/drm/panthor/panthor_mmu.c | 3 +-
> drivers/gpu/drm/panthor/panthor_sched.c | 4 +-
> 9 files changed, 107 insertions(+), 105 deletions(-)
>
prev parent reply other threads:[~2024-12-11 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 7:54 [PATCH v3 0/5] drm/panthor: Be robust against failures in the resume path Boris Brezillon
2024-12-11 7:54 ` [PATCH v3 1/5] drm/panthor: Preserve the result returned by panthor_fw_resume() Boris Brezillon
2024-12-11 9:50 ` Liviu Dudau
2024-12-11 7:54 ` [PATCH v3 2/5] drm/panthor: Be robust against runtime PM resume failures in the suspend path Boris Brezillon
2024-12-11 7:54 ` [PATCH v3 3/5] drm/panthor: Ignore devfreq_{suspend, resume}_device() failures Boris Brezillon
2024-12-11 7:54 ` [PATCH v3 4/5] drm/panthor: Be robust against resume failures Boris Brezillon
2024-12-11 7:54 ` [PATCH v3 5/5] drm/panthor: Fix the fast-reset logic Boris Brezillon
2024-12-11 9:57 ` Liviu Dudau
2024-12-11 10:09 ` Boris Brezillon
2024-12-11 10:10 ` Boris Brezillon [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=20241211111011.22a24c64@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=liviu.dudau@arm.com \
--cc=steven.price@arm.com \
/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.