dri-devel April 2022

dri-devel@lists.freedesktop.org

351 participants
951 discussions

[PATCH v20 0/8] Add Mediatek Soc DRM (vdosys0) support for mt8195
by jason-jh.lin 25 May '22

25 May '22

From: jason-jhlin <jason-jh.lin(a)mediatek.corp-partner.google.com> Change in v20: - split binding patch to another series 'MediaTek MT8195 display binding': https://patchwork.ozlabs.org/project/devicetree-bindings/list/?series=295669 - fix io_start type from u32 to resource_size_t - fix some commit message for DITHER enum Change in v19: - fix checking condition for the return vaule of platform resource - drm/mediatek fix build waning for [-Wunused-const-variable] Change in v18: - change get driver data by io_start and wrap mmsys driver data into mmsys match data structure to support identifying multi mmsys driver data with the same compatible name - change DDP_COMPONENT_DITHER to DDP_CONPONENT_DITHER0 Change in v17: - change compatible name from 2 vdosys to 1 mmsys - add get driver data by clk name function to get corresponding driver data for mt8195 vdosys0 - add all routing table setting for mt8195 vdosys0 - remove useless mutex define Change in v16: - rebase on linu-next tag: 'next-20220303' - rebase on series: 'Fix MediaTek display dt-bindings issues' Change in v15: - remove mt8195-mmsys.h comment for mux settings - define the mask macro to replace using value as mask to fix zero mask problem - add EOF setting comment for MUTEX sof register Change in v14: - rebase on mediatek-drm-next-5.17 - rebase on "Add mmsys and mutex support for MDP" series - rebase on "media: mediatek: support mdp3 on mt8183 platform" series Change in v13: - remove dts patch - rebase on kernel-5.16-rc1 - rebase on mediatek-drm-next Change in v12: - add clock-names property to merge yaml - using BIT(nr) macro to define the settings of mmsys routing table - fix clk_get and clk_prepare_enable error handling issue Change in v11: - rebase on kernel-5.15-rc1 - change mbox label to gce0 for dts node of vdosys0 - change ovl compatibale to mt8192 to set smi_id_en=true in driver data - move common module from display folder to common folder, such as AAL, COCLOR, CCORR and MUTEX Change in v10: - rebase on "drm/mediatek: add support for mediatek SOC MT8192" series - rebase on "soc: mediatek: mmsys: add mt8192 mmsys support" series - fix some typo and "mediatek" start with capital in every dt-bindings - move mutex yaml from dfisplay folder to soc folder - separate merge additional propoerties to an individual dt-bindings patch Change in v9: - separate power and gce properties of mmsys into another dt-binding patch - rebase on "Separate aal module" series - keep mtk_ddp_clk_enable/disable in the same place - change mtk_dsc_start config register to mtk_drm_ddp_write_mask - remove the 0 setting of merge fifo config function - add CCORR driver data for mt8195 Change in v8: - add DP_INTF0 mux into mmsys routing table - add DP_INTF0 mutex mod and enum into add/remove comp function - remove bypass DSC enum in mtk_ddp_comp_init Change in v7: - add dt=binding of mmsys and disp path into this series - separate th modidfication of alphabetic order, remove unused define and rename the define of register offset to individual patch - add comment for MERGE ultra and preultra setting Change in v6: - adjust alphabetic order for mediatek-drm - move the patch that add mt8195 support for mediatek-drm as the lastest patch - add MERGE define for const varriable Change in v5: - add power-domain property into vdosys0 and vdosys1 dts node. - add MT8195 prifix and remove unused VDO1 define in mt8195-mmsys.h Change in v4: - extract dt-binding patches to another patch series - squash DSC module into mtk_drm_ddp_comp.c - add coment and simplify MERGE config function Change in v3: - change mmsys and display dt-bindings document from txt to yaml - add MERGE additional description in display dt-bindings document - fix mboxes-cells number of vdosys0 node in dts - drop mutex eof convert define - remove pm_runtime apis in DSC and MERGE - change DSC and MERGE enum to alphabetic order Change in v2: - add DSC yaml file - add mt8195 drm driver porting parts in to one patch - remove useless define, variable, structure member and function - simplify DSC and MERGE file and switch threre order jason-jh.lin (8): soc: mediatek: add mtk-mmsys support for mt8195 vdosys0 soc: mediatek: add mtk-mutex support for mt8195 vdosys0 drm/mediatek: add DSC support for mediatek-drm drm/mediatek: add MERGE support for mediatek-drm drm/mediatek: add mediatek-drm of vdosys0 support for mt8195 soc: mediatek: add DDP_DOMPONENT_DITHER0 enum for mt8195 vdosys0 drm/mediatek: add suffix 0 to DDP_COMPONENT_DITHER for mt8195 vdosys0 soc: mediatek: remove DDP_DOMPONENT_DITHER from enum drivers/gpu/drm/mediatek/Makefile | 1 + drivers/gpu/drm/mediatek/mtk_disp_drv.h | 8 + drivers/gpu/drm/mediatek/mtk_disp_merge.c | 246 +++++++++++++ drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 6 + drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 65 +++- drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 2 + drivers/gpu/drm/mediatek/mtk_drm_drv.c | 151 +++++++- drivers/gpu/drm/mediatek/mtk_drm_drv.h | 7 + drivers/soc/mediatek/mt8167-mmsys.h | 2 +- drivers/soc/mediatek/mt8183-mmsys.h | 2 +- drivers/soc/mediatek/mt8186-mmsys.h | 4 +- drivers/soc/mediatek/mt8192-mmsys.h | 4 +- drivers/soc/mediatek/mt8195-mmsys.h | 370 ++++++++++++++++++++ drivers/soc/mediatek/mt8365-mmsys.h | 4 +- drivers/soc/mediatek/mtk-mmsys.c | 152 +++++++- drivers/soc/mediatek/mtk-mmsys.h | 6 + drivers/soc/mediatek/mtk-mutex.c | 95 ++++- include/linux/soc/mediatek/mtk-mmsys.h | 13 +- 18 files changed, 1098 insertions(+), 40 deletions(-) create mode 100644 drivers/gpu/drm/mediatek/mtk_disp_merge.c create mode 100644 drivers/soc/mediatek/mt8195-mmsys.h -- 2.18.0

