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 <[email protected]>
Reviewed-by: Jeff Hugo <[email protected]>

Thanks, applied to drm-misc-next.

Reply via email to