system_long_wq vs very long but mostly sleeping job

nikita.yoush

Hi

A driver needs to asynchronously execute a hardware calibration routine that periodically executes hardware communication and gathers statistics, total duration could be up to several 10s of seconds, but almost all of that time it sleeps.

Is such a routine a valid candidate to execute in scope of a work item inside system_long_wq?

Or system_long_wq is not intended for that long tasks and driver shall use a dedicated thread and/or split it into short-running work items?