7 31

[PATCH 00/22] drm/mediatek: Add mt8195 DisplayPort driver
by Guillaume Ranquet 25 May '22

25 May '22

this series is built around the DisplayPort driver. The dpi/dpintf driver and the added helper functions are required for the DisplayPort driver to work. This v9 is not quite ready yet, as project constraints forces me to publish v9 this week, I'm sorry if it's not standard practice. Moreover, it is still un-tested on a recent kernel. The integration kernel we are using is still based on 5.10... but we are actively working on bringing up a mt8195 integration branch on 5.17. The patches have been rebased on top of next-20220301 and have been tested to build sucessfully (no functional testing). Changes from v8: - The DP-Phy now has its own dt-bindings and now shares a regmap using the syscon facility with the DP driver. - hot plug detection has been removed from the Embedded Display Port. patch and moved to the patch adding External Display Port support. - started working on better error handling for the mtk_dp driver. - rebased on linux-next. - removal of tvd pll clocks re-introduced by mistake. - various coding style fixes. Things that are in my todolist for v10: - fixing the train_handler in the mtk_dp driver, as I haven't been able to reproduce locally (hopefully migrating to running the tests on a more recent kernel will help) - explaining the various sleep/delays introduced in the drivers - explaining some of the differences between mt8195 and "legacy" - retrieve CK/DE support from panel driver instead of hardcoding it into the dpi driver. - better error handling/reporting in mtk_dp - look into re-implementing mtk_dp_aux_transfer() using drm_dp_dpcd_read and drm_dp_dpcd_write as suggested by Rex. Older revisions: RFC - https://lore.kernel.org/linux-mediatek/20210816192523.1739365-1-msp@baylibr… v1 - https://lore.kernel.org/linux-mediatek/20210906193529.718845-1-msp@baylibre… v2 - https://lore.kernel.org/linux-mediatek/20210920084424.231825-1-msp@baylibre… v3 - https://lore.kernel.org/linux-mediatek/20211001094443.2770169-1-msp@baylibr… v4 - https://lore.kernel.org/linux-mediatek/20211011094624.3416029-1-msp@baylibr… v5 - https://lore.kernel.org/all/20211021092707.3562523-1-msp@baylibre.com/ v6 - https://lore.kernel.org/linux-mediatek/20211110130623.20553-1-granquet@bayl… v7 - https://lore.kernel.org/linux-mediatek/20211217150854.2081-1-granquet@bayli… v8 - https://lore.kernel.org/linux-mediatek/20220218145437.18563-1-granquet@bayl… Functional dependencies are: - Add Mediatek Soc DRM (vdosys0) support for mt8195 https://lore.kernel.org/all/20211026155911.17651-1-jason-jh.lin@mediatek.co… - Add MediaTek SoC DRM (vdosys1) support for mt8195 https://lore.kernel.org/all/20211029075203.17093-1-nancy.lin@mediatek.com/ Guillaume Ranquet (15): dt-bindings: mediatek,dp_phy: Add Display Port PHY binding drm/edid: Convert cea_sad helper struct to kernelDoc drm/edid: Add cea_sad helpers for freq/length drm/mediatek: dpi: move dpi limits to SoC config drm/mediatek: dpi: implement a CK/DE pol toggle in SoC config drm/mediatek: dpi: implement a swap_input toggle in SoC config drm/mediatek: dpi: move dimension mask to SoC config drm/mediatek: dpi: move hvsize_mask to SoC config drm/mediatek: dpi: move swap_shift to SoC config drm/mediatek: dpi: move the yuv422_en_bit to SoC config drm/mediatek: dpi: move the csc_enable bit to SoC config drm/mediatek: dpi: Add dpintf support drm/meditek: dpi: Add matrix_sel helper drm/mediatek: Add mt8195 External DisplayPort support drm/mediatek: DP audio support for mt8195 Jitao Shi (2): drm/mediatek: add hpd debounce drm/mediatek: change the aux retries times when receiving AUX_DEFER Markus Schneider-Pargmann (5): dt-bindings: mediatek,dpi: Add DP_INTF compatible dt-bindings: mediatek,dp: Add Display Port binding video/hdmi: Add audio_infoframe packing for DP phy: phy-mtk-dp: Add driver for DP phy drm/mediatek: Add mt8195 Embedded DisplayPort driver .../display/mediatek/mediatek,dp.yaml | 97 + .../display/mediatek/mediatek,dpi.yaml | 11 +- .../bindings/phy/mediatek,dp-phy.yaml | 43 + MAINTAINERS | 1 + drivers/gpu/drm/drm_edid.c | 74 + drivers/gpu/drm/mediatek/Kconfig | 8 + drivers/gpu/drm/mediatek/Makefile | 2 + drivers/gpu/drm/mediatek/mtk_dp.c | 3204 +++++++++++++++++ drivers/gpu/drm/mediatek/mtk_dp_reg.h | 568 +++ drivers/gpu/drm/mediatek/mtk_dpi.c | 222 +- drivers/gpu/drm/mediatek/mtk_dpi_regs.h | 38 + drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 8 + drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 1 + drivers/gpu/drm/mediatek/mtk_drm_drv.c | 6 +- drivers/gpu/drm/mediatek/mtk_drm_drv.h | 1 + drivers/phy/mediatek/Kconfig | 8 + drivers/phy/mediatek/Makefile | 1 + drivers/phy/mediatek/phy-mtk-dp.c | 202 ++ drivers/video/hdmi.c | 82 +- include/drm/dp/drm_dp_helper.h | 2 + include/drm/drm_edid.h | 25 +- include/linux/hdmi.h | 7 +- include/linux/soc/mediatek/mtk-mmsys.h | 3 +- 23 files changed, 4541 insertions(+), 73 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,dp-phy.yaml create mode 100644 drivers/gpu/drm/mediatek/mtk_dp.c create mode 100644 drivers/gpu/drm/mediatek/mtk_dp_reg.h create mode 100644 drivers/phy/mediatek/phy-mtk-dp.c -- 2.34.1

