Re: [PATCH] drm/amdgpu/display: drop the reduction loop when setting the sync groups

2020-05-29 Thread Kazlauskas, Nicholas
On 2020-05-29 2:04 p.m., Alex Deucher wrote: On Fri, May 29, 2020 at 9:56 AM Kazlauskas, Nicholas wrote: On 2020-05-28 10:06 a.m., Alex Deucher wrote: The logic for blanked is not the same as having a plane_state. Technically you can drive an OTG without anything connected in the front end

Re: [PATCH] drm/amdgpu/display: drop the reduction loop when setting the sync groups

2020-05-29 Thread Alex Deucher
On Fri, May 29, 2020 at 9:56 AM Kazlauskas, Nicholas wrote: > > On 2020-05-28 10:06 a.m., Alex Deucher wrote: > > The logic for blanked is not the same as having a plane_state. Technically > > you can drive an OTG without anything connected in the front end and it'll > > just draw out the back

Re: [PATCH] drm/amdgpu/display: drop the reduction loop when setting the sync groups

2020-05-29 Thread Kazlauskas, Nicholas
On 2020-05-28 10:06 a.m., Alex Deucher wrote: The logic for blanked is not the same as having a plane_state. Technically you can drive an OTG without anything connected in the front end and it'll just draw out the back color which is distinct from having the OTG be blanked. If we add planes or

[PATCH] drm/amdgpu/display: drop the reduction loop when setting the sync groups

2020-05-28 Thread Alex Deucher
The logic for blanked is not the same as having a plane_state. Technically you can drive an OTG without anything connected in the front end and it'll just draw out the back color which is distinct from having the OTG be blanked. If we add planes or unblank the OTG later then we'll still want the