[Bug 95207] [SKL] 5k tiled display issues (dual DP)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=95207

--- Comment #14 from Tomas Bzatek <bugs at bzatek.net> ---
Created attachment 123391
  --> https://bugs.freedesktop.org/attachment.cgi?id=123391&action=edit
dmesg with type1 timings parsed

So with the above three patches I'm actually able to see the native resolution
modes parsed. Attaching fresh dmesg, the interesting part is this one:

> [    0.969147] [drm:intel_dp_detect] [CONNECTOR:42:DP-1]
> [    0.983551] [drm:drm_parse_display_id] base revision v1.2, edid length 128, bytes 121, prod_id 0 ext_count 0
> [    0.983552] [drm:drm_parse_display_id] block id 0x12, rev 0, len 22
> [    0.983553] [drm:drm_parse_display_id] tile cap 0x82
> [    0.983553] [drm:drm_parse_display_id] tile_size 2560 x 2880
> [    0.983558] [drm:drm_parse_display_id] topo num tiles 2x1, location 1x0
> [    0.983567] [drm:drm_parse_display_id] vend DEL
> [    0.983568] [drm:drm_parse_display_id] block id 0x3, rev 0, len 60
> [    0.983594] [drm:drm_parse_display_id]    Modeline "3840x2160 at 60"  533240  3840 3887 3919 3999  2160 2162 2167 2221  +hsync -vsync
> [    0.983595] [drm:drm_parse_display_id]      pixel clock 533240 kHz, preferred = 1, interlaced = 0, aspect_ratio = 4, stereo_3d_support = 0
> [    0.983596] [drm:drm_parse_display_id]      hactive = 3840, hblank = 160, hsync_offset = 48, hsync_width = 32
> [    0.983597] [drm:drm_parse_display_id]      vactive = 2160, vblank = 62, vsync_offset = 3, vsync_width = 5
> [    0.983598] [drm:drm_parse_display_id]      hblank_start = 3839, width = 3840, hblank_end = 3999, hsync_start = 3887, hsync_end = htotal = 3919
> [    0.983608] [drm:drm_parse_display_id]      vblank_start = 2159, height = 2160, vblank_end = 2221, vsync_start = 2162, vsync_end = vtotal = 2167
> [    0.983609] [drm:drm_parse_display_id]    Modeline "2560x2880 at 30"  238240  2560 2607 2639 2719  2880 2882 2892 2920  +hsync -vsync
> [    0.983610] [drm:drm_parse_display_id]      pixel clock 238240 kHz, preferred = 0, interlaced = 0, aspect_ratio = 4, stereo_3d_support = 0
> [    0.983611] [drm:drm_parse_display_id]      hactive = 2560, hblank = 160, hsync_offset = 48, hsync_width = 32
> [    0.983611] [drm:drm_parse_display_id]      vactive = 2880, vblank = 41, vsync_offset = 3, vsync_width = 10
> [    0.983617] [drm:drm_parse_display_id]      hblank_start = 2559, width = 2560, hblank_end = 2719, hsync_start = 2607, hsync_end = htotal = 2639
> [    0.983618] [drm:drm_parse_display_id]      vblank_start = 2879, height = 2880, vblank_end = 2920, vsync_start = 2882, vsync_end = vtotal = 2892
> [    0.983619] [drm:drm_parse_display_id]    Modeline "2560x2880 at 60"  483240  2560 2607 2639 2719  2880 2882 2892 2961  +hsync -vsync
> [    0.983620] [drm:drm_parse_display_id]      pixel clock 483240 kHz, preferred = 0, interlaced = 0, aspect_ratio = 4, stereo_3d_support = 0
> [    0.983620] [drm:drm_parse_display_id]      hactive = 2560, hblank = 160, hsync_offset = 48, hsync_width = 32
> [    0.983625] [drm:drm_parse_display_id]      vactive = 2880, vblank = 82, vsync_offset = 3, vsync_width = 10
> [    0.983626] [drm:drm_parse_display_id]      hblank_start = 2559, width = 2560, hblank_end = 2719, hsync_start = 2607, hsync_end = htotal = 2639
> [    0.983627] [drm:drm_parse_display_id]      vblank_start = 2879, height = 2880, vblank_end = 2961, vsync_start = 2882, vsync_end = vtotal = 2892
> [    0.983628] [drm:drm_parse_display_id] block id 0x7, rev 0, len 10
> [    0.983628] [drm:drm_parse_display_id] found DisplayID tag 0x7, unhandled

The 0x07 block contains VESA timings, not expecting any special modes there.
FYI, the panel marks the "3840x2160 at 60" mode as preferred, we wouldn't get
native resolution out-of-the-box if the flag is honored.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160501/13948577/attachment-0001.html>