7 66

[syzbot] WARNING in __dma_map_sg_attrs
by syzbot 23 May '22

23 May '22

Hello, syzbot found the following issue on: HEAD commit: c5c17547b778 Merge tag 'net-5.16-rc3' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13a73609b00000 kernel config: https://syzkaller.appspot.com/x/.config?x=bf85c53718a1e697 dashboard link: https://syzkaller.appspot.com/bug?extid=10e27961f4da37c443b2 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+10e27961f4da37c443b2(a)syzkaller.appspotmail.com ------------[ cut here ]------------ WARNING: CPU: 2 PID: 17169 at kernel/dma/mapping.c:188 __dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Modules linked in: CPU: 0 PID: 17169 Comm: syz-executor.3 Not tainted 5.16.0-rc2-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 RIP: 0010:__dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Code: 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c 10 00 75 71 4c 8b 3d 70 6d b1 0d e9 db fe ff ff e8 86 ff 12 00 0f 0b e8 7f ff 12 00 <0f> 0b 45 31 e4 e9 54 ff ff ff e8 70 ff 12 00 49 8d 7f 50 48 b8 00 RSP: 0018:ffffc90002c0fb20 EFLAGS: 00010216 RAX: 0000000000013018 RBX: 0000000000000020 RCX: ffffc900037d4000 RDX: 0000000000040000 RSI: ffffffff8163d361 RDI: ffff8880182ae4d0 RBP: ffff8880182ae088 R08: 0000000000000002 R09: ffff888017ba054f R10: ffffffff8163d242 R11: 000000000008808a R12: 0000000000000000 R13: ffff888024ca5700 R14: 0000000000000001 R15: 0000000000000000 FS: 00007fa269e34700(0000) GS:ffff88802cb00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000040c120 CR3: 000000006c77c000 CR4: 0000000000150ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> dma_map_sgtable+0x70/0xf0 kernel/dma/mapping.c:264 drm_gem_map_dma_buf+0x12a/0x1e0 drivers/gpu/drm/drm_prime.c:633 __map_dma_buf drivers/dma-buf/dma-buf.c:675 [inline] dma_buf_map_attachment+0x39a/0x5b0 drivers/dma-buf/dma-buf.c:954 drm_gem_prime_import_dev.part.0+0x85/0x220 drivers/gpu/drm/drm_prime.c:939 drm_gem_prime_import_dev drivers/gpu/drm/drm_prime.c:982 [inline] drm_gem_prime_import+0xc8/0x200 drivers/gpu/drm/drm_prime.c:982 virtgpu_gem_prime_import+0x49/0x150 drivers/gpu/drm/virtio/virtgpu_prime.c:166 drm_gem_prime_fd_to_handle+0x21d/0x550 drivers/gpu/drm/drm_prime.c:318 drm_prime_fd_to_handle_ioctl+0x9b/0xd0 drivers/gpu/drm/drm_prime.c:374 drm_ioctl_kernel+0x27d/0x4e0 drivers/gpu/drm/drm_ioctl.c:782 drm_ioctl+0x51e/0x9d0 drivers/gpu/drm/drm_ioctl.c:885 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7fa26c8beae9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fa269e34188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fa26c9d1f60 RCX: 00007fa26c8beae9 RDX: 00000000200004c0 RSI: 00000000c00c642e RDI: 0000000000000005 RBP: 00007fa26c918f6d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc0019c51f R14: 00007fa269e34300 R15: 0000000000022000 </TASK> --- This report 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 issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

