dri-devel February 2020

dri-devel@lists.freedesktop.org

302 participants
679 discussions

BUG: unable to handle kernel paging request in drm_fb_helper_dirty_work
by syzbot 18 Jun '20

18 Jun '20

Hello, syzbot found the following crash on: HEAD commit: e42617b8 Linux 5.5-rc1 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=126dc282e00000 kernel config: https://syzkaller.appspot.com/x/.config?x=3754e2c78c1adb82 dashboard link: https://syzkaller.appspot.com/bug?extid=8a2039467425e497e64a compiler: gcc (GCC) 9.0.0 20181231 (experimental) userspace arch: i386 Unfortunately, I don't have any reproducer for this crash yet. IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+8a2039467425e497e64a(a)syzkaller.appspotmail.com BUG: unable to handle page fault for address: fffff520015a7200 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 7ffcd067 P4D 7ffcd067 PUD 2cd1c067 PMD 76d10067 PTE 0 Oops: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 18 Comm: kworker/1:0 Not tainted 5.5.0-rc1-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 Workqueue: events drm_fb_helper_dirty_work RIP: 0010:memory_is_nonzero mm/kasan/generic.c:121 [inline] RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:135 [inline] RIP: 0010:memory_is_poisoned mm/kasan/generic.c:166 [inline] RIP: 0010:check_memory_region_inline mm/kasan/generic.c:182 [inline] RIP: 0010:check_memory_region+0x9c/0x1a0 mm/kasan/generic.c:192 Code: c9 4d 0f 49 c1 49 c1 f8 03 45 85 c0 0f 84 10 01 00 00 41 83 e8 01 4e 8d 44 c0 08 eb 0d 48 83 c0 08 4c 39 c0 0f 84 a7 00 00 00 <48> 83 38 00 74 ed 4c 8d 40 08 eb 09 48 83 c0 01 49 39 c0 74 53 80 RSP: 0018:ffffc900004cfc30 EFLAGS: 00010216 RAX: fffff520015a7200 RBX: fffff520015a7400 RCX: ffffffff83f94dec RDX: 0000000000000001 RSI: 0000000000001000 RDI: ffffc9000ad39000 RBP: ffffc900004cfc48 R08: fffff520015a7400 R09: 0000000000000200 R10: fffff520015a73ff R11: ffffc9000ad39fff R12: fffff520015a7200 R13: ffffc9000ad39000 R14: ffffc9000a53a000 R15: ffffc9000a53a000 FS: 0000000000000000(0000) GS:ffff88802d100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffff520015a7200 CR3: 0000000052ea7000 CR4: 0000000000340ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600 Call Trace: memcpy+0x38/0x50 mm/kasan/common.c:126 memcpy include/linux/string.h:380 [inline] drm_fb_helper_dirty_blit_real drivers/gpu/drm/drm_fb_helper.c:399 [inline] drm_fb_helper_dirty_work+0x44c/0x780 drivers/gpu/drm/drm_fb_helper.c:428 process_one_work+0x9af/0x1740 kernel/workqueue.c:2264 worker_thread+0x98/0xe40 kernel/workqueue.c:2410 kthread+0x361/0x430 kernel/kthread.c:255 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352 Modules linked in: CR2: fffff520015a7200 ---[ end trace 1682650b38de1096 ]--- RIP: 0010:memory_is_nonzero mm/kasan/generic.c:121 [inline] RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:135 [inline] RIP: 0010:memory_is_poisoned mm/kasan/generic.c:166 [inline] RIP: 0010:check_memory_region_inline mm/kasan/generic.c:182 [inline] RIP: 0010:check_memory_region+0x9c/0x1a0 mm/kasan/generic.c:192 Code: c9 4d 0f 49 c1 49 c1 f8 03 45 85 c0 0f 84 10 01 00 00 41 83 e8 01 4e 8d 44 c0 08 eb 0d 48 83 c0 08 4c 39 c0 0f 84 a7 00 00 00 <48> 83 38 00 74 ed 4c 8d 40 08 eb 09 48 83 c0 01 49 39 c0 74 53 80 RSP: 0018:ffffc900004cfc30 EFLAGS: 00010216 RAX: fffff520015a7200 RBX: fffff520015a7400 RCX: ffffffff83f94dec RDX: 0000000000000001 RSI: 0000000000001000 RDI: ffffc9000ad39000 RBP: ffffc900004cfc48 R08: fffff520015a7400 R09: 0000000000000200 R10: fffff520015a73ff R11: ffffc9000ad39fff R12: fffff520015a7200 R13: ffffc9000ad39000 R14: ffffc9000a53a000 R15: ffffc9000a53a000 FS: 0000000000000000(0000) GS:ffff88802d100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffff520015a7200 CR3: 0000000052ea7000 CR4: 0000000000340ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600 --- This bug is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller(a)googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

