Lines Matching refs:DRM
2 I915 GuC Submission/DRM Scheduler Section
8 i915 with the DRM scheduler is:
14 * Lots of rework will need to be done to integrate with DRM scheduler so
32 * Convert the i915 to use the DRM scheduler
33 * GuC submission backend fully integrated with DRM scheduler
35 handled in DRM scheduler)
36 * Resets / cancels hook in DRM scheduler
37 * Watchdog hooks into DRM scheduler
39 integrated with DRM scheduler (e.g. state machine gets
41 * Execlists backend will minimum required to hook in the DRM scheduler
44 be difficult to integrate with the DRM scheduler and these
47 * ROI low on fully integrating into DRM scheduler
48 * Fully integrating would add lots of complexity to DRM
50 * Port i915 priority inheritance / boosting feature in DRM scheduler
51 * Used for i915 page flip, may be useful to other DRM drivers as
53 * Will be an optional feature in the DRM scheduler
54 * Remove in-order completion assumptions from DRM scheduler
55 * Even when using the DRM scheduler the backends will handle
58 * Pull out i915 priority levels and use DRM priority levels
59 * Optimize DRM scheduler as needed
80 band is reserved with the kernel. This aligns with the DRM scheduler priority