5 6

[PATCH] drm/bridge: fix anx6345 power up sequence
by Torsten Duwe 21 May '22

21 May '22

Align the power-up sequence with the known-good procedure documented in [1]: un-swap dvdd12 and dvdd25, and allow a little extra time for them to settle before de-asserting reset. Fixes: 6aa192698089b ("drm/bridge: Add Analogix anx6345 support") [1] https://github.com/OLIMEX/DIY-LAPTOP/blob/master/ HARDWARE/A64-TERES/TERES-PCB1-A64-MAIN/Rev.C/TERES_PCB1-A64-MAIN_Rev.C.pdf (page 5, blue comment down left) Reported-by: Harald Geyer <harald(a)ccbib.org> Signed-off-by: Torsten Duwe <duwe(a)lst.de> Cc: stable(a)vger.kernel.org --- This fixes the problem that e.g. X screensaver turns the screen black, and it stays black until the next reboot; definitely on the Teres-I, probably on the pinebook64, too. --- a/drivers/gpu/drm/bridge/analogix/analogix-anx6345.c +++ b/drivers/gpu/drm/bridge/analogix/analogix-anx6345.c @@ -309,27 +309,27 @@ static void anx6345_poweron(struct anx63 gpiod_set_value_cansleep(anx6345->gpiod_reset, 1); usleep_range(1000, 2000); - err = regulator_enable(anx6345->dvdd12); + err = regulator_enable(anx6345->dvdd25); if (err) { - DRM_ERROR("Failed to enable dvdd12 regulator: %d\n", + DRM_ERROR("Failed to enable dvdd25 regulator: %d\n", err); return; } - /* T1 - delay between VDD12 and VDD25 should be 0-2ms */ + /* T1 - delay between VDD25 and VDD12 should be 0-2ms */ usleep_range(1000, 2000); - err = regulator_enable(anx6345->dvdd25); + err = regulator_enable(anx6345->dvdd12); if (err) { - DRM_ERROR("Failed to enable dvdd25 regulator: %d\n", + DRM_ERROR("Failed to enable dvdd12 regulator: %d\n", err); return; } /* T2 - delay between RESETN and all power rail stable, - * should be 2-5ms + * should be at least 2-5ms, 10ms to be safe. */ - usleep_range(2000, 5000); + usleep_range(9000, 11000); gpiod_set_value_cansleep(anx6345->gpiod_reset, 0);

2 6

[Bug 215618] New: vblank related lockup during start of SteamVR using Valve Index HMD
by bugzilla-daemon＠kernel.org 21 May '22

21 May '22

