From: Karol Wachowski <karol.wachowski@linux.intel.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, lizhi.hou@amd.com,
dawid.osuchowski@linux.intel.com
Subject: Re: [PATCH v2] accel/ivpu: Remove sched_mode module parameter
Date: Wed, 18 Nov 2026 09:04:52 +0100 [thread overview]
Message-ID: <d87dbef5-e8b1-418c-87c8-e1ba55fb4b68@linux.intel.com> (raw)
In-Reply-To: <2f3d94d3-1f9d-4a88-b500-ce42ff85949d@oss.qualcomm.com>
On 17-Nov-26 21:52, Jeff Hugo wrote:
> On 11/17/2026 1:44 PM, Andrzej Kacprowski wrote:
>> OS scheduling supports only a limited subset of NPU functionality and
>> is not intended for production use. However, the sched_mode module
>> parameter exposes it as a regular configuration option, and the driver
>> silently falls back to it when the firmware JSM API is older than 3.24.
>>
>> Make hardware scheduling the only production mode:
>> - remove the sched_mode module parameter,
>> - require BOOT API 3.17 and JSM API 3.24 or newer, and fail probe with
>> a message requesting a firmware update otherwise,
>> - allow OS scheduling on pre-60XX devices only through the
>> IVPU_TEST_MODE_HWS_DISABLE test_mode bit, for debugging.
>>
>> The initial 37xx and 40xx firmware added to linux-firmware in March 2025
>> reports BOOT and JSM APIs 3.27, meeting both minimum requirements.
>>
>> Extend IVPU_FW_CHECK_API_COMPAT() to accept minimum major and minor
>> versions so both API requirements can be checked explicitly.
>>
>> Signed-off-by: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
> Reviewed-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
Thanks, applied to drm-misc-next.
prev parent reply other threads:[~2026-11-18 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 20:44 [PATCH v2] accel/ivpu: Remove sched_mode module parameter Andrzej Kacprowski
2026-11-17 20:52 ` Jeff Hugo
2026-11-18 8:04 ` 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=d87dbef5-e8b1-418c-87c8-e1ba55fb4b68@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=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 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.