Re: [PATCH] drm/i915: add port info to debugfs

2019-08-26 Thread Ser, Simon
On Mon, 2019-08-26 at 16:10 +0300, Jani Nikula wrote: > On Thu, 22 Aug 2019, Simon Ser wrote: > > This patch adds a line with the port name to connectors in > > debugfs/i915_debug_info. If the port is Type-C, the Type-C port > > number is > > printed too. > > > > Signed-off-by: Simon Ser > >

Re: [PATCH] drm: fix out-of-bounds access with short VSDB blocks

2019-07-22 Thread Ser, Simon
On Mon, 2019-07-22 at 14:38 +, Simon Ser wrote: > From: Simon Ser > > The VSDB parsing code contains a few len >= N checks, accessing db[N] on > success. However if len == N, db[N] is out-of-bounds. > > This commit changes the checks to test for len > N. > > Signed-off-by: Simon Ser

Re: Linking ALSA playback devices and DRM connectors

2019-06-06 Thread Ser, Simon
On Tue, 2019-06-04 at 17:24 +0200, Daniel Vetter wrote: > On Tue, Jun 4, 2019 at 5:15 PM Christian König > wrote: > > Am 04.06.19 um 17:05 schrieb Ser, Simon: > > > Hi, > > > > > > I'm trying to link ALSA playback devices and DRM connectors. In other &

Re: Linking ALSA playback devices and DRM connectors

2019-06-06 Thread Ser, Simon
On Tue, 2019-06-04 at 17:15 +0200, Christian König wrote: > Am 04.06.19 um 17:05 schrieb Ser, Simon: > > Hi, > > > > I'm trying to link ALSA playback devices and DRM connectors. In other > > words, I'd like to be able to know which ALSA device I should open to > >

Linking ALSA playback devices and DRM connectors

2019-06-04 Thread Ser, Simon
Hi, I'm trying to link ALSA playback devices and DRM connectors. In other words, I'd like to be able to know which ALSA device I should open to play audio on a given connector. Unfortunately, I haven't found a way to extract this information. I know /proc/asound/cardN/eld* expose the EDID-like

Re: [PATCH v7 09/11] drm: uevent for connector status change

2019-06-03 Thread Ser, Simon
On Mon, 2019-06-03 at 17:08 +0200, Daniel Vetter wrote: > On Mon, Jun 03, 2019 at 11:50:53AM +0200, Michel Dänzer wrote: > > On 2019-05-21 9:52 a.m., Daniel Vetter wrote: > > > On Tue, May 21, 2019 at 8:55 AM Pekka Paalanen > > > wrote: > > > > On Mon, 20 May 2019 18:11:07 +0200 > > > > Daniel

Re: [PATCH v7 09/11] drm: uevent for connector status change

2019-05-14 Thread Ser, Simon
On Tue, 2019-05-14 at 11:02 +0300, Pekka Paalanen wrote: > On Mon, 13 May 2019 11:34:58 +0200 > Daniel Vetter wrote: > > > On Mon, May 13, 2019 at 11:02 AM Paul Kocialkowski > > wrote: > > > Hi, > > > > > > On Fri, 2019-05-10 at 16:54 +0200, Daniel Vetter wrote: > > > > On Fri, May 10, 2019

Re: [PATCH v7 09/11] drm: uevent for connector status change

2019-05-14 Thread Ser, Simon
On Mon, 2019-05-13 at 17:04 +0200, Daniel Vetter wrote: > On Mon, May 13, 2019 at 10:11:01AM +0000, Ser, Simon wrote: > > On Mon, 2019-05-13 at 11:34 +0200, Daniel Vetter wrote: > > > On Mon, May 13, 2019 at 11:02 AM Paul Kocialkowski > > > wrote: > > > >

Re: [PATCH v7 09/11] drm: uevent for connector status change

2019-05-13 Thread Ser, Simon
On Mon, 2019-05-13 at 11:34 +0200, Daniel Vetter wrote: > On Mon, May 13, 2019 at 11:02 AM Paul Kocialkowski > wrote: > > Hi, > > > > On Fri, 2019-05-10 at 16:54 +0200, Daniel Vetter wrote: > > > On Fri, May 10, 2019 at 2:12 PM Paul Kocialkowski > > > wrote: > > > > Hi, > > > > > > > > On Tue,

Re: Improving DRM connector hotplug uevents

2019-05-10 Thread Ser, Simon
probe at all in case > > of a disconnect). > > > > It feels like there is growing temptation to have per-driver hacks to > > avoid full reprobes when the driver knows that nothing changed, but I > > think it makes more sense to fixup the uevent we send to make sure that