1 1

[Bug 205497] New: Attempt to read amd gpu id causes a freeze
by bugzilla-daemon＠bugzilla.kernel.org 15 Jun '20

15 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=205497 Bug ID: 205497 Summary: Attempt to read amd gpu id causes a freeze Product: Drivers Version: 2.5 Kernel Version: 5.3.9 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: luya(a)fedoraproject.org Regression: No Created attachment 285871 --> https://bugzilla.kernel.org/attachment.cgi?id=285871&action=edit Script from radeontop to read AMD gpu ids Running an utility named radeontop on an AMD APU causes a freeze while attempting to read amdgpu ids. Attached is the script. It will be nice to provide a better method to read AMD GPU cards. -- You are receiving this mail because: You are watching the assignee of the bug.

1 24

[Bug 71891] New: 3.13 fails to boot with the radeon module
by bugzilla-daemon＠bugzilla.kernel.org 08 Jun '20

08 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=71891 Bug ID: 71891 Summary: 3.13 fails to boot with the radeon module Product: Drivers Version: 2.5 Kernel Version: 3.13.6-1-ARCH Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: sh.siddhartha(a)gmail.com Regression: No $ lspci -k | grep -A3 VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] Subsystem: Dell Device 0447 Kernel driver in use: fglrx_pci Kernel modules: radeon, fglrx Dell Inspiron N5010 (BIOS) Legacy catalyst works properly. Using the open source radeon driver either boots to tty login with above errors, or boots to a locked up black screen. drm syslog: [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver [drm] initializing kernel modesetting (RV730 0x1002:0x9480 0x1028:0x0447). [drm] register mmio base: 0xFBE20000 [drm] register mmio size: 65536 [drm] Detected VRAM RAM=1024M, BAR=256M [drm] RAM width 128bits DDR [drm] radeon: 1024M of VRAM memory ready [drm] radeon: 1024M of GTT memory ready. [drm] GART: num cpu pages 262144, num gpu pages 262144 [drm] Loading RV730 Microcode [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. [drm] radeon: irq initialized. [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!! [drm:rv770_startup] *ERROR* radeon: failed initializing UVD (-1). [drm] Enabling audio 0 support [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs [drm] radeon atom DIG backlight initialized [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA-1 [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] Connector 1: [drm] HDMI-A-1 [drm] HPD1 [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 2: [drm] LVDS-1 [drm] DDC: 0x7f68 0x7f68 0x7f6c 0x7f6c 0x7f70 0x7f70 0x7f74 0x7f74 [drm] Encoders: [drm] LCD1: INTERNAL_UNIPHY2 [drm] Internal thermal controller with fan control [drm] radeon: dpm initialized [drm] fb mappable at 0xC045E000 [drm] vram apper at 0xC0000000 [drm] size 4325376 [drm] fb depth is 24 [drm] pitch is 5632 fbcon: radeondrmfb (fb0) is primary device [drm:rv770_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [drm] Initialized radeon 2.36.0 20080528 for 0000:01:00.0 on minor 0 -- You are receiving this mail because: You are watching the assignee of the bug.

1 51

KMS documentation for userspace
by Simon Ser 03 Jun '20

03 Jun '20

Hi all, With Wayland compositors and DRM leases, the number of DRM userspace programs has increased (and will probably continue to increase). However it's been pretty hard to find good DRM docs for userspace. The resources currently available are: - The kernel docs, although only the high level overview is useful to userspace. - User-contributed tutorials, like [1] and [2]. - To help userspace understand hardware capabilities and limitations, I've recently started a DRM database dump project [3]. (Anything else I've missed?) We still lack docs that describe how to properly use the KMS API and the KMS properties. There is a deprecated list at [4], and another list mixed with kernel structs at [5]. This is not great for userspace developers. So I wanted to know if there's interest from the kernel community to maintain documentation for userspace? Or should userspace maintain its own docs of the kernel API? I don't know what would be the best place for these docs. If they live in kernel doc comments, then references to kernel functions and guidelines for kernel devs will appear (just like in the current docs). If they live outside of the kernel source code or outside of the kernel tree, they might get outdated. Thoughts? Thanks, [1]: https://github.com/ascent12/drm_doc [2]: https://gitlab.freedesktop.org/daniels/kms-quads [3]: https://drmdb.emersion.fr/ [4]: https://01.org/linuxgraphics/gfx-docs/drm/gpu/drm-kms.html#standard-connect… [5]: https://01.org/linuxgraphics/gfx-docs/drm/gpu/drm-kms.html#existing-kms-pro… -- Simon Ser https://emersion.fr

3 7

[PATCH resend 0/2] dts: keystone-k2g-evm: Display support
by Jyri Sarha 02 Jun '20

02 Jun '20

Resend because the earlier recipient list was wrong. Now that drm/tidss is queued for mainline, lets add display support for k2g-evm. There is no hurry since tidss is out only in v5.7, but it should not harm to have the dts changes in place before that. Jyri Sarha (2): ARM: dts: keystone-k2g: Add DSS node ARM: dts: keystone-k2g-evm: add HDMI video support arch/arm/boot/dts/keystone-k2g-evm.dts | 101 +++++++++++++++++++++++++ arch/arm/boot/dts/keystone-k2g.dtsi | 22 ++++++ 2 files changed, 123 insertions(+) -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

3 5

[Bug 205827] New: drm:drm_atomic_helper_wait_for_dependencies - drm_kms_helper - flip_done timed out
by bugzilla-daemon＠bugzilla.kernel.org 02 Jun '20

02 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=205827 Bug ID: 205827 Summary: drm:drm_atomic_helper_wait_for_dependencies - drm_kms_helper - flip_done timed out Product: Drivers Version: 2.5 Kernel Version: 5.3.13-vanilla Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: ionut_n2001(a)yahoo.com Regression: No Created attachment 286245 --> https://bugzilla.kernel.org/attachment.cgi?id=286245&action=edit inspect dmesg logs for drm error Hi, I compiled new kernel on my machine, this version 5.3.13. And wait 2-3 days for inspect error with dmesg and appear error with drm. [105790.812641] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out [105801.052698] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out [157144.794587] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out [157155.034746] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out [178642.290388] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out [178652.530562] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out [215497.863723] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out [215508.103790] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out [275188.513449] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out [275198.753543] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:34:plane-0] flip_done timed out I use VMware ESXi for hypervisor. -- You are receiving this mail because: You are watching the assignee of the bug.

1 3

[PATCH v1 0/4] make hdmi work on bananapi-r2
by Frank Wunderlich 21 May '20

21 May '20

This Patch-Series adds missing Patches/Bugfixes to get hdmi working on BPI-R2 first 2 Patches were already posted, but not yet merged into mainline i found no hint why - config component output by device node port https://patchwork.kernel.org/patch/10609007/ - add display subsystem related device nodes (resend) https://patchwork.kernel.org/patch/10588951/ Bibby Hsieh (1): drm/mediatek: config component output by device node port Ryder Lee (2): arm: dts: mt7623: add display subsystem related device nodes drm/mediatek: fix possible_crtcs chunhui dai (1): drm/mediatek: fix boot up for 720 and 480 but 1080 arch/arm/boot/dts/mt7623.dtsi | 177 ++++++++++++++++++ arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 85 +++++++++ arch/arm/boot/dts/mt7623n-rfb-emmc.dts | 85 +++++++++ drivers/gpu/drm/mediatek/mtk_dpi.c | 2 +- drivers/gpu/drm/mediatek/mtk_drm_drv.c | 41 +++- drivers/gpu/drm/mediatek/mtk_drm_drv.h | 4 +- drivers/gpu/drm/mediatek/mtk_hdmi_phy.c | 3 + drivers/gpu/drm/mediatek/mtk_hdmi_phy.h | 1 + .../gpu/drm/mediatek/mtk_mt2701_hdmi_phy.c | 1 + 9 files changed, 390 insertions(+), 9 deletions(-) -- 2.17.1

4 10

[PATCH 1/3] arm64: dts: mt8183: Add gce setting in display node
by Bibby Hsieh 21 May '20

21 May '20

In order to use GCE function, we need add some information into display node (mboxes, mediatek,gce-client-reg, mediatek,gce-events). Signed-off-by: Bibby Hsieh <bibby.hsieh(a)mediatek.com> Signed-off-by: Yongqiang Niu <yongqiang.niu(a)mediatek.com> --- arch/arm64/boot/dts/mediatek/mt8183.dtsi | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi index be4428c92f35..8b522b039a37 100644 --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi @@ -9,6 +9,7 @@ #include <dt-bindings/interrupt-controller/arm-gic.h> #include <dt-bindings/interrupt-controller/irq.h> #include <dt-bindings/power/mt8183-power.h> +#include <dt-bindings/gce/mt8183-gce.h> #include "mt8183-pinfunc.h" / { @@ -664,6 +665,9 @@ reg = <0 0x14000000 0 0x1000>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; #clock-cells = <1>; + mboxes = <&gce 0 CMDQ_THR_PRIO_HIGHEST>, + <&gce 1 CMDQ_THR_PRIO_HIGHEST>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0 0x1000>; }; ovl0: ovl@14008000 { @@ -672,6 +676,7 @@ interrupts = <GIC_SPI 225 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_OVL0>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0x8000 0x1000>; }; ovl_2l0: ovl@14009000 { @@ -680,6 +685,7 @@ interrupts = <GIC_SPI 226 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_OVL0_2L>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0x9000 0x1000>; }; ovl_2l1: ovl@1400a000 { @@ -688,6 +694,7 @@ interrupts = <GIC_SPI 227 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_OVL1_2L>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xa000 0x1000>; }; rdma0: rdma@1400b000 { @@ -697,6 +704,7 @@ power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_RDMA0>; mediatek,rdma_fifo_size = <5120>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xb000 0x1000>; }; rdma1: rdma@1400c000 { @@ -706,6 +714,7 @@ power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_RDMA1>; mediatek,rdma_fifo_size = <2048>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xc000 0x1000>; }; color0: color@1400e000 { @@ -715,6 +724,7 @@ interrupts = <GIC_SPI 231 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_COLOR0>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xe000 0x1000>; }; ccorr0: ccorr@1400f000 { @@ -723,6 +733,7 @@ interrupts = <GIC_SPI 232 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_CCORR0>; + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0xf000 0x1000>; }; aal0: aal@14010000 { @@ -732,6 +743,7 @@ interrupts = <GIC_SPI 233 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_AAL0>; + mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0 0x1000>; }; gamma0: gamma@14011000 { @@ -741,6 +753,7 @@ interrupts = <GIC_SPI 234 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_GAMMA0>; + mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x1000 0x1000>; }; dither0: dither@14012000 { @@ -749,6 +762,7 @@ interrupts = <GIC_SPI 235 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; clocks = <&mmsys CLK_MM_DISP_DITHER0>; + mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0x2000 0x1000>; }; mutex: mutex@14016000 { @@ -756,6 +770,8 @@ reg = <0 0x14016000 0 0x1000>; interrupts = <GIC_SPI 217 IRQ_TYPE_LEVEL_LOW>; power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>; + mediatek,gce-events = <CMDQ_EVENT_MUTEX_STREAM_DONE0>, + <CMDQ_EVENT_MUTEX_STREAM_DONE1>; }; smi_common: smi@14019000 { -- 2.18.0

3 8

[PATCH v5, 00/32] add drm support for MT8183
by yongqiang.niu＠mediatek.com 21 May '20

21 May '20

From: Yongqiang Niu <yongqiang.niu(a)mediatek.com> This series are based on 5.3-rc1 and provid 32 patch to support mediatek SOC MT8183 Change since v4 - fix reviewed issue in v4 Change since v3 - fix reviewed issue in v3 - fix type error in v3 - fix conflict with iommu patch Change since v2 - fix reviewed issue in v2 - add mutex node into dts file Changes since v1: - fix reviewed issue in v1 - add dts for mt8183 display nodes - adjust display clock control flow in patch 22 - add vmap support for mediatek drm in patch 23 - fix page offset issue for mmap function in patch 24 - enable allow_fb_modifiers for mediatek drm in patch 25 Yongqiang Niu (32): dt-bindings: mediatek: add binding for mt8183 display dt-bindings: mediatek: add ovl_2l description for mt8183 display dt-bindings: mediatek: add ccorr description for mt8183 display dt-bindings: mediatek: add dither description for mt8183 display dt-bindings: mediatek: add mutex description for mt8183 display arm64: dts: add display nodes for mt8183 drm/mediatek: add mutex mod into ddp private data drm/mediatek: add mutex mod register offset into ddp private data drm/mediatek: add mutex sof into ddp private data drm/mediatek: add mutex sof register offset into ddp private data drm/mediatek: split DISP_REG_CONFIG_DSI_SEL setting into another use case drm/mediatek: add mmsys private data for ddp path config drm/mediatek: move rdma sout from mtk_ddp_mout_en into mtk_ddp_sout_sel drm/mediatek: add ddp component CCORR drm/mediatek: add commponent OVL_2L0 drm/mediatek: add component OVL_2L1 drm/mediatek: add component DITHER drm/mediatek: add gmc_bits for ovl private data drm/medaitek: add layer_nr for ovl private data drm/mediatek: add function to background color input select for ovl/ovl_2l direct link drm/mediatek: add background color input select function for ovl/ovl_2l drm/mediatek: add ovl0/ovl_2l0 usecase drm/mediatek: distinguish ovl and ovl_2l by layer_nr drm/mediatek: add clock property check before get it drm/mediatek: add connection from OVL0 to OVL_2L0 drm/mediatek: add connection from RDMA0 to COLOR0 drm/mediatek: add connection from RDMA1 to DSI0 drm/mediatek: add connection from OVL_2L0 to RDMA0 drm/mediatek: add connection from OVL_2L1 to RDMA1 drm/mediatek: add connection from DITHER0 to DSI0 drm/mediatek: add connection from RDMA0 to DSI0 drm/mediatek: add support for mediatek SOC MT8183 .../bindings/display/mediatek/mediatek,disp.txt | 30 +- .../bindings/display/mediatek/mediatek,display.txt | 21 ++ arch/arm64/boot/dts/mediatek/mt8183.dtsi | 111 ++++++ drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 79 +++- drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 27 +- drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 42 ++- drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 410 ++++++++++++++++----- drivers/gpu/drm/mediatek/mtk_drm_ddp.h | 6 + drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 67 ++++ drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 21 ++ drivers/gpu/drm/mediatek/mtk_drm_drv.c | 50 +++ drivers/gpu/drm/mediatek/mtk_drm_drv.h | 3 + 12 files changed, 745 insertions(+), 122 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,display.txt -- 1.8.1.1.dirty

4 71

[PATCH] drm/debugfs: accept trailing whitespace in "force" attribute
by Michael Tretter 18 May '20

18 May '20

Using plain echo to set the "force" connector attribute fails with -EINVAL, because echo appends a newline to the output. Strip trailing whitespace in the input before checking the value to accept "off\n" or "off ". Signed-off-by: Michael Tretter <m.tretter(a)pengutronix.de> --- drivers/gpu/drm/drm_debugfs.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/drm_debugfs.c b/drivers/gpu/drm/drm_debugfs.c index c1807d5754b2..10dd89d3f28e 100644 --- a/drivers/gpu/drm/drm_debugfs.c +++ b/drivers/gpu/drm/drm_debugfs.c @@ -241,6 +241,7 @@ static ssize_t connector_write(struct file *file, const char __user *ubuf, struct seq_file *m = file->private_data; struct drm_connector *connector = m->private; char buf[12]; + int i; if (len > sizeof(buf) - 1) return -EINVAL; @@ -250,6 +251,10 @@ static ssize_t connector_write(struct file *file, const char __user *ubuf, buf[len] = '\0'; + /* strip trailing whitespace */ + for (i = len - 1; i > 0 && isspace(buf[i]); i--) + buf[i] = '\0'; + if (!strcmp(buf, "on")) connector->force = DRM_FORCE_ON; else if (!strcmp(buf, "digital")) -- 2.11.0

3 6

← Newer
1
...
6
7
8
9
10
11
12
...
68
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2020