Re: [PATCH v3] drm/msm/dpu: drop validity checks for clear_pending_flush() ctl op

2024-06-23 Thread Dmitry Baryshkov
On Thu, 20 Jun 2024 13:17:30 -0700, Abhinav Kumar wrote: > clear_pending_flush() ctl op is always assigned irrespective of the DPU > hardware revision. Hence there is no needed to check whether the op has > been assigned before calling it. > > Drop the checks across the driver for

Re: [PATCH v3] drm/msm/dpu: drop validity checks for clear_pending_flush() ctl op

2024-06-22 Thread Dmitry Baryshkov
On Thu, Jun 20, 2024 at 01:17:30PM GMT, Abhinav Kumar wrote: > clear_pending_flush() ctl op is always assigned irrespective of the DPU > hardware revision. Hence there is no needed to check whether the op has > been assigned before calling it. > > Drop the checks across the driver for

Re: [PATCH v3] drm/msm/dpu: drop validity checks for clear_pending_flush() ctl op

2024-06-20 Thread Dmitry Baryshkov
On Thu, Jun 20, 2024 at 01:17:30PM GMT, Abhinav Kumar wrote: > clear_pending_flush() ctl op is always assigned irrespective of the DPU > hardware revision. Hence there is no needed to check whether the op has > been assigned before calling it. > > Drop the checks across the driver for

[PATCH v3] drm/msm/dpu: drop validity checks for clear_pending_flush() ctl op

2024-06-20 Thread Abhinav Kumar
clear_pending_flush() ctl op is always assigned irrespective of the DPU hardware revision. Hence there is no needed to check whether the op has been assigned before calling it. Drop the checks across the driver for clear_pending_flush() and also update its documentation that it is always expected