Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-16 Thread Daniel Stone
Hi, On Fri, 16 Feb 2024 at 09:00, Tomi Valkeinen wrote: > On 13/02/2024 13:39, Daniel Stone wrote: > > Specifically, you probably want commits 4cde507be6a1 and 58dde0e0c000. > > I think the window of breakage was small enough that - assuming either > > those commits or an upgrade to Weston 12/13

Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-16 Thread Tomi Valkeinen
Hi, On 13/02/2024 13:39, Daniel Stone wrote: Hi, On Tue, 13 Feb 2024 at 10:18, Marius Vlad wrote: On Tue, Feb 13, 2024 at 11:57:59AM +0200, Tomi Valkeinen wrote: I haven't. I'm quite unfamiliar with Weston, and Randolph from TI (cc'd) has been working on the Weston side of things. I also

Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-15 Thread Aradhya Bhatia
Tomi, thank you for the fixes. On 13/02/24 13:46, Tomi Valkeinen wrote: > When the driver sets up the zpos property it sets the default zpos value > to the HW id of the plane. That is fine as such, but as on many DSS > versions the driver arranges the DRM planes in a different order than > the HW

Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-13 Thread Daniel Stone
Hi, On Tue, 13 Feb 2024 at 10:18, Marius Vlad wrote: > On Tue, Feb 13, 2024 at 11:57:59AM +0200, Tomi Valkeinen wrote: > > I haven't. I'm quite unfamiliar with Weston, and Randolph from TI (cc'd) has > > been working on the Weston side of things. I also don't know if there's > > something TI

Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-13 Thread Marius Vlad
On Tue, Feb 13, 2024 at 11:57:59AM +0200, Tomi Valkeinen wrote: > Hi, Hi, > > On 13/02/2024 11:04, Pekka Paalanen wrote: > > On Tue, 13 Feb 2024 10:16:36 +0200 > > Tomi Valkeinen wrote: > > > > > When the driver sets up the zpos property it sets the default zpos value > > > to the HW id of the

Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-13 Thread Tomi Valkeinen
Hi, On 13/02/2024 11:04, Pekka Paalanen wrote: On Tue, 13 Feb 2024 10:16:36 +0200 Tomi Valkeinen wrote: When the driver sets up the zpos property it sets the default zpos value to the HW id of the plane. That is fine as such, but as on many DSS versions the driver arranges the DRM planes in

Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-13 Thread Pekka Paalanen
On Tue, 13 Feb 2024 10:16:36 +0200 Tomi Valkeinen wrote: > When the driver sets up the zpos property it sets the default zpos value > to the HW id of the plane. That is fine as such, but as on many DSS > versions the driver arranges the DRM planes in a different order than > the HW planes (to

[PATCH 1/2] drm/tidss: Fix initial plane zpos values

2024-02-13 Thread Tomi Valkeinen
When the driver sets up the zpos property it sets the default zpos value to the HW id of the plane. That is fine as such, but as on many DSS versions the driver arranges the DRM planes in a different order than the HW planes (to keep the non-scalable planes first), this leads to odd initial zpos