Re: [PATCH] drm: document how user-space should use link-status

2020-06-02 Thread Manasi Navare
On Tue, Jun 02, 2020 at 11:58:36AM +0200, Daniel Vetter wrote: > On Tue, Jun 02, 2020 at 10:38:46AM +0300, Pekka Paalanen wrote: > > On Mon, 01 Jun 2020 14:48:58 + > > Simon Ser wrote: > > > > > Describe what a "BAD" link-status means for user-space and how it should > > > handle it. The

Re: [PATCH] drm: document how user-space should use link-status

2020-06-02 Thread Simon Ser
On Tuesday, June 2, 2020 9:38 AM, Pekka Paalanen wrote: > Can it happen that there will be no modes left in > the list? Reading drm_helper_probe_single_connector_modes, this sounds unlikely but possible. This isn't specific to link-status though. This can be the case on a regular hotplug

Re: [PATCH] drm: document how user-space should use link-status

2020-06-02 Thread Daniel Vetter
On Tue, Jun 02, 2020 at 10:38:46AM +0300, Pekka Paalanen wrote: > On Mon, 01 Jun 2020 14:48:58 + > Simon Ser wrote: > > > Describe what a "BAD" link-status means for user-space and how it should > > handle it. The logic described has been implemented in igt [1]. > > > > [1]: > >

Re: [PATCH] drm: document how user-space should use link-status

2020-06-02 Thread Pekka Paalanen
On Mon, 01 Jun 2020 14:48:58 + Simon Ser wrote: > Describe what a "BAD" link-status means for user-space and how it should > handle it. The logic described has been implemented in igt [1]. > > [1]: >

[PATCH] drm: document how user-space should use link-status

2020-06-01 Thread Simon Ser
Describe what a "BAD" link-status means for user-space and how it should handle it. The logic described has been implemented in igt [1]. [1]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/fbe61f529737191d0920521946a575bd55f00fbe Signed-off-by: Simon Ser Cc: Daniel Vetter Cc: