dri-devel March 2022

dri-devel@lists.freedesktop.org

370 participants
780 discussions

[PATCH] drm/edid: Update comments for drm_find_edid_extension
by Drew Davenport 11 Mar '22

11 Mar '22

In (40d9b043a89e drm/connector: store tile information from displayid (v3)) this function was changed to find EDID extensions by id, but the comments still are specific to the CEA extension. Signed-off-by: Drew Davenport <ddavenport(a)chromium.org> --- drivers/gpu/drm/drm_edid.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c index 561f53831e29..1afe73fbf3e0 100644 --- a/drivers/gpu/drm/drm_edid.c +++ b/drivers/gpu/drm/drm_edid.c @@ -3326,7 +3326,7 @@ add_detailed_modes(struct drm_connector *connector, struct edid *edid, #define EDID_CEA_VCDB_QS (1 << 6) /* - * Search EDID for CEA extension block. + * Search EDID for the extension block with id @ext_id. */ const u8 *drm_find_edid_extension(const struct edid *edid, int ext_id, int *ext_index) @@ -3338,7 +3338,7 @@ const u8 *drm_find_edid_extension(const struct edid *edid, if (edid == NULL || edid->extensions == 0) return NULL; - /* Find CEA extension */ + /* Find extension that matches @ext_id */ for (i = *ext_index; i < edid->extensions; i++) { edid_ext = (const u8 *)edid + EDID_LENGTH * (i + 1); if (edid_ext[0] == ext_id) -- 2.35.1.723.g4982287a31-goog

1 0

[PATCH v3 0/4] Ingenic DRM bridge_atomic_enable proposal
by Christophe Branchereau 11 Mar '22

11 Mar '22

Hello, v3 : Drop -spi in the compatible string, adjust bindings doc accordingly KR Christophe ------------------------ Hello, this is the v2 for my set of patches : - use dev_err_probe() instead of dev_err() in the newvision panel driver probe function - add bindings documentation for the Leadtek ltk035c5444t Cheers - Christophe ------------------------ Hello, this is a set of patches to allow the upstreaming of the NV3052C panel found in the Anbernic RG350M mips gaming handheld. It was never upstreamed so far due to a longstanding graphical bug, which I propose to solve by introducing ingenic_drm_bridge_atomic_enable in the drm driver so the CRTC can be enabled after the panel itself slept out, and not before as it used to. After the drm change, 2 of the existing panels have to be modified accordingly to introduce missing .enable and .disable in their code. Christophe Branchereau (4): drm/ingenic : add ingenic_drm_bridge_atomic_enable drm/panel: Add panel driver for NewVision NV3052C based LCDs drm/panel : innolux-ej030na and abt-y030xx067a : add .enable and .disable dt-bindings: display/panel: Add Leadtek ltk035c5444t .../display/panel/leadtek,ltk035c5444t.yaml | 59 +++ drivers/gpu/drm/ingenic/ingenic-drm-drv.c | 19 +- drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile | 1 + drivers/gpu/drm/panel/panel-abt-y030xx067a.c | 23 +- drivers/gpu/drm/panel/panel-innolux-ej030na.c | 31 +- .../gpu/drm/panel/panel-newvision-nv3052c.c | 497 ++++++++++++++++++ 7 files changed, 627 insertions(+), 12 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/panel/leadtek,ltk035c5444t.yaml create mode 100644 drivers/gpu/drm/panel/panel-newvision-nv3052c.c -- 2.35.1

2 6

[Bug 215648] New: amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic
by bugzilla-daemon＠kernel.org 11 Mar '22

11 Mar '22

https://bugzilla.kernel.org/show_bug.cgi?id=215648 Bug ID: 215648 Summary: amdgpu: Changing monitor configuration (plug/unplug/wake from DPMS) causes kernel panic Product: Drivers Version: 2.5 Kernel Version: 5.15.12 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: pr_kernel(a)tum.fail Regression: No Hi! My Lenovo T14s (AMD) crashes with a panic (https://imgur.com/a/P6Twvov) when I unplug/replug any monitor. This also happens when an external display wakes from DPMS. I have bisected the issue to the same 0f591d17e36e08313b0c440b99b0e57b47e01a9a as Jose Mestre did in #215511. The patch proposed there (that is already mainlined, if I see that correctly) does not help. Alex Deucher asked me to open this as a new bug. I have tried all kernel up to 5.15.24 -- I cannot try 5.16 as I use zfs as root device the and zfs module is not (yet) compatible with 5.16. Is there anything you would like me to try or should my issue be fixed in 5.16+? Cheers, Philipp -- 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 6

[PATCH v2 0/4] Ingenic DRM bridge_atomic_enable proposal
by Christophe Branchereau 11 Mar '22

11 Mar '22

Hello, this is the v2 for my set of patches : - use dev_err_probe() instead of dev_err() in the newvision panel driver probe function - add bindings documentation for the Leadtek ltk035c5444t Cheers - Christophe ------------------------ Hello, this is a set of patches to allow the upstreaming of the NV3052C panel found in the Anbernic RG350M mips gaming handheld. It was never upstreamed so far due to a longstanding graphical bug, which I propose to solve by introducing ingenic_drm_bridge_atomic_enable in the drm driver so the CRTC can be enabled after the panel itself slept out, and not before as it used to. After the drm change, 2 of the existing panels have to be modified accordingly to introduce missing .enable and .disable in their code. Christophe Branchereau (4): drm/ingenic : add ingenic_drm_bridge_atomic_enable drm/panel: Add panel driver for NewVision NV3052C based LCDs drm/panel : innolux-ej030na and abt-y030xx067a : add .enable and .disable dt-bindings: display/panel: Add Leadtek ltk035c5444t .../panel/leadtek,ltk035c5444t-spi.yaml | 59 +++ drivers/gpu/drm/ingenic/ingenic-drm-drv.c | 19 +- drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile | 1 + drivers/gpu/drm/panel/panel-abt-y030xx067a.c | 23 +- drivers/gpu/drm/panel/panel-innolux-ej030na.c | 31 +- .../gpu/drm/panel/panel-newvision-nv3052c.c | 497 ++++++++++++++++++ 7 files changed, 627 insertions(+), 12 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/panel/leadtek,ltk035c5444t-spi.yaml create mode 100644 drivers/gpu/drm/panel/panel-newvision-nv3052c.c -- 2.34.1

3 7

[PATCH 0/2] drm/i915: Avoid explicit IRQ-off sections.
by Sebastian Andrzej Siewior 11 Mar '22

11 Mar '22

Hi, these two patches are from the RT queue. They avoid IRQ-off checks and IRQ-off regions which are not valid/ possible on PREEMPT_RT and are not needed on !PREEMPT_RT. Sebastian

1 2

[PATCH] devcoredump: increase the device delete timeout to 10 mins
by Abhinav Kumar 11 Mar '22

11 Mar '22

There are cases where depending on the size of the devcoredump and the speed at which the usermode reads the dump, it can take longer than the current 5 mins timeout. This can lead to incomplete dumps as the device is deleted once the timeout expires. One example is below where it took 6 mins for the devcoredump to be completely read. 04:22:24.668 23916 23994 I HWDeviceDRM::DumpDebugData: Opening /sys/class/devcoredump/devcd6/data 04:28:35.377 23916 23994 W HWDeviceDRM::DumpDebugData: Freeing devcoredump node Increase the timeout to 10 mins to accommodate system delays and large coredump sizes. Signed-off-by: Abhinav Kumar <quic_abhinavk(a)quicinc.com> --- drivers/base/devcoredump.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/base/devcoredump.c b/drivers/base/devcoredump.c index f4d794d..6b83ae5 100644 --- a/drivers/base/devcoredump.c +++ b/drivers/base/devcoredump.c @@ -18,8 +18,8 @@ static struct class devcd_class; /* global disable flag, for security purposes */ static bool devcd_disabled; -/* if data isn't read by userspace after 5 minutes then delete it */ -#define DEVCD_TIMEOUT (HZ * 60 * 5) +/* if data isn't read by userspace after 10 minutes then delete it */ +#define DEVCD_TIMEOUT (HZ * 60 * 10) struct devcd_entry { struct device devcd_dev; -- 2.7.4

5 21

[PATCH v2 0/8] Some more bits for small BAR enabling
by Matthew Auld 11 Mar '22

11 Mar '22

The leftover bits around dealing with stolen-local memory + small BAR, plus some related fixes. v2: some tweaks based on feedback from Ville -- 2.34.1

3 10

[PATCH 0/2] xen/grant-table: do some cleanup
by Juergen Gross 11 Mar '22

11 Mar '22

Cleanup grant table code by removing unused functionality. Juergen Gross (2): xen/grant-table: remove gnttab_*transfer*() functions xen/grant-table: remove readonly parameter from functions drivers/block/xen-blkfront.c | 8 +- drivers/char/tpm/xen-tpmfront.c | 2 +- drivers/gpu/drm/xen/xen_drm_front_evtchnl.c | 2 +- drivers/input/misc/xen-kbdfront.c | 4 +- drivers/net/xen-netfront.c | 13 +- drivers/pci/xen-pcifront.c | 2 +- drivers/scsi/xen-scsifront.c | 4 +- drivers/usb/host/xen-hcd.c | 4 +- drivers/xen/gntalloc.c | 2 +- drivers/xen/gntdev-dmabuf.c | 2 +- drivers/xen/grant-table.c | 151 +++----------------- drivers/xen/pvcalls-front.c | 6 +- drivers/xen/xen-front-pgdir-shbuf.c | 3 +- include/xen/grant_table.h | 13 +- net/9p/trans_xen.c | 8 +- sound/xen/xen_snd_front_evtchnl.c | 2 +- 16 files changed, 50 insertions(+), 176 deletions(-) -- 2.34.1

2 2

[PATCH v3 0/4] Improve anti-pre-emption w/a for compute workloads
by John.C.Harrison＠Intel.com 11 Mar '22

11 Mar '22

From: John Harrison <John.C.Harrison(a)Intel.com> Compute workloads are inherently not pre-emptible on current hardware. Thus the pre-emption timeout was disabled as a workaround to prevent unwanted resets. Instead, the hang detection was left to the heartbeat and its (longer) timeout. This is undesirable with GuC submission as the heartbeat is a full GT reset rather than a per engine reset and so is much more destructive. Instead, just bump the pre-emption timeout to a big value. Also, update the heartbeat to allow such a long pre-emption delay in the final heartbeat period. v2: Add clamping helpers. v3: Remove long timeout algorithm and replace with hard coded value (review feedback from Tvrtko). Also, fix execlist selftest failure and fix bug in compute enabling patch related to pre-emption timeouts. Signed-off-by: John Harrison <John.C.Harrison(a)Intel.com> John Harrison (4): drm/i915/guc: Limit scheduling properties to avoid overflow drm/i915: Fix compute pre-emption w/a to apply to compute engines drm/i915: Make the heartbeat play nice with long pre-emption timeouts drm/i915: Improve long running OCL w/a for GuC submission drivers/gpu/drm/i915/Kconfig.profile | 26 +++++- drivers/gpu/drm/i915/gt/intel_engine.h | 6 ++ drivers/gpu/drm/i915/gt/intel_engine_cs.c | 92 +++++++++++++++++-- .../gpu/drm/i915/gt/intel_engine_heartbeat.c | 18 ++++ drivers/gpu/drm/i915/gt/sysfs_engines.c | 25 +++-- drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 9 ++ 6 files changed, 153 insertions(+), 23 deletions(-) -- 2.25.1

5 14

[PATCH] video: fbdev: kyro: make read-only array ODValues static const
by Colin Ian King 11 Mar '22

11 Mar '22

Don't populate the read-only array ODValues on the stack but instead make it static const. Also makes the object code a little smaller. Signed-off-by: Colin Ian King <colin.i.king(a)gmail.com> --- drivers/video/fbdev/kyro/STG4000InitDevice.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/fbdev/kyro/STG4000InitDevice.c b/drivers/video/fbdev/kyro/STG4000InitDevice.c index 21875d3c2dc2..ffeb355c8b50 100644 --- a/drivers/video/fbdev/kyro/STG4000InitDevice.c +++ b/drivers/video/fbdev/kyro/STG4000InitDevice.c @@ -124,7 +124,7 @@ u32 ProgramClock(u32 refClock, u32 ulScore, ulPhaseScore, ulVcoScore; u32 ulTmp = 0, ulVCO; u32 ulScaleClockReq, ulMinClock, ulMaxClock; - u32 ODValues[] = { 1, 2, 0 }; + static const u32 ODValues[] = { 1, 2, 0 }; /* Translate clock in Hz */ coreClock *= 100; /* in Hz */ -- 2.35.1

2 1

← Newer
1
...
51
52
53
54
55
56
57
...
78
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2022