https://bugzilla.kernel.org/show_bug.cgi?id=215618 Bug ID: 215618 Summary: vblank related lockup during start of SteamVR using Valve Index HMD Product: Drivers Version: 2.5 Kernel Version: 5.16.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: farmboy0(a)googlemail.com Regression: No Happens on nearly every SteamVR start but not always. Feb 17 00:06:29 kernel: [ 125.716702] [drm:dm_vblank_get_counter] *ERROR* dc_stream_state is NULL for crtc '1'! Feb 17 00:06:29 kernel: [ 125.716711] [drm:dm_crtc_get_scanoutpos] *ERROR* dc_stream_state is NULL for crtc '1'! Feb 17 00:06:29 kernel: [ 125.716713] [drm:dm_vblank_get_counter] *ERROR* dc_stream_state is NULL for crtc '1'! Feb 17 00:06:29 kernel: [ 125.716715] ------------[ cut here ]------------ Feb 17 00:06:29 kernel: [ 125.716715] amdgpu 0000:29:00.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev)) Feb 17 00:06:29 kernel: [ 125.716722] WARNING: CPU: 9 PID: 4516 at drivers/gpu/drm/drm_vblank.c:728 drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x367/0x380 Feb 17 00:06:29 kernel: [ 125.716728] Modules linked in: joydev Feb 17 00:06:29 kernel: [ 125.716730] CPU: 9 PID: 4516 Comm: VulkanVblankThr Not tainted 5.16.9 #1 Feb 17 00:06:29 kernel: [ 125.716732] Hardware name: Micro-Star International Co., Ltd. MS-7A31/X370 XPOWER GAMING TITANIUM (MS-7A31), BIOS 1.MS 06/24/2020 Feb 17 00:06:29 kernel: [ 125.716734] RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x367/0x380 Feb 17 00:06:29 kernel: [ 125.716737] Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 82 a7 35 00 48 c7 c1 d0 ca f1 ae 48 89 c6 4c 89 ea 48 c7 c7 92 36 f1 ae e8 cd 56 7d 00 <0f> 0b e9 ba fe ff ff e8 cd e0 84 00 66 66 2e 0f 1f 84 00 00 00 00 Feb 17 00:06:29 kernel: [ 125.716738] RSP: 0018:ffffad1f42d63b20 EFLAGS: 00010082 Feb 17 00:06:29 kernel: [ 125.716740] RAX: 0000000000000000 RBX: ffffffffad6e9060 RCX: 0000000000000000 Feb 17 00:06:29 kernel: [ 125.716741] RDX: 0000000000000003 RSI: ffffffffaeee68eb RDI: 00000000ffffffff Feb 17 00:06:29 kernel: [ 125.716742] RBP: ffffad1f42d63bb8 R08: 0000000000000000 R09: ffffad1f42d63958 Feb 17 00:06:29 kernel: [ 125.716743] R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000 Feb 17 00:06:29 kernel: [ 125.716744] R13: ffffa369c190c660 R14: 0000000000000000 R15: ffffa369c565e9d8 Feb 17 00:06:29 kernel: [ 125.716745] FS: 00007fb348913640(0000) GS:ffffa370bea40000(0000) knlGS:0000000000000000 Feb 17 00:06:29 kernel: [ 125.716746] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 00:06:29 kernel: [ 125.716747] CR2: 00007fb31c001248 CR3: 00000001cbf37000 CR4: 00000000003506e0 Feb 17 00:06:29 kernel: [ 125.716748] Call Trace: Feb 17 00:06:29 kernel: [ 125.716750] <TASK> Feb 17 00:06:29 kernel: [ 125.716752] ? __drm_err+0x72/0x90 Feb 17 00:06:29 kernel: [ 125.716755] drm_get_last_vbltimestamp+0xc8/0xe0 Feb 17 00:06:29 kernel: [ 125.716758] drm_update_vblank_count+0x84/0x3d0 Feb 17 00:06:29 kernel: [ 125.716759] ? queue_work_on+0x79/0x80 Feb 17 00:06:29 kernel: [ 125.716763] drm_vblank_enable+0x16b/0x1a0 Feb 17 00:06:29 kernel: [ 125.716765] drm_vblank_get+0xb8/0x100 Feb 17 00:06:29 kernel: [ 125.716767] drm_crtc_queue_sequence_ioctl+0x112/0x2d0 Feb 17 00:06:29 kernel: [ 125.716769] ? _drm_lease_held+0x46/0x80 Feb 17 00:06:29 kernel: [ 125.716771] ? drm_crtc_get_sequence_ioctl+0x1c0/0x1c0 Feb 17 00:06:29 kernel: [ 125.716773] drm_ioctl_kernel+0xd4/0x170 Feb 17 00:06:29 kernel: [ 125.716776] drm_ioctl+0x270/0x430 Feb 17 00:06:29 kernel: [ 125.716777] ? __check_object_size+0x68/0x180 Feb 17 00:06:29 kernel: [ 125.716781] ? drm_crtc_get_sequence_ioctl+0x1c0/0x1c0 Feb 17 00:06:29 kernel: [ 125.716783] ? smk_tskacc+0xd7/0x110 Feb 17 00:06:29 kernel: [ 125.716786] ? smack_file_ioctl+0xdb/0x120 Feb 17 00:06:29 kernel: [ 125.716788] ? trace_hardirqs_on+0x35/0xf0 Feb 17 00:06:29 kernel: [ 125.716791] amdgpu_drm_ioctl+0x5d/0xa0 Feb 17 00:06:29 kernel: [ 125.716793] __x64_sys_ioctl+0xac/0xe0 Feb 17 00:06:29 kernel: [ 125.716796] ? trace_hardirqs_on+0x35/0xf0 Feb 17 00:06:29 kernel: [ 125.716797] do_syscall_64+0x5c/0x80 Feb 17 00:06:29 kernel: [ 125.716800] ? exit_to_user_mode_prepare+0x44/0x1a0 Feb 17 00:06:29 kernel: [ 125.716803] ? trace_hardirqs_on_prepare+0x24/0x90 Feb 17 00:06:29 kernel: [ 125.716805] ? syscall_exit_to_user_mode+0x29/0x60 Feb 17 00:06:29 kernel: [ 125.716807] ? do_syscall_64+0x69/0x80 Feb 17 00:06:29 kernel: [ 125.716809] entry_SYSCALL_64_after_hwframe+0x44/0xae Feb 17 00:06:29 kernel: [ 125.716812] RIP: 0033:0x7fb398cdaa97 Feb 17 00:06:29 kernel: [ 125.716813] Code: 3c 1c e8 1c ff ff ff 85 c0 79 87 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 63 0c 00 f7 d8 64 89 01 48 Feb 17 00:06:29 kernel: [ 125.716815] RSP: 002b:00007fb348912af8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Feb 17 00:06:29 kernel: [ 125.716816] RAX: ffffffffffffffda RBX: 00007fb348912b30 RCX: 00007fb398cdaa97 Feb 17 00:06:29 kernel: [ 125.716817] RDX: 00007fb348912b30 RSI: 00000000c018643c RDI: 0000000000000050 Feb 17 00:06:29 kernel: [ 125.716818] RBP: 00000000c018643c R08: 0000000000000000 R09: 00007fb31c000bd0 Feb 17 00:06:29 kernel: [ 125.716819] R10: 0000000000000000 R11: 0000000000000246 R12: 00005652b28e1de8 Feb 17 00:06:29 kernel: [ 125.716820] R13: 0000000000000050 R14: 00005652b29acef0 R15: 00005652b28e1da0 Feb 17 00:06:29 kernel: [ 125.716822] </TASK> Feb 17 00:06:29 kernel: [ 125.716822] ---[ end trace e8b4537a57c9dbe1 ]--- Feb 17 00:06:29 kernel: [ 125.716823] [drm:dm_vblank_get_counter] *ERROR* dc_stream_state is NULL for crtc '1'! Feb 17 00:06:29 kernel: [ 125.716825] [drm:dm_crtc_get_scanoutpos] *ERROR* dc_stream_state is NULL for crtc '1'! Feb 17 00:06:29 kernel: [ 125.716827] [drm:dm_vblank_get_counter] *ERROR* dc_stream_state is NULL for crtc '1'! -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 2

