dri-devel March 2019

dri-devel@lists.freedesktop.org

294 participants
2102 discussions

[PATCH] gpu: drm: atomic_helper: Fix spelling errors
by Kieran Bingham 11 Mar '19

11 Mar '19

Trivial fixes identified while working on the DRM code. s/artifically/artificially/ s/achive/acheive/ Signed-off-by: Kieran Bingham <kieran.bingham+renesas(a)ideasonboard.com> --- drivers/gpu/drm/drm_atomic_helper.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c index 540a77a2ade9..ccb278ed1bf8 100644 --- a/drivers/gpu/drm/drm_atomic_helper.c +++ b/drivers/gpu/drm/drm_atomic_helper.c @@ -1752,7 +1752,7 @@ int drm_atomic_helper_commit(struct drm_device *dev, * * NOTE: Commit work has multiple phases, first hardware commit, then * cleanup. We want them to overlap, hence need system_unbound_wq to - * make sure work items don't artifically stall on each another. + * make sure work items don't artificially stall on each another. */ drm_atomic_state_get(state); @@ -1786,7 +1786,7 @@ EXPORT_SYMBOL(drm_atomic_helper_commit); * * Asynchronous workers need to have sufficient parallelism to be able to run * different atomic commits on different CRTCs in parallel. The simplest way to - * achive this is by running them on the &system_unbound_wq work queue. Note + * acheive this is by running them on the &system_unbound_wq work queue. Note * that drivers are not required to split up atomic commits and run an * individual commit in parallel - userspace is supposed to do that if it cares. * But it might be beneficial to do that for modesets, since those necessarily -- 2.19.1

2 2

[PATCH 0/3] drm/vboxvideo: Move the vboxvideo driver out of staging
by Hans de Goede 11 Mar '19

11 Mar '19

Hi All, This patch-series addresses the 2 TODO / FIXME items recently reported by Daniel and after that moves the vboxvideo driver out of staging. Note this applies on top of drm-misc-next + this patch: https://patchwork.kernel.org/patch/10824279/ Currently that patch is not yet in drm-misc, I can push it myself before pushing the rest of this series (after review). Greg, the intent is for this series to be merged upstream through drm-misc, may we have your Acked-by for that please? Regards, Hans

3 6

[Bug 109017] The drop in resolution with AMD Kaveri
by bugzilla-daemon＠freedesktop.org 11 Mar '19

11 Mar '19

https://bugs.freedesktop.org/show_bug.cgi?id=109017 --- Comment #9 from Dmitry <terapy-session(a)bk.ru> --- Now the bug does not appear. Perhaps this is due to the fact that I set all the parameters before installing Arch, or it was fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH] drm/stm: fix CONFIG_FB dependency
by Arnd Bergmann 11 Mar '19

11 Mar '19

The DRM_STM driver can be built independently of the framebuffer layer, but it causes a Kconfig warning: WARNING: unmet direct dependencies detected for FB_PROVIDE_GET_FB_UNMAPPED_AREA Depends on [n]: HAS_IOMEM [=y] && FB [=n] Selected by [y]: - DRM_STM [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARCH_STM32 [=n] || ARCH_MULTIPLATFORM [=y]) Selecting FB_PROVIDE_GET_FB_UNMAPPED_AREA actually has no effect if CONFIG_FB is disabled, so we can make it a conditional 'select' instead. Signed-off-by: Arnd Bergmann <arnd(a)arndb.de> --- drivers/gpu/drm/stm/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/stm/Kconfig b/drivers/gpu/drm/stm/Kconfig index 35367ada3bc1..d15b10de1da6 100644 --- a/drivers/gpu/drm/stm/Kconfig +++ b/drivers/gpu/drm/stm/Kconfig @@ -6,7 +6,7 @@ config DRM_STM select DRM_KMS_CMA_HELPER select DRM_PANEL_BRIDGE select VIDEOMODE_HELPERS - select FB_PROVIDE_GET_FB_UNMAPPED_AREA + select FB_PROVIDE_GET_FB_UNMAPPED_AREA if FB help Enable support for the on-chip display controller on -- 2.20.0

3 3

[PATCH v2 0/8] HDCP2.2 Phase II
by Ramalingam C 11 Mar '19

11 Mar '19

HDCP2.2 phase-II mojorly adds below features: Addition of three connector properties CP_Content_Type CP_Downstream_Info Addition of binary sysfs "hdcp_srm" parsing for HDCP1.4 and 2.2 SRM table Once HDCP1.4/2.2 authentication is completed gathering the all downstream topology for userspace Extending debugfs entry to provide the HDCP2.2 capability too. CP_Content_Type: This property is used to indicate the content type classification of a stream. Which indicate the HDCP version required for the rendering of that streams. This conten type is one of the parameter in the HDCP2.2 authentication flow, as even downstream repeaters will mandate the HDCP version requirement. Two values possible for content type of a stream: Type 0: Stream can be rendered only on HDCP encrypted link no restriction on HDCP versions. Type 1: Stream can be rendered only on HDCP2.2 encrypted link. There is a parallel effort in #wayland community to add the support for HDCP2.2 along with content type support. Patches are under review in #wayland community. CP_downstream_info: This blob property is used by the kernel to pass the downstream topology of the HDCP encrypted port to the userspace. This is used by the userspace to implement the HDCP repeater, which KMD implementing the HDCP transmitters(downstream ports) and userspace implementing the upstream port(HDCP receiver). Discussion is on going to add the downstream_info support in the weston HDCP stack. hdcp_srm: write only binary sysfs used by the userspace to pass the SRM table of HDCP1.4 and 2.2. These are nothing but revocated list of receiver IDs of the HDCP sinks. KMD will use this list to identify the revocated devices in the HDCP authentication and deny the hdcp encryption to it. v2: srm is passed through binary sysfs [Daniel] CP abbreviation is expanded except for downstream_info [Daniel] restrictions at atomic_set_property is removed [Maarten] upon content type change durin encryption, HDCP is restarted within kernel [Maarten] Resending it as previous submission was failed find the mentioned igt version. Series can be cloned from github https://github.com/ramalingampc2008/drm-tip.git hdcp2_2_p2_v2 Test-with: <20190308163049.9016-2-ramalingam.c(a)intel.com> Ramalingam C (8): drm/i915: debugfs: HDCP2.2 capability read drm: Add Content protection type property drm/i915: Attach content type property drm/i915: HDCP SRM parsing and revocation check drm/i915/sysfs: Node for hdcp srm drm: Add CP downstream_info property drm/i915: Populate downstream info for HDCP1.4 drm/i915: Populate downstream info for HDCP2.2 drivers/gpu/drm/drm_atomic_uapi.c | 8 + drivers/gpu/drm/drm_connector.c | 152 +++++++++++ drivers/gpu/drm/i915/i915_debugfs.c | 13 +- drivers/gpu/drm/i915/i915_drv.c | 1 + drivers/gpu/drm/i915/i915_drv.h | 6 + drivers/gpu/drm/i915/i915_sysfs.c | 32 +++ drivers/gpu/drm/i915/intel_ddi.c | 21 +- drivers/gpu/drm/i915/intel_drv.h | 7 +- drivers/gpu/drm/i915/intel_hdcp.c | 405 ++++++++++++++++++++++++++-- include/drm/drm_connector.h | 27 ++ include/drm/drm_hdcp.h | 33 +++ include/uapi/drm/drm_mode.h | 39 +++ 12 files changed, 712 insertions(+), 32 deletions(-) -- 2.19.1

2 9

WARNING in vkms_vblank_simulate
by syzbot 11 Mar '19

11 Mar '19

syzbot has bisected this bug to: commit 09ef09b4ab95dc405ad4171ec2cd8a4ff5227108 Author: Shayenne Moura <shayenneluzmoura(a)gmail.com> Date: Wed Feb 6 20:08:13 2019 +0000 drm/vkms: WARN when hrtimer_forward_now fails bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=128448cf200000 start commit: 09ef09b4 drm/vkms: WARN when hrtimer_forward_now fails git tree: upstream final crash: https://syzkaller.appspot.com/x/report.txt?x=118448cf200000 console output: https://syzkaller.appspot.com/x/log.txt?x=168448cf200000 kernel config: https://syzkaller.appspot.com/x/.config?x=c1e0e0ec44d1e5ff dashboard link: https://syzkaller.appspot.com/bug?extid=0871b14ca2e2fb64f6e3 userspace arch: amd64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1787db8d200000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17fc9883200000 Reported-by: syzbot+0871b14ca2e2fb64f6e3(a)syzkaller.appspotmail.com Fixes: 09ef09b4 ("drm/vkms: WARN when hrtimer_forward_now fails")

2 1

[PATCH v7 0/4] drm & vgaarb: handle vgacon removal in vgaarb.
by Gerd Hoffmann 11 Mar '19

11 Mar '19

v7: - codestype fixes. - new patch, switching i915 to use drm_fb_helper_remove_conflicting_pci_framebuffers v6: buildfix. Gerd Hoffmann (4): drm: move i915_kick_out_vgacon to vgaarb drm/fb-helper: call vga_remove_vgacon automatically. drm/qxl: remove conflicting framebuffers earlier drm/i915: switch to drm_fb_helper_remove_conflicting_pci_framebuffers include/drm/drm_fb_helper.h | 14 ++++++-- include/linux/vgaarb.h | 2 ++ drivers/gpu/drm/i915/i915_drv.c | 71 ++--------------------------------------- drivers/gpu/drm/qxl/qxl_drv.c | 5 ++- drivers/gpu/vga/vgaarb.c | 49 ++++++++++++++++++++++++++++ 5 files changed, 68 insertions(+), 73 deletions(-) -- 2.9.3

2 5

linux-next: manual merge of the drm tree with the drm-fixes tree
by Stephen Rothwell 11 Mar '19

11 Mar '19

Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c between commit: d63716658ac1 ("drm/amd/display: Use vrr friendly pageflip throttling in DC.") from the drm-fixes tree and commits: 8a48b44cd00f ("drm/amd/display: Call into DC once per multiplane flip") bc7f670ee04c ("drm/amd/display: Perform plane updates only when needed") from the drm tree. I had no idea how to resolve this, so I just effectively reverted the drm-fixes commit. I fixed it up (see above) 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. -- Cheers, Stephen Rothwell

3 3

[PATCH 0/5] drm: Add PSR helpers
by Sean Paul 11 Mar '19

11 Mar '19

From: Sean Paul <seanpaul(a)chromium.org> Hey all, Here's a set to add some helpers for drivers looking to implement PSR. I've converted rockchip as a proof of concept, and will likely do the work for msm dsi sometime in the coming months. PTAL, Sean Sean Paul (5): drm: Add helpers to kick off PSR enable/disable drm/rockchip: Check for fast link training before enabling psr drm/rockchip: Use the helpers for PSR drm/rockchip: Don't fully disable vop on PSR drm/rockchip: Use drm_atomic_helper_commit_tail_rpm Documentation/gpu/drm-kms-helpers.rst | 9 + drivers/gpu/drm/Makefile | 2 +- .../drm/bridge/analogix/analogix_dp_core.c | 206 +++++++---- .../drm/bridge/analogix/analogix_dp_core.h | 1 - drivers/gpu/drm/drm_atomic_helper.c | 34 ++ drivers/gpu/drm/drm_atomic_uapi.c | 5 + drivers/gpu/drm/drm_fb_helper.c | 9 + drivers/gpu/drm/drm_framebuffer.c | 18 + drivers/gpu/drm/drm_psr_helper.c | 343 ++++++++++++++++++ drivers/gpu/drm/rockchip/Makefile | 3 +- .../gpu/drm/rockchip/analogix_dp-rockchip.c | 70 ++-- drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 12 +- drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 37 +- drivers/gpu/drm/rockchip/rockchip_drm_psr.c | 290 --------------- drivers/gpu/drm/rockchip/rockchip_drm_psr.h | 30 -- drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 59 ++- include/drm/bridge/analogix_dp.h | 4 +- include/drm/drm_connector.h | 22 ++ include/drm/drm_crtc.h | 11 + include/drm/drm_mode_config.h | 6 + include/drm/drm_psr_helper.h | 24 ++ 21 files changed, 699 insertions(+), 496 deletions(-) create mode 100644 drivers/gpu/drm/drm_psr_helper.c delete mode 100644 drivers/gpu/drm/rockchip/rockchip_drm_psr.c delete mode 100644 drivers/gpu/drm/rockchip/rockchip_drm_psr.h create mode 100644 include/drm/drm_psr_helper.h -- Sean Paul, Software Engineer, Google / Chromium OS

3 9

WARNING in vkms_vblank_simulate
by syzbot 11 Mar '19

11 Mar '19

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2019