dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1
by bugzilla-daemon＠freedesktop.org 17 Sep '19

17 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93652 Bug ID: 93652 Summary: Random crashes/freezing with amdgpu Fury X mesa 11.1 Product: Mesa Version: 11.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: wittyman37(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120931 --> https://bugs.freedesktop.org/attachment.cgi?id=120931&action=edit dmesg output after crash on Dota 2 So I am using a Sapphire R9 Fury X with Antergos and the open source amdgpu driver. I am currently running the 4.4rc8 kernel and am getting random freezes or crashes about once per hour or so. Software versions: 4.4.0-rc8-g02006f7a OpenGL version string: 3.0 Mesa 11.1.0 GPU hardware: OpenGL renderer string: Gallium 0.4 on AMD FIJI (DRM 3.1.0, LLVM 3.7.0) 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Fiji XT [Radeon R9 FURY X] 1002:7300 CPU hardware: x86_64 AMD FX-8370 Eight-Core Processor Attached is the output of dmesg after a crash. -- You are receiving this mail because: You are the assignee for the bug.

2 21

[Bug 103743] Nier:Automata - "if" in fragment shader incorrectly evaluated, causes artifacts
by bugzilla-daemon＠freedesktop.org 17 Sep '19

17 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103743 Bug ID: 103743 Summary: Nier:Automata - "if" in fragment shader incorrectly evaluated, causes artifacts Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: philip.rebohle(a)tu-dortmund.de QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 135457 --> https://bugs.freedesktop.org/attachment.cgi?id=135457&action=edit Fragment shader with workaround When compiling Mesa against LLVM >= 5.0, Nier:Automata shows lighting artifacts that are caused by a misbehaving 'if' in a fragment shader. Apitrace that shows the issue (2.5G, bz2-compressed): https://mega.nz/#!JaBD0IoT!yBekRb7ZmvsSY60mo0E7N6uwaYfp_KfRDlnQWL0-QOo I attached a copy of the fragment shader that causes the problem, but also includes a workaround. The file name for MESA_SHADER_READ_PATH is FS_feba74122c9590d1522b92bbec52d662ecd99012.glsl. The offending code is located at line 135: R1.x = uintBitsToFloat(floatBitsToUint(R0).y >= 0x4u ? 0xffffffffu : 0u); if (bool(floatBitsToUint(R1).x)) The artifacts go away when changing the original 'if' condition to the following: if (floatBitsToUint(R0).y >= 0x4u) This happens with both Mesa 17.2 and latest Mesa-git when compiling against LLVM 5.0 or later. This does *not* happen with LLVM 4.0.1. My GPU is an RX 480. -- You are receiving this mail because: You are the assignee for the bug.

1 15

linux-next: manual merge of the drm tree with the drm-misc-fixes tree
by Mark Brown 17 Sep '19

17 Sep '19

Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/lima/lima_gem.c between commit: 21670bd78a25001cf8e ("drm/lima: fix lima_gem_wait() return value") from the drm-misc-fixes tree and commit: 52791eeec1d9f4a7e7f ("dma-buf: rename reservation_object to dma_resv") from the drm tree. I fixed it up (see below) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. diff --cc drivers/gpu/drm/lima/lima_gem.c index b609dc030d6ca,ff3d9acc24fcf..0000000000000 --- a/drivers/gpu/drm/lima/lima_gem.c +++ b/drivers/gpu/drm/lima/lima_gem.c @@@ -341,8 -341,8 +341,8 @@@ int lima_gem_wait(struct drm_file *file timeout = drm_timeout_abs_to_jiffies(timeout_ns); - ret = drm_gem_reservation_object_wait(file, handle, write, timeout); + ret = drm_gem_dma_resv_wait(file, handle, write, timeout); - if (ret == 0) + if (ret == -ETIME) ret = timeout ? -ETIMEDOUT : -EBUSY; return ret;

3 2

[PATCH] drm: Handle connector tile support only for modes that match tile size
by Manasi Navare 16 Sep '19

16 Sep '19

DRM Fb driver expects multiple CRTCs if it sees connector->has_tile is set, but we need to handle tile support and look for multiple CRTCs only for the modes that match the tile size. The other modes should be able to be displayed without tile support or uisng single CRTC. This patch adds the check to match the tile size with requested mode to handle the tile support. Cc: Ville Syrjälä <ville.syrjala(a)linux.intel.com> Cc: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com> Cc: Jani Nikula <jani.nikula(a)intel.com> Cc: Dave Airlie <airlied(a)redhat.com> Signed-off-by: Manasi Navare <manasi.d.navare(a)intel.com> --- drivers/gpu/drm/drm_fb_helper.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c index a7ba5b4902d6..ab11e86dd6d5 100644 --- a/drivers/gpu/drm/drm_fb_helper.c +++ b/drivers/gpu/drm/drm_fb_helper.c @@ -1613,7 +1613,9 @@ static int drm_fb_helper_single_fb_probe(struct drm_fb_helper *fb_helper, for (j = 0; j < mode_set->num_connectors; j++) { struct drm_connector *connector = mode_set->connectors[j]; - if (connector->has_tile) { + if (connector->has_tile && + desired_mode->hdisplay == connector->tile_h_size && + desired_mode->vdisplay == connector->tile_v_size) { lasth = (connector->tile_h_loc == (connector->num_h_tile - 1)); lastv = (connector->tile_v_loc == (connector->num_v_tile - 1)); /* cloning to multiple tiles is just crazy-talk, so: */ -- 2.19.1

1 0

[PATCH] drm/amd/display: Fix compile error due to 'endif' missing
by Austin Kim 16 Sep '19

16 Sep '19

gcc throws compile error with below message: HDRINST usr/include/drm/i915_drm.h drivers/gpu/drm/amd/amdgpu/../display/dc/dml/Makefile:70: *** missing 'endif'. Stop. scripts/Makefile.modbuiltin:55: recipe for target 'drivers/gpu/drm/amd/amdgpu' failed make[3]: *** [drivers/gpu/drm/amd/amdgpu] Error 2 make[3]: *** Waiting for unfinished jobs.... HDRINST usr/include/drm/omap_drm.h HDRINST usr/include/drm/tegra_drm.h HDRINST usr/include/drm/drm_sarea.h HDRINST usr/include/drm/panfrost_drm.h HDRINST usr/include/drm/drm.h scripts/Makefile.modbuiltin:55: recipe for target 'drivers/gpu/drm' failed make[2]: *** [drivers/gpu/drm] Error 2 scripts/Makefile.modbuiltin:55: recipe for target 'drivers/gpu' failed make[1]: *** [drivers/gpu] Error 2 make[1]: *** Waiting for unfinished jobs.... Add 'endif' to Makefile to stop compile error. Signed-off-by: Austin Kim <austindh.kim(a)gmail.com> --- drivers/gpu/drm/amd/display/dc/dml/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/amd/display/dc/dml/Makefile b/drivers/gpu/drm/amd/display/dc/dml/Makefile index a2eb59e..5b2a65b 100644 --- a/drivers/gpu/drm/amd/display/dc/dml/Makefile +++ b/drivers/gpu/drm/amd/display/dc/dml/Makefile @@ -44,6 +44,7 @@ CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_mode_vba_20.o := $(dml_ccflags) CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_rq_dlg_calc_20.o := $(dml_ccflags) CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_mode_vba_20v2.o := $(dml_ccflags) CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_rq_dlg_calc_20v2.o := $(dml_ccflags) +endif ifdef CONFIG_DRM_AMD_DC_DCN2_1 CFLAGS_$(AMDDALPATH)/dc/dml/dcn21/display_mode_vba_21.o := $(dml_ccflags) CFLAGS_$(AMDDALPATH)/dc/dml/dcn21/display_rq_dlg_calc_21.o := $(dml_ccflags) -- 2.6.2

3 3

Re: ✓ Fi.CI.IGT: success for series starting with [CI,1/2] drm/connector: Share with non-atomic drivers the function to get the single encoder
by Souza, Jose 16 Sep '19

16 Sep '19

Someone with drm-misc commit access could push this? Thanks On Sun, 2019-09-15 at 11:36 +0000, Patchwork wrote: > == Series Details == > > Series: series starting with [CI,1/2] drm/connector: Share with non- > atomic drivers the function to get the single encoder > URL : https://patchwork.freedesktop.org/series/66701/ > State : success > > == Summary == > > CI Bug Log - changes from CI_DRM_6894_full -> Patchwork_14412_full > ==================================================== > > Summary > ------- > > **SUCCESS** > > No regressions found. > > > > Known issues > ------------ > > Here are the changes found in Patchwork_14412_full that come from > known issues: > > ### IGT changes ### > > #### Issues hit #### > > * igt@gem_exec_schedule@preempt-contexts-bsd2: > - shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#109276]) +14 > similar issues > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb1/igt@gem_ex… > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb7/igt@ge… > > * igt@gem_exec_schedule@preemptive-hang-bsd: > - shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#111325]) +3 > similar issues > [3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb6/igt@gem_ex… > [4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb4/igt@ge… > > * igt@i915_pm_rpm@modeset-stress-extra-wait: > - shard-glk: [PASS][5] -> [DMESG-WARN][6] ([fdo#105763] > / [fdo#106538]) > [5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-glk7/igt@i915_pm… > [6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-glk8/igt@i91… > > * igt@i915_suspend@fence-restore-tiled2untiled: > - shard-apl: [PASS][7] -> [DMESG-WARN][8] ([fdo#108566]) > +3 similar issues > [7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-apl1/igt@i915_su… > [8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-apl7/igt@i91… > > * igt@kms_cursor_crc@pipe-b-cursor-alpha-transparent: > - shard-snb: [PASS][9] -> [SKIP][10] ([fdo#109271]) > [9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-snb5/igt@kms_cur… > [10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-snb7/igt@kms… > > * igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy: > - shard-hsw: [PASS][11] -> [FAIL][12] ([fdo#105767]) > [11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-hsw6/igt@kms_cur… > [12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-hsw1/igt@kms… > > * igt@kms_flip@2x-flip-vs-expired-vblank-interruptible: > - shard-glk: [PASS][13] -> [FAIL][14] ([fdo#105363]) > [13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-glk8/igt@kms_fli… > [14]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-glk2/igt@kms… > > * igt@kms_flip@basic-flip-vs-modeset: > - shard-apl: [PASS][15] -> [INCOMPLETE][16] > ([fdo#103927]) > [15]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-apl7/igt@kms_fli… > [16]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-apl3/igt@kms… > > * igt@kms_flip@flip-vs-expired-vblank-interruptible: > - shard-apl: [PASS][17] -> [FAIL][18] ([fdo#105363]) > [17]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-apl1/igt@kms_fli… > [18]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-apl3/igt@kms… > > * igt@kms > _frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite: > - shard-iclb: [PASS][19] -> [FAIL][20] ([fdo#103167]) +7 > similar issues > [19]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb8/igt@kms_fr… > [20]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb2/igt@km… > > * igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes: > - shard-skl: [PASS][21] -> [INCOMPLETE][22] > ([fdo#104108]) > [21]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-skl3/igt@kms_pla… > [22]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-skl4/igt@kms… > > * igt@kms_plane_lowres@pipe-a-tiling-x: > - shard-iclb: [PASS][23] -> [FAIL][24] ([fdo#103166]) +1 > similar issue > [23]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb1/igt@kms_pl… > [24]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb7/igt@km… > > * igt@kms_psr@psr2_cursor_render: > - shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441]) +3 > similar issues > [25]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb2/igt@kms_ps… > [26]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb6/igt@km… > > * igt@kms_rotation_crc@multiplane-rotation-cropping-bottom: > - shard-skl: [PASS][27] -> [DMESG-WARN][28] > ([fdo#106107]) > [27]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-skl9/igt@kms_rot… > [28]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-skl10/igt@km… > > * igt@perf@polling: > - shard-skl: [PASS][29] -> [FAIL][30] ([fdo#110728]) > [29]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-skl2/igt@perf@po… > [30]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-skl6/igt@per… > > > #### Possible fixes #### > > * igt@gem_eio@reset-stress: > - shard-iclb: [FAIL][31] ([fdo#109661]) -> [PASS][32] > [31]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb2/igt@gem_ei… > [32]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb6/igt@ge… > > * igt@gem_exec_schedule@preempt-queue-bsd1: > - shard-iclb: [SKIP][33] ([fdo#109276]) -> [PASS][34] +10 > similar issues > [33]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb6/igt@gem_ex… > [34]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb2/igt@ge… > > * igt@gem_exec_schedule@preempt-self-bsd: > - shard-iclb: [SKIP][35] ([fdo#111325]) -> [PASS][36] > [35]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb2/igt@gem_ex… > [36]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb6/igt@ge… > > * igt@kms_cursor_crc@pipe-c-cursor-128x42-offscreen: > - shard-hsw: [INCOMPLETE][37] ([fdo#103540]) -> > [PASS][38] > [37]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-hsw8/igt@kms_cur… > [38]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-hsw1/igt@kms… > > * igt@kms_flip@flip-vs-suspend-interruptible: > - shard-kbl: [DMESG-WARN][39] ([fdo#108566]) -> > [PASS][40] +1 similar issue > [39]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-kbl3/igt@kms_fli… > [40]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-kbl4/igt@kms… > > * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt: > - shard-iclb: [FAIL][41] ([fdo#103167]) -> [PASS][42] +2 > similar issues > [41]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb2/igt@kms_fr… > [42]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb6/igt@km… > > * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c: > - shard-apl: [DMESG-WARN][43] ([fdo#108566]) -> > [PASS][44] +3 similar issues > [43]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-apl7/igt@kms_pip… > [44]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-apl1/igt@kms… > > * igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min: > - shard-skl: [FAIL][45] ([fdo#108145]) -> [PASS][46] > [45]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-skl7/igt@kms_pla… > [46]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-skl4/igt@kms… > > * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: > - shard-skl: [FAIL][47] ([fdo#108145] / [fdo#110403]) -> > [PASS][48] > [47]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-skl5/igt@kms_pla… > [48]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-skl6/igt@kms… > > * igt@kms_psr@psr2_primary_mmap_gtt: > - shard-iclb: [SKIP][49] ([fdo#109441]) -> [PASS][50] +1 > similar issue > [49]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb8/igt@kms_ps… > [50]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb2/igt@km… > > * igt@kms_rotation_crc@cursor-rotation-180: > - shard-iclb: [INCOMPLETE][51] ([fdo#107713] / > [fdo#110026]) -> [PASS][52] > [51]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb7/igt@kms_ro… > [52]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb8/igt@km… > > * igt@perf@blocking: > - shard-skl: [FAIL][53] ([fdo#110728]) -> [PASS][54] > [53]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-skl1/igt@perf@bl… > [54]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-skl2/igt@per… > > > #### Warnings #### > > * igt@gem_ctx_isolation@vcs1-nonpriv: > - shard-iclb: [FAIL][55] ([fdo#111329]) -> [SKIP][56] > ([fdo#109276]) > [55]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb4/igt@gem_ct… > [56]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb8/igt@ge… > > * igt@gem_exec_schedule@preempt-queue-chain-bsd: > - shard-iclb: [SKIP][57] ([fdo#111325]) -> > [INCOMPLETE][58] ([fdo#107713]) > [57]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb4/igt@gem_ex… > [58]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb7/igt@ge… > > * igt@gem_mocs_settings@mocs-reset-bsd2: > - shard-iclb: [FAIL][59] ([fdo#111330]) -> [SKIP][60] > ([fdo#109276]) > [59]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6894/shard-iclb1/igt@gem_mo… > [60]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/shard-iclb7/igt@ge… > > > [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166 > [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 > [fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540 > [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927 > [fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108 > [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363 > [fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763 > [fdo#105767]: https://bugs.freedesktop.org/show_bug.cgi?id=105767 > [fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107 > [fdo#106538]: https://bugs.freedesktop.org/show_bug.cgi?id=106538 > [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 > [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 > [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 > [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 > [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276 > [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 > [fdo#109661]: https://bugs.freedesktop.org/show_bug.cgi?id=109661 > [fdo#110026]: https://bugs.freedesktop.org/show_bug.cgi?id=110026 > [fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403 > [fdo#110728]: https://bugs.freedesktop.org/show_bug.cgi?id=110728 > [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325 > [fdo#111329]: https://bugs.freedesktop.org/show_bug.cgi?id=111329 > [fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330 > > > Participating hosts (10 -> 10) > ------------------------------ > > No changes in participating hosts > > > Build changes > ------------- > > * CI: CI-20190529 -> None > * Linux: CI_DRM_6894 -> Patchwork_14412 > > CI-20190529: 20190529 > CI_DRM_6894: a323fd657c577491b1660662624bac36bb964222 @ > git://anongit.freedesktop.org/gfx-ci/linux > IGT_5182: f7104497049e3761ac297b66fd5586849b3cfcc8 @ > git://anongit.freedesktop.org/xorg/app/intel-gpu-tools > Patchwork_14412: 71a0b54618371628a5f271b5c2432bcb20deabc8 @ > git://anongit.freedesktop.org/gfx-ci/linux > piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ > git://anongit.freedesktop.org/piglit > > == Logs == > > For more details see: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14412/

2 3

linux-next: manual merge of the drm tree with the kbuild tree
by Mark Brown 16 Sep '19

16 Sep '19

Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/amd/display/dc/dml/Makefile between commit: 54b8ae66ae1a345 ("kbuild: change *FLAGS_<basetarget>.o to take the path relative to $(obj)") from the kbuild tree and commits: 0f0727d971f6fdf ("drm/amd/display: readd -msse2 to prevent Clang from emitting libcalls to undefined SW FP routines") 542816ff168d8a3 ("drm/amd/display: Add DCN2.1 changes to DML") b04641a3f4c54b0 ("drm/amd/display: Add Renoir DML") 057fc695e934a77 ("drm/amd/display: support "dummy pstate"") from the drm tree. I fixed it up (see below) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. diff --cc drivers/gpu/drm/amd/display/dc/dml/Makefile index 83792e2c0f0e4,af2a864a6da05..0000000000000 --- a/drivers/gpu/drm/amd/display/dc/dml/Makefile +++ b/drivers/gpu/drm/amd/display/dc/dml/Makefile @@@ -32,16 -32,29 +32,25 @@@ endi dml_ccflags := -mhard-float -msse $(cc_stack_align) + ifdef CONFIG_CC_IS_CLANG + dml_ccflags += -msse2 + endif + -CFLAGS_display_mode_lib.o := $(dml_ccflags) +CFLAGS_$(AMDDALPATH)/dc/dml/display_mode_lib.o := $(dml_ccflags) ifdef CONFIG_DRM_AMD_DC_DCN2_0 -CFLAGS_display_mode_vba.o := $(dml_ccflags) -CFLAGS_display_mode_vba_20.o := $(dml_ccflags) -CFLAGS_display_rq_dlg_calc_20.o := $(dml_ccflags) -CFLAGS_display_mode_vba_20v2.o := $(dml_ccflags) -CFLAGS_display_rq_dlg_calc_20v2.o := $(dml_ccflags) -endif +CFLAGS_$(AMDDALPATH)/dc/dml/display_mode_vba.o := $(dml_ccflags) +CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_mode_vba_20.o := $(dml_ccflags) +CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_rq_dlg_calc_20.o := $(dml_ccflags) ++CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_mode_vba_20v2.o := $(dml_ccflags) ++CFLAGS_$(AMDDALPATH)/dc/dml/dcn20/display_rq_dlg_calc_20v2.o := $(dml_ccflags) + ifdef CONFIG_DRM_AMD_DC_DCN2_1 -CFLAGS_display_mode_vba_21.o := $(dml_ccflags) -CFLAGS_display_rq_dlg_calc_21.o := $(dml_ccflags) -endif -ifdef CONFIG_DRM_AMD_DCN3AG -CFLAGS_display_mode_vba_3ag.o := $(dml_ccflags) ++CFLAGS_$(AMDDALPATH)/dc/dml/dcn21/display_mode_vba_21.o := $(dml_ccflags) ++CFLAGS_$(AMDDALPATH)/dc/dml/dcn21/display_rq_dlg_calc_21.o := $(dml_ccflags) endif -CFLAGS_dml1_display_rq_dlg_calc.o := $(dml_ccflags) -CFLAGS_display_rq_dlg_helpers.o := $(dml_ccflags) -CFLAGS_dml_common_defs.o := $(dml_ccflags) +CFLAGS_$(AMDDALPATH)/dc/dml/dml1_display_rq_dlg_calc.o := $(dml_ccflags) +CFLAGS_$(AMDDALPATH)/dc/dml/display_rq_dlg_helpers.o := $(dml_ccflags) +CFLAGS_$(AMDDALPATH)/dc/dml/dml_common_defs.o := $(dml_ccflags) DML = display_mode_lib.o display_rq_dlg_helpers.o dml1_display_rq_dlg_calc.o \ dml_common_defs.o

2 2

[PATCH] drm/tegra: switch to using devm_gpiod_get_optional
by Dmitry Torokhov 16 Sep '19

16 Sep '19

We do not really need to use API that fetches GPIO data from an arbitrary device tree node, as we are dealing with device tree node assigned to the device structure. We can easily switch to devm_gpiod_get_optional() plus gpiod_set_consumer_name() and clean up the code. Note this is part of efforts to get rid of [devm_]gpiod_get_from_of_node in drivers so that gpiolib can be cleaned up. Signed-off-by: Dmitry Torokhov <dmitry.torokhov(a)gmail.com> --- drivers/gpu/drm/tegra/output.c | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/drivers/gpu/drm/tegra/output.c b/drivers/gpu/drm/tegra/output.c index bdcaa4c7168c..b4248125b844 100644 --- a/drivers/gpu/drm/tegra/output.c +++ b/drivers/gpu/drm/tegra/output.c @@ -121,19 +121,15 @@ int tegra_output_probe(struct tegra_output *output) of_node_put(ddc); } - output->hpd_gpio = devm_gpiod_get_from_of_node(output->dev, - output->of_node, - "nvidia,hpd-gpio", 0, - GPIOD_IN, - "HDMI hotplug detect"); - if (IS_ERR(output->hpd_gpio)) { - if (PTR_ERR(output->hpd_gpio) != -ENOENT) - return PTR_ERR(output->hpd_gpio); - - output->hpd_gpio = NULL; - } + output->hpd_gpio = devm_gpiod_get_optional(output->dev, + "nvidia,hpd", GPIOD_IN); + if (IS_ERR(output->hpd_gpio)) + return PTR_ERR(output->hpd_gpio); if (output->hpd_gpio) { + gpiod_set_consumer_name(output->hpd_gpio, + "HDMI hotplug detect"); + err = gpiod_to_irq(output->hpd_gpio); if (err < 0) { dev_err(output->dev, "gpiod_to_irq(): %d\n", err); -- 2.23.0.237.gc6a4ce50a0-goog -- Dmitry

2 2

[PATCH v5 0/8] add driver for boe, tv101wum-nl6, boe, tv101wum-n53, auo, kd101n80-45na and auo, b101uan08.3 panels
by Jitao Shi 16 Sep '19

16 Sep '19

Changes since v4: - add auo,b101uan08.3 panel for this driver. - add boe,tv101wum-n53 panel for this driver. Changes since v3: - remove check enable_gpio. - fine tune the auo,kd101n80-45na panel's power on timing. Changes since v2: - correct the panel size - remove blank line in Kconfig - move auo,kd101n80-45na panel driver in this series. Changes since v1: - update typo nl6 -> n16. - update new panel config and makefile are added in alphabetically order. - add the panel mode and panel info in driver data. - merge auo,kd101n80-45a and boe,tv101wum-nl6 in one driver Jitao Shi (8): dt-bindings: display: panel: Add BOE tv101wum-n16 panel bindings drm/panel: support for BOE tv101wum-nl6 wuxga dsi video mode panel dt-bindings: display: panel: add auo kd101n80-45na panel bindings drm/panel: support for auo,kd101n80-45na wuxga dsi video mode panel dt-bindings: display: panel: add boe tv101wum-n53 panel documentation drm/panel: support for boe,tv101wum-n53 wuxga dsi video mode panel dt-bindings: display: panel: add AUO auo,b101uan08.3 panel documentation drm/panel: support for auo,b101uan08.3 wuxga dsi video mode panel .../display/panel/auo,b101uan08.3.txt | 34 + .../display/panel/auo,kd101n80-45na.txt | 34 + .../display/panel/boe,tv101wum-n53.txt | 34 + .../display/panel/boe,tv101wum-nl6.txt | 34 + drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile | 1 + .../gpu/drm/panel/panel-boe-tv101wum-nl6.c | 876 ++++++++++++++++++ 7 files changed, 1022 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/auo,b101uan08.3.txt create mode 100644 Documentation/devicetree/bindings/display/panel/auo,kd101n80-45na.txt create mode 100644 Documentation/devicetree/bindings/display/panel/boe,tv101wum-n53.txt create mode 100644 Documentation/devicetree/bindings/display/panel/boe,tv101wum-nl6.txt create mode 100644 drivers/gpu/drm/panel/panel-boe-tv101wum-nl6.c -- 2.21.0

2 9

[PATCH 0/4] drm/nouveau: Miscellaneous fixes
by Thierry Reding 16 Sep '19

16 Sep '19

From: Thierry Reding <treding(a)nvidia.com> Hi Ben, these are fixes for a couple of issues that I've been running into when testing on various Tegra boards. The first two patches fix up issues in the fix that I had sent out earlier to fix the regression introduced in drm-misc-next. The first one is critical because it avoids a BUG_ON as reported by Ilia, while the second is less critical, but restores the locking correctness (at least to the best of my knowledge). Patch 3 is something that I think was also caused by the reservation object rework and is kind of a continuation of my earlier attempt to fix the VMA node sharing breakage. The current ordering between TTM and GEM teardown is causing a DEBUG_LOCKS_WARN_ON() because GEM cleanup already freed a mutex that TTM teardown will still want to use. Lastly, patch 4 is quite uncritical, but it's a one-line change that is causing an ugly (but harmless) external memory address decode error on Tegra210 and later. It seems that for some reason clearing this register will cause a DMA operation to be started by the GPU. I've verified that it's tied to exactly that register write by modifying the value written to the register, and stalling for a couple of seconds after the register write. The address decode error reflects the value written into this register exactly and it always happens a couple of milliseconds after this write. Thierry Thierry Reding (4): drm/nouveau: Fix fallout from reservation object rework drm/nouveau: prime: Extend DMA reservation object lock drm/nouveau: Fix ordering between TTM and GEM release drm/nouveau: gm20b: Avoid BAR1 teardown during init drivers/gpu/drm/nouveau/nouveau_bo.c | 26 +++++++++++------- drivers/gpu/drm/nouveau/nouveau_bo.h | 4 +-- drivers/gpu/drm/nouveau/nouveau_gem.c | 7 ++--- drivers/gpu/drm/nouveau/nouveau_prime.c | 27 ++++++++++++------- .../gpu/drm/nouveau/nvkm/subdev/bar/gm20b.c | 1 - 5 files changed, 39 insertions(+), 26 deletions(-) -- 2.23.0

1 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019