[Regression] No framebuffer console on Rpi since 5.14-rc1
by Stefan Wahren 20 May '22

20 May '22

Hi guys, starting with Linux 5.14-rc1 the framebuffer console on Raspberry Pi 3/4 (no U-Boot, multi_v7_defconfig) isn't available anymore. The display shows the rainbow screen from the bootloader and than the HDMI screen goes black instead of kernel messages. I bisected the issue: 62fb9874f5da54fdb243003b386128037319b219 good e73f0f0ee7541171d89f2e2491130c7771ba58d3 bad e058a84bfddc42ba356a2316f2cf1141974625c9 bad a6eaf3850cb171c328a8b0db6d3c79286a1eba9d good 007b312c6f294770de01fbc0643610145012d244 good 18703923a66aecf6f7ded0e16d22eb412ddae72f good 334200bf52f0637a5ab8331c557dfcecbb9c30fa bad c707b73f0cfb1acc94a20389aecde65e6385349b bad caa18dd6dd9305d52943a6b59f410cbc960ad0a0 good 691cf8cd7a531dbfcc29d09a23c509a86fd9b24f bad 2fdcb55dfc86835e4845e3f422180b5596d23cb4 bad 6c3f953381e526a1623d4575660afae8b19ffa20 bad 5ea4dba68305d9648b9dba30036cc36d4e877bca bad 4a888ba03fd97d1cb0253581973533965bf348c4 good c5ef15ae09637fb51ae43e1d1d98329d67dd4fd6 good f611b1e7624ccdbd495c19e9805629e22265aa16 bad ff323d6d72e1e4971c8ba9e2f3cf8afc48f22383 good f611b1e7624ccdbd495c19e9805629e22265aa16 is the first bad commit commit f611b1e7624ccdbd495c19e9805629e22265aa16 Author: Kees Cook <keescook(a)chromium.org> Date: Wed Jun 2 14:52:50 2021 -0700 drm: Avoid circular dependencies for CONFIG_FB When cleaning up other drm config dependencies, it is too easy to create larger problems. Instead, mark CONFIG_FB as a "depends": drivers/gpu/drm/Kconfig:74:error: recursive dependency detected! I compared the changes to the config (based on multi_v7_defconfig) with and without this patch and it shows a lot of changes. Is this intended? Best regards Stefan

3 9

[PATCH v7 0/7] Introduce multitile support
by Andi Shyti 19 May '22

19 May '22

Hi, This is the second series that prepares i915 to host multitile platforms. It introduces the for_each_gt() macro that loops over the tiles to perform per gt actions. This patch is a combination of two patches developed originally by Abdiel, who introduced some refactoring during probe, and then Tvrtko has added the necessary tools to start using the various tiles. The second patch re-organises the sysfs interface to expose the API for each of the GTs. I decided to prioritise this patch over others to unblock Sujaritha for further development. A third series will still follow this. Thanks Michal and Andrzej for the reviews and support! Thanks, Andi Patchwork: https://patchwork.freedesktop.org/series/98741/ Changelog ========= v6 -> v7 - fixed a mock selftest error by initializing i915->gt[0] (thanks Tvrtko!) - removed spurious file added by mistake (thanks Matt!) - improved commit log in patch 7 (thanks Suja!) v5 -> v6 - address all Michal and Andrzej's reviews that consist mainly in code refactoring. v4 -> v5 - fixed Michal's reviews. - the sysfs patches have been split in 3 parts to make reviews easier. - Sujaritha's patch on pm throttle has been queued. - INTEL_REGION_LMEM has been renamed to INTEL_REGION_LMEM_0 - added the gt_is_root() helper - the sysfs files will be called intel_gt_sysfs_* instead of sysfs_gt_* v3 -> v4 - fixed Tvrtko's review: - remove the SYSFS_DEPRECATED_V2 mention from the commit log - reworded the error message when accessing deprecated files - errors in sysfs are printed as warnings as they are not fatal - the inline functions are moved to be out of line. and some other minor refactoring. v2 -> v3 - Added Matt and Sujaritha's r-b for patch 1 and 2. - Reworded the commit of patch 2 to underline the fact that the interface is useful also when used manually. v1 -> v2 - fixed a couple of coding style issues in patch 2. Andi Shyti (5): drm/i915: Rename INTEL_REGION_LMEM with INTEL_REGION_LMEM_0 drm/i915/gt: add gt_is_root() helper drm/i915/gt: create per-tile sysfs interface drm/i915/gt: Create per-tile RC6 sysfs interface drm/i915/gt: Create per-tile RPS sysfs interfaces Sujaritha Sundaresan (1): drm/i915/gt: Add sysfs throttle frequency interfaces Tvrtko Ursulin (1): drm/i915: Prepare for multiple GTs drivers/gpu/drm/i915/Makefile | 2 + drivers/gpu/drm/i915/display/intel_fb.c | 2 +- drivers/gpu/drm/i915/display/intel_fb_pin.c | 2 +- .../drm/i915/display/intel_plane_initial.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_lmem.c | 4 +- .../drm/i915/gem/selftests/i915_gem_dmabuf.c | 6 +- .../drm/i915/gem/selftests/i915_gem_migrate.c | 8 +- drivers/gpu/drm/i915/gt/intel_gt.c | 135 +++- drivers/gpu/drm/i915/gt/intel_gt.h | 22 +- drivers/gpu/drm/i915/gt/intel_gt_pm.c | 9 +- drivers/gpu/drm/i915/gt/intel_gt_sysfs.c | 122 ++++ drivers/gpu/drm/i915/gt/intel_gt_sysfs.h | 34 + drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c | 601 ++++++++++++++++++ drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.h | 15 + drivers/gpu/drm/i915/gt/intel_gt_types.h | 7 + drivers/gpu/drm/i915/gt/intel_rps.c | 18 + drivers/gpu/drm/i915/gt/intel_rps.h | 4 + drivers/gpu/drm/i915/i915_driver.c | 28 +- drivers/gpu/drm/i915/i915_drv.h | 8 + drivers/gpu/drm/i915/i915_reg.h | 11 + drivers/gpu/drm/i915/i915_sysfs.c | 310 +-------- drivers/gpu/drm/i915/i915_sysfs.h | 3 + drivers/gpu/drm/i915/intel_memory_region.c | 2 +- drivers/gpu/drm/i915/intel_memory_region.h | 7 +- drivers/gpu/drm/i915/intel_uncore.c | 11 +- drivers/gpu/drm/i915/intel_uncore.h | 3 +- .../gpu/drm/i915/selftests/mock_gem_device.c | 13 +- 27 files changed, 1023 insertions(+), 366 deletions(-) create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_sysfs.c create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_sysfs.h create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.h base-commit: 76874531ffae41683316380bd6d6227bbba12148 -- 2.35.1

5 16

[PATCH] omapfb: simplify the return expression of dsi_init_pll_data()
by cgel.zte＠gmail.com 19 May '22

