Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-29 Thread Lisovskiy, Stanislav
On Thu, 2018-11-29 at 09:48 +0100, Daniel Vetter wrote: > I didn't check wayland (well, weston or any of the others, wayland > doesn't exist as an implementation), but -modesetting and -amdgpu. > And > they all have the same issue. It's roughly: > - You unplug > - Kernel sends out uevent > -

Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-29 Thread Daniel Vetter
On Thu, Nov 29, 2018 at 8:37 AM Lisovskiy, Stanislav wrote: > > On Wed, 2018-11-28 at 22:21 +0100, Daniel Vetter wrote: > > On Wed, Nov 28, 2018 at 09:51:13PM +0100, Daniel Vetter wrote: > > > On Wed, Nov 28, 2018 at 03:55:58PM +0200, Stanislav Lisovskiy > > > wrote: > > > > Currently kernel

Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-29 Thread Lisovskiy, Stanislav
On Thu, 2018-11-29 at 07:37 +, Lisovskiy, Stanislav wrote: > On Wed, 2018-11-28 at 22:21 +0100, Daniel Vetter wrote: > > > > > I tried to read the bug and I have no idea what's going on here. > > > Userspace > > > is supposed to shut off outputs that are disconnected, whether > > > that's DP,

Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-28 Thread Lisovskiy, Stanislav
On Wed, 2018-11-28 at 22:21 +0100, Daniel Vetter wrote: > On Wed, Nov 28, 2018 at 09:51:13PM +0100, Daniel Vetter wrote: > > On Wed, Nov 28, 2018 at 03:55:58PM +0200, Stanislav Lisovskiy > > wrote: > > > Currently kernel might allocate different connector ids > > > for the same outputs in case of

Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-28 Thread Daniel Vetter
On Wed, Nov 28, 2018 at 10:21:33PM +0100, Daniel Vetter wrote: > On Wed, Nov 28, 2018 at 09:51:13PM +0100, Daniel Vetter wrote: > > On Wed, Nov 28, 2018 at 03:55:58PM +0200, Stanislav Lisovskiy wrote: > > > Currently kernel might allocate different connector ids > > > for the same outputs in case

Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-28 Thread Daniel Vetter
On Wed, Nov 28, 2018 at 09:51:13PM +0100, Daniel Vetter wrote: > On Wed, Nov 28, 2018 at 03:55:58PM +0200, Stanislav Lisovskiy wrote: > > Currently kernel might allocate different connector ids > > for the same outputs in case of DP MST, which seems to > > confuse userspace. There are can be

Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-28 Thread Daniel Vetter
On Wed, Nov 28, 2018 at 03:55:58PM +0200, Stanislav Lisovskiy wrote: > Currently kernel might allocate different connector ids > for the same outputs in case of DP MST, which seems to > confuse userspace. There are can be different connector > ids in the list, which could be assigned to the same >

[Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl

2018-11-28 Thread Stanislav Lisovskiy
Currently kernel might allocate different connector ids for the same outputs in case of DP MST, which seems to confuse userspace. There are can be different connector ids in the list, which could be assigned to the same output, while being in different states. This results in issues, like external