Lines Matching full:scheduling

38  * Number of Priority Bands for Hardware Scheduling
159  * For HWS command queue scheduling, we can prioritise command queues inside the
167  * For HWS priority scheduling, we can have multiple realtime priority bands.
213  * Job scheduling priority bands for both hardware scheduling and OS scheduling.
477 	 * aborted and removed from internal scheduling queues. All doorbells assigned
513 	/** Control command: Set context scheduling properties */
620 	/** Response to control command: Set context scheduling properties */
675  * This structure supports doorbell registration for only OS scheduling.
693  * Request structure to unregister a doorbell for both HW and OS scheduling.
892  * and HW scheduling.
905  * and HW scheduling.
948 	 * Default quantum in 100ns units for scheduling across processes
1024 /* HWS set context scheduling properties request / response */
1056  * This structure supports doorbell registration for both HW and OS scheduling.
1058  * OS scheduling and HW scheduling. For OS scheduling, cmdq_id will be ignored
1059  * and cmdq_base and cmdq_size will be used. For HW scheduling, cmdq_base and cmdq_size will be
1077  * @brief Structure to set another buffer to be used for scheduling-related logging.
1088  * scheduling log notification.
1121  * @brief The scheduling log notification is generated by VPU when it writes
1187  * After a HWS engine reset, all scheduling is stopped on VPU until a engine resume.
1188  * Host shall send this command to resume scheduling of any valid queue.