From: Karol Wachowski <karol.wachowski@linux.intel.com>
To: Toast <swizzguy76@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
Oded Gabbay <ogabbay@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
dawid.osuchowski@linux.intel.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] accel/ivpu: Defer recovery until probe completes
Date: Sun, 15 Nov 2026 11:11:00 +0100 [thread overview]
Message-ID: <aeea0018-4242-4424-a29a-94fe77dc6e92@linux.intel.com> (raw)
In-Reply-To: <CAHBKUQYqAEuDHBDX-z6hvTY-GMOwqR9Skmtpn=UhaTK-JRx+1Q@mail.gmail.com>
On 13-Nov-26 9:49, Toast wrote:
> Tested on Meteor Lake (Core Ultra 5 125H, vpu_37xx firmware 20260219)
> on top of v7.4-rc1:
>
> - kexec from a 7.0 kernel and from 7.4 with the NPU runtime-suspended:
> both runs hit ATS_ERR during probe, recovery_work was not queued,
> probe failed once with -ETIMEDOUT, and there was no oops
> - FLR plus rebind brings the NPU back
> - debugfs force_recovery after a successful probe recovers the NPU
>
> I couldn't hit an error IRQ after ivpu_boot() succeeds, so the deferred
> recovery in ivpu_pm_enable() isn't covered by this.
>
> Tested-by: Daksh Sahni <swizzguy76@gmail.com>
Hi Daksh,
Thanks a lot for testing!
Just a heads-up: I already sent v3 a few days ago:
https://lore.kernel.org/all/20261110121534.3566028-1-karol.wachowski@linux.intel.com/
which includes a small adjustment in ivpu_pm_reset_complete() so
autosuspend isn't lost after a reset (reported by Sashiko).
Because of this change, I haven't carried over your Tested-by tag
automatically. If you happen to have a spare moment to give v3 a quick
spin, that would be great, otherwise no worries I've already have your
Reported-by tag.
Thanks,
Karol
prev parent reply other threads:[~2026-11-15 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261107174215.15818-1-swizzguy76@gmail.com>
2026-11-10 8:50 ` [PATCH v2] accel/ivpu: Defer recovery until probe completes Karol Wachowski
2026-11-13 8:49 ` Toast
2026-11-15 10:11 ` Karol Wachowski [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=aeea0018-4242-4424-a29a-94fe77dc6e92@linux.intel.com \
--to=karol.wachowski@linux.intel.com \
--cc=andrzej.kacprowski@linux.intel.com \
--cc=dawid.osuchowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=ogabbay@kernel.org \
--cc=stable@vger.kernel.org \
--cc=swizzguy76@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox