On Wed, Jan 8, 2025 at 7:14 PM Abhinav Kumar wrote:
>
>
>
> On 1/8/2025 7:04 PM, Rob Clark wrote:
> > On Wed, Jan 8, 2025 at 6:22 PM Abhinav Kumar
> > wrote:
> >>
> >>
> >>
> >> On 1/8/2025 6:14 PM, Dmitry Baryshkov wrote:
> >>> On Thu, 9 Jan 2025 at 03:45, Rob Clark wrote:
>
> On Wed
On 1/8/2025 7:04 PM, Rob Clark wrote:
On Wed, Jan 8, 2025 at 6:22 PM Abhinav Kumar wrote:
On 1/8/2025 6:14 PM, Dmitry Baryshkov wrote:
On Thu, 9 Jan 2025 at 03:45, Rob Clark wrote:
On Wed, Jan 8, 2025 at 2:58 PM Jessica Zhang wrote:
Force commit that are disabling a plane in the as
On Wed, Jan 8, 2025 at 6:22 PM Abhinav Kumar wrote:
>
>
>
> On 1/8/2025 6:14 PM, Dmitry Baryshkov wrote:
> > On Thu, 9 Jan 2025 at 03:45, Rob Clark wrote:
> >>
> >> On Wed, Jan 8, 2025 at 2:58 PM Jessica Zhang
> >> wrote:
> >>>
> >>> Force commit that are disabling a plane in the async_crtc to
On 1/8/2025 6:14 PM, Dmitry Baryshkov wrote:
On Thu, 9 Jan 2025 at 03:45, Rob Clark wrote:
On Wed, Jan 8, 2025 at 2:58 PM Jessica Zhang wrote:
Force commit that are disabling a plane in the async_crtc to take the
non-async commit tail path.
In cases where there are two consecutive async
On Thu, 9 Jan 2025 at 03:45, Rob Clark wrote:
>
> On Wed, Jan 8, 2025 at 2:58 PM Jessica Zhang
> wrote:
> >
> > Force commit that are disabling a plane in the async_crtc to take the
> > non-async commit tail path.
> >
> > In cases where there are two consecutive async cursor updates (one
> > reg
On Wed, Jan 8, 2025 at 2:58 PM Jessica Zhang wrote:
>
> Force commit that are disabling a plane in the async_crtc to take the
> non-async commit tail path.
>
> In cases where there are two consecutive async cursor updates (one
> regular non-NULL update followed by a disabling NULL FB update), it i
