dri-devel August 2019

dri-devel@lists.freedesktop.org

318 participants
2338 discussions

[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 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 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

[PATCH v2 00/10] drivers, provide a way to add sysfs groups easily
by Greg Kroah-Hartman 14 May '20

14 May '20

This patch originally started out just as a way for platform drivers to easily add a sysfs group in a race-free way, but thanks to Dmitry's patch, this series now is for all drivers in the kernel (hey, a unified driver model works!!!) I've only converted a few platform drivers here in this series to show how it works, but other busses can be converted after the first patch goes into the tree. Here's the original 00 message, for people to get an idea of what is going on here: If a platform driver wants to add a sysfs group, it has to do so in a racy way, adding it after the driver is bound. To resolve this issue, have the platform driver core do this for the driver, making the individual drivers logic smaller and simpler, and solving the race at the same time. All of these patches depend on the first patch. I'll take the first one through my driver-core tree, and any subsystem maintainer can either ack their individul patch and I will be glad to also merge it, or they can wait until after 5.4-rc1 when the core patch hits Linus's tree and then take it, it's up to them. Thank to Richard Gong for the idea and the testing of the platform driver patch and to Dmitry Torokhov for rewriting the first patch to work well for all busses. ----- V2 - work for all busses and not just platform drivers. Dmitry Torokhov (1): driver core: add dev_groups to all drivers Greg Kroah-Hartman (9): uio: uio_fsl_elbc_gpcm: convert platform driver to use dev_groups input: keyboard: gpio_keys: convert platform driver to use dev_groups input: axp20x-pek: convert platform driver to use dev_groups firmware: arm_scpi: convert platform driver to use dev_groups olpc: x01: convert platform driver to use dev_groups platform: x86: hp-wmi: convert platform driver to use dev_groups video: fbdev: wm8505fb: convert platform driver to use dev_groups video: fbdev: w100fb: convert platform driver to use dev_groups video: fbdev: sm501fb: convert platform driver to use dev_groups arch/x86/platform/olpc/olpc-xo1-sci.c | 17 ++++------ drivers/base/dd.c | 14 ++++++++ drivers/firmware/arm_scpi.c | 5 +-- drivers/input/keyboard/gpio_keys.c | 13 ++------ drivers/input/misc/axp20x-pek.c | 15 ++------- drivers/platform/x86/hp-wmi.c | 47 +++++++-------------------- drivers/uio/uio_fsl_elbc_gpcm.c | 23 +++++-------- drivers/video/fbdev/sm501fb.c | 37 +++++---------------- drivers/video/fbdev/w100fb.c | 23 ++++++------- drivers/video/fbdev/wm8505fb.c | 13 ++++---- include/linux/device.h | 3 ++ 11 files changed, 76 insertions(+), 134 deletions(-) -- 2.22.0

4 13

[Bug 201505] New: Resume from suspend does not power up the display
by bugzilla-daemon＠bugzilla.kernel.org 11 May '20

11 May '20

https://bugzilla.kernel.org/show_bug.cgi?id=201505 Bug ID: 201505 Summary: Resume from suspend does not power up the display 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: 0xe2.0x9a.0x9b(a)gmail.com Regression: No Resuming the machine from suspend-to-ram no longer restores power to the display attached to an AMD GPU in Linux 4.19 (assuming the display has switched to sleep mode by itself because the computer hasn't been in use for a while). If the display is still powered on when resuming, it ends up blank. Linux 4.18 did not contain this bug. Kernel: 4.19 Module: amdgpu GPU: R9 390 -- You are receiving this mail because: You are watching the assignee of the bug.

1 6

[PATCH] drm: panel-orientation-quirks: 320 FHD and D330 HD
by David Santamaría Rogado 26 Apr '20

26 Apr '20

This adds the HD version of Lenovo Ideapad D330 and FHD version of Lenovo Ideapad Miix 320. This should work despite the dmi data is the same because the resolution checks. Signed-off-by: David Santamaría Rogado <howl.nsp(a)gmail.com> --- drivers/gpu/drm/drm_panel_orientation_quirks.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_panel_orientation_quirks.c b/drivers/gpu/drm/drm_panel_orientation_quirks.c index ffd95bfeaa94..896c783ce135 100644 --- a/drivers/gpu/drm/drm_panel_orientation_quirks.c +++ b/drivers/gpu/drm/drm_panel_orientation_quirks.c @@ -191,14 +191,28 @@ static const struct dmi_system_id orientation_data[] = { DMI_EXACT_MATCH(DMI_PRODUCT_VERSION, "MIIX 310-10ICR"), }, .driver_data = (void *)&lcd800x1280_rightside_up, - }, { /* Lenovo Ideapad Miix 320 */ + }, { /* Lenovo Ideapad Miix 320 (HD) */ .matches = { DMI_EXACT_MATCH(DMI_SYS_VENDOR, "LENOVO"), DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "80XF"), DMI_EXACT_MATCH(DMI_PRODUCT_VERSION, "Lenovo MIIX 320-10ICR"), }, .driver_data = (void *)&lcd800x1280_rightside_up, - }, { /* Lenovo Ideapad D330 */ + }, { /* Lenovo Ideapad Miix 320 (FHD) */ + .matches = { + DMI_EXACT_MATCH(DMI_SYS_VENDOR, "LENOVO"), + DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "80XF"), + DMI_EXACT_MATCH(DMI_PRODUCT_VERSION, "Lenovo MIIX 320-10ICR"), + }, + .driver_data = (void *)&lcd1200x1920_rightside_up, + }, { /* Lenovo Ideapad D330 (HD) */ + .matches = { + DMI_EXACT_MATCH(DMI_SYS_VENDOR, "LENOVO"), + DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "81H3"), + DMI_EXACT_MATCH(DMI_PRODUCT_VERSION, "Lenovo ideapad D330-10IGM"), + }, + .driver_data = (void *)&lcd800x1280_rightside_up, + }, { /* Lenovo Ideapad D330 (FHD) */ .matches = { DMI_EXACT_MATCH(DMI_SYS_VENDOR, "LENOVO"), DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "81H3"), -- 2.21.0

3 6

[Bug 202445] New: amdgpu/dc: framerate dropping below adaptive sync range causes screen flickering
by bugzilla-daemon＠bugzilla.kernel.org 07 Apr '20

07 Apr '20

https://bugzilla.kernel.org/show_bug.cgi?id=202445 Bug ID: 202445 Summary: amdgpu/dc: framerate dropping below adaptive sync range causes screen flickering Product: Drivers Version: 2.5 Kernel Version: 5.0rc4 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: libcg(a)protonmail.com Regression: No linux 5.0rc4 mesa 4aa64940c xf86-video-amdgpu a1b479c hardware: - R9 Fury - Samsung C27HG70 (1020.0 firmware, Freesync Ultimate Engine) I'm running the Unigine Valley benchmark extremely smoothly as long as the framerate stays in between 48-144fps. When it drops below that, I'm observing heavy stuttering and flickering in the darker parts of the image. The flickering also affects the loading screen when frames are rendered very infrequently. -- You are receiving this mail because: You are watching the assignee of the bug.

1 39

[PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()
by Peter Jones 07 Apr '20

07 Apr '20

This was sort of annoying me: random:~$ dmesg | tail -1 [523884.039227] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. random:~$ dmesg | grep -c "Reducing the compressed" 47 This patch makes it DRM_INFO_ONCE() just like the similar message farther down in that function is pr_info_once(). Signed-off-by: Peter Jones <pjones(a)redhat.com> --- drivers/gpu/drm/i915/intel_fbc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/intel_fbc.c b/drivers/gpu/drm/i915/intel_fbc.c index b431b6733cc..88b013758da 100644 --- a/drivers/gpu/drm/i915/intel_fbc.c +++ b/drivers/gpu/drm/i915/intel_fbc.c @@ -585,7 +585,7 @@ static int intel_fbc_alloc_cfb(struct intel_crtc *crtc) if (!ret) goto err_llb; else if (ret > 1) { - DRM_INFO("Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.\n"); + DRM_INFO_ONCE("Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.\n"); } -- 2.17.1

3 2

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2019