Re: [PATCH] drm/msm/dpu: Don't always set merge_3d pending flush

2024-10-15 Thread Dmitry Baryshkov
On Wed, Oct 09, 2024 at 08:41:13PM -0700, Jessica Zhang wrote: > Don't set the merge_3d pending flush bits if the mode_3d is > BLEND_3D_NONE. > > Always flushing merge_3d can cause timeout issues when there are > multiple commits with concurrent writeback enabled. > > This is because the video ph

Re: [PATCH] drm/msm/dpu: Don't always set merge_3d pending flush

2024-10-14 Thread Jessica Zhang
On 10/10/2024 8:20 AM, Dmitry Baryshkov wrote: On Wed, Oct 09, 2024 at 08:41:13PM GMT, Jessica Zhang wrote: Don't set the merge_3d pending flush bits if the mode_3d is BLEND_3D_NONE. Always flushing merge_3d can cause timeout issues when there are multiple commits with concurrent writeback e

Re: [PATCH] drm/msm/dpu: Don't always set merge_3d pending flush

2024-10-10 Thread Dmitry Baryshkov
On Wed, Oct 09, 2024 at 08:41:13PM GMT, Jessica Zhang wrote: > Don't set the merge_3d pending flush bits if the mode_3d is > BLEND_3D_NONE. > > Always flushing merge_3d can cause timeout issues when there are > multiple commits with concurrent writeback enabled. > > This is because the video phys

[PATCH] drm/msm/dpu: Don't always set merge_3d pending flush

2024-10-09 Thread Jessica Zhang
Don't set the merge_3d pending flush bits if the mode_3d is BLEND_3D_NONE. Always flushing merge_3d can cause timeout issues when there are multiple commits with concurrent writeback enabled. This is because the video phys enc waits for the hw_ctl flush register to be completely cleared [1] in it