Re: [PATCH v2 3/3] drm/sched: Update timedout_job()'s documentation

2025-01-27 Thread Danilo Krummrich
On Mon, Jan 27, 2025 at 01:32:40PM +0100, Philipp Stanner wrote: > On Fri, 2025-01-24 at 13:27 +0100, Danilo Krummrich wrote: > > On Tue, Jan 21, 2025 at 04:15:46PM +0100, Philipp Stanner wrote: > > > drm_sched_backend_ops.timedout_job()'s documentation is outdated. > > > It > > > mentions the depr

Re: [PATCH v2 3/3] drm/sched: Update timedout_job()'s documentation

2025-01-27 Thread Philipp Stanner
On Fri, 2025-01-24 at 13:27 +0100, Danilo Krummrich wrote: > On Tue, Jan 21, 2025 at 04:15:46PM +0100, Philipp Stanner wrote: > > drm_sched_backend_ops.timedout_job()'s documentation is outdated. > > It > > mentions the deprecated function drm_sched_resubmit_job(). > > Furthermore, > > it does not

Re: [PATCH v2 3/3] drm/sched: Update timedout_job()'s documentation

2025-01-24 Thread Danilo Krummrich
On Tue, Jan 21, 2025 at 04:15:46PM +0100, Philipp Stanner wrote: > drm_sched_backend_ops.timedout_job()'s documentation is outdated. It > mentions the deprecated function drm_sched_resubmit_job(). Furthermore, > it does not point out the important distinction between hardware and > firmware schedul

[PATCH v2 3/3] drm/sched: Update timedout_job()'s documentation

2025-01-21 Thread Philipp Stanner
drm_sched_backend_ops.timedout_job()'s documentation is outdated. It mentions the deprecated function drm_sched_resubmit_job(). Furthermore, it does not point out the important distinction between hardware and firmware schedulers. Since firmware schedulers tyipically only use one entity per schedu