19 May '22

From: Minghao Chi <chi.minghao(a)zte.com.cn> Simplify the return expression. Reported-by: Zeal Robot <zealci(a)zte.com.cn> Signed-off-by: Minghao Chi <chi.minghao(a)zte.com.cn> --- drivers/video/fbdev/omap2/omapfb/dss/hdmi_pll.c | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/drivers/video/fbdev/omap2/omapfb/dss/hdmi_pll.c b/drivers/video/fbdev/omap2/omapfb/dss/hdmi_pll.c index c5f89129dcdd..531b36d2232b 100644 --- a/drivers/video/fbdev/omap2/omapfb/dss/hdmi_pll.c +++ b/drivers/video/fbdev/omap2/omapfb/dss/hdmi_pll.c @@ -173,7 +173,6 @@ static int dsi_init_pll_data(struct platform_device *pdev, struct hdmi_pll_data { struct dss_pll *pll = &hpll->pll; struct clk *clk; - int r; clk = devm_clk_get(&pdev->dev, "sys_clk"); if (IS_ERR(clk)) { @@ -203,12 +202,7 @@ static int dsi_init_pll_data(struct platform_device *pdev, struct hdmi_pll_data } pll->ops = &dsi_pll_ops; - - r = dss_pll_register(pll); - if (r) - return r; - - return 0; + return dss_pll_register(pll); } int hdmi_pll_init(struct platform_device *pdev, struct hdmi_pll_data *pll, -- 2.25.1

2 1

[PATCH] video: hyperv_fb: Allow resolutions with size > 64 MB for Gen1
by Saurabh Sengar 19 May '22

19 May '22

This patch fixes a bug where GEN1 VMs doesn't allow resolutions greater than 64 MB size (eg 7680x4320). Unnecessary PCI check limits Gen1 VRAM to legacy PCI BAR size only (ie 64MB). Thus any, resolution requesting greater then 64MB (eg 7680x4320) would fail. MMIO region assigning this memory shouldn't be limited by PCI bar size. Signed-off-by: Saurabh Sengar <ssengar(a)linux.microsoft.com> --- drivers/video/fbdev/hyperv_fb.c | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/drivers/video/fbdev/hyperv_fb.c b/drivers/video/fbdev/hyperv_fb.c index c8e0ea2..58c304a 100644 --- a/drivers/video/fbdev/hyperv_fb.c +++ b/drivers/video/fbdev/hyperv_fb.c @@ -1009,7 +1009,6 @@ static int hvfb_getmem(struct hv_device *hdev, struct fb_info *info) struct pci_dev *pdev = NULL; void __iomem *fb_virt; int gen2vm = efi_enabled(EFI_BOOT); - resource_size_t pot_start, pot_end; phys_addr_t paddr; int ret; @@ -1060,23 +1059,7 @@ static int hvfb_getmem(struct hv_device *hdev, struct fb_info *info) dio_fb_size = screen_width * screen_height * screen_depth / 8; - if (gen2vm) { - pot_start = 0; - pot_end = -1; - } else { - if (!(pci_resource_flags(pdev, 0) & IORESOURCE_MEM) || - pci_resource_len(pdev, 0) < screen_fb_size) { - pr_err("Resource not available or (0x%lx < 0x%lx)\n", - (unsigned long) pci_resource_len(pdev, 0), - (unsigned long) screen_fb_size); - goto err1; - } - - pot_end = pci_resource_end(pdev, 0); - pot_start = pot_end - screen_fb_size + 1; - } - - ret = vmbus_allocate_mmio(&par->mem, hdev, pot_start, pot_end, + ret = vmbus_allocate_mmio(&par->mem, hdev, 0, -1, screen_fb_size, 0x100000, true); if (ret != 0) { pr_err("Unable to allocate framebuffer memory\n"); -- 1.8.3.1

5 6

[Bug 201497] New: [amdgpu]: '*ERROR* No EDID read' is back in 4.19
by bugzilla-daemon＠bugzilla.kernel.org 19 May '22

19 May '22

https://bugzilla.kernel.org/show_bug.cgi?id=201497 Bug ID: 201497 Summary: [amdgpu]: '*ERROR* No EDID read' is back in 4.19 Product: Drivers Version: 2.5 Kernel Version: 4.19 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: engywook(a)gmail.com Regression: No Hey, I have this EDID bug again, see https://lists.freedesktop.org/archives/amd-gfx/2018-July/023923.html 018d82e5f02ef3583411bcaa4e00c69786f46f19 seems to have gotten back in through: # first bad commit: [d98c71dadc2d0debdb80beb5a478baf1e6f98758] Merge drm-upstream/drm-next into drm-misc-next / Daniel -- You are receiving this mail because: You are watching the assignee of the bug.

2 26

← Newer
1
2
3
4
5
6
7
8
9
...
96
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2022