dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
	karol.wachowski@linux.intel.com, lizhi.hou@amd.com,
	dawid.osuchowski@linux.intel.com,
	Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
Subject: [PATCH v2] accel/ivpu: Improve IVPU_TEST_MODE_FW_TEST handling
Date: Wed,  7 Oct 2026 18:13:23 +0200	[thread overview]
Message-ID: <20261007161323.2737682-1-andrzej.kacprowski@linux.intel.com> (raw)

In IVPU_TEST_MODE_FW_TEST mode the driver triggers a firmware boot but
does not wait for boot completion. Because it never waits for the boot
to finish, it cannot send a message and expect a response from the
firmware.

Exit ivpu_boot() early in this mode, bypassing ivpu_hw_sched_init() and
the rest of the post-boot initialization. ivpu_hw_sched_init() was
sending a message that timed out and failed the boot sequence.

Signed-off-by: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
---
 drivers/accel/ivpu/ivpu_drv.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/accel/ivpu/ivpu_drv.c b/drivers/accel/ivpu/ivpu_drv.c
index 8c1c87e69f91..538179dcd316 100644
--- a/drivers/accel/ivpu/ivpu_drv.c
+++ b/drivers/accel/ivpu/ivpu_drv.c
@@ -485,6 +485,9 @@ int ivpu_boot(struct ivpu_device *vdev)
 	ivpu_ipc_enable(vdev);
 
 	if (!ivpu_fw_is_warm_boot(vdev)) {
+		if (ivpu_test_mode & IVPU_TEST_MODE_FW_TEST)
+			return 0;
+
 		ret = ivpu_pm_dct_init(vdev);
 		if (ret)
 			goto err_disable_ipc;
-- 
2.43.0


             reply	other threads:[~2026-10-07 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 16:13 Andrzej Kacprowski [this message]
2026-10-07 16:30 ` [PATCH v2] accel/ivpu: Improve IVPU_TEST_MODE_FW_TEST handling sashiko-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=20261007161323.2737682-1-andrzej.kacprowski@linux.intel.com \
    --to=andrzej.kacprowski@linux.intel.com \
    --cc=dawid.osuchowski@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=karol.wachowski@linux.intel.com \
    --cc=lizhi.hou@amd.com \
    --cc=oded.gabbay@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