[Intel-gfx] [PATCH] drm/i915/dp: Check for Low voltage IO only for eDP

The low voltage sku check can be ignored as OEMs need to consider that when designing the board and then put any limits in VBT. Due to this check many DP sink that can be run with higher link rate, are run at lower link rate, thereby pruning the resolutions that are intended to be working as per b

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev10)

this patch is not related this incomplete issue. This patch series fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation, etc. This patch has no code changes affecting the test case reported here (cache mode change after suspend). T

Re: [Intel-gfx] [PATCH v5 1/7] drm: Move and add a few utility macros into drm util header

On 7/25/22 2:36 PM, Andrzej Hajda wrote: On 25.07.2022 11:25, Gwan-gyeong Mun wrote: It moves overflows_type utility macro into drm util header from i915_utils header. The overflows_type can be used to catch the truncation between data types. And it adds safe_conversion() macro which perform

[Intel-gfx] [PATCH] drm/i915: disable pci resize on 32-bit machine

PCI bar resize only works with 64 bit BAR so disable this on 32-bit machine. Fixes: a91d1a17cd341 ("drm/i915: Add support for LMEM PCIe resizable bar") Signed-off-by: Nirmoy Das --- drivers/gpu/drm/i915/gt/intel_region_lmem.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/dr

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dp: Check for Low voltage IO only for eDP (rev2)

== Series Details == Series: drm/i915/dp: Check for Low voltage IO only for eDP (rev2) URL : https://patchwork.freedesktop.org/series/105573/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943 -> Patchwork_105573v2 Summary

Re: [Intel-gfx] [RFC 02/10] drm/i915/vm_bind: Bind and unbind mappings

On 26/07/2022 06:07, Niranjana Vishwanathapura wrote: On Mon, Jul 18, 2022 at 11:55:41AM +0100, Tvrtko Ursulin wrote: On 01/07/2022 23:50, Niranjana Vishwanathapura wrote: Bind and unbind the mappings upon VM_BIND and VM_UNBIND calls. Signed-off-by: Niranjana Vishwanathapura Signed-off-b

Re: [Intel-gfx] [PATCH] drm/i915: Pass drm_i915_private struct instead of gt for gen11_gu_misc_irq_handler/ack()

On 25/07/2022 19:38, Srivatsa, Anusha wrote: @Ursulin, Tvrtko Is this wat you had in mind? Two functions aligned in prototype yes - but I left to you guys which prototype is correct. AFAICT Matt looked and concluded i915 is correct so that's good for me. Regards, Tvrtko -Original M

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: disable pci resize on 32-bit machine

== Series Details == Series: drm/i915: disable pci resize on 32-bit machine URL : https://patchwork.freedesktop.org/series/106708/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106708v1 Summary ---

Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for Sanitycheck PCI BARs

Patchwork wrote on pon [2022-lip-25 19:45:33 +]: > == Series Details == > > Series: Sanitycheck PCI BARs > URL : https://patchwork.freedesktop.org/series/106686/ > State : failure > > == Summary == > > Error: make failed > CALLscripts/checksyscalls.sh > CALLscripts/atomic/che

Re: [Intel-gfx] [PATCH v2 4/6] drm/i915: Implement intersect/compatible functions

On 25/07/2022 12:42, Arunpravin Paneer Selvam wrote: Implemented a new intersect and compatible callback function fetching start offset from drm buddy allocator. Signed-off-by: Christian König Signed-off-by: Arunpravin Paneer Selvam --- drivers/gpu/drm/i915/i915_ttm_buddy_manager.c | 43

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dp: Check for Low voltage IO only for eDP (rev2)

== Series Details == Series: drm/i915/dp: Check for Low voltage IO only for eDP (rev2) URL : https://patchwork.freedesktop.org/series/105573/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_105573v2_full ===

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: disable pci resize on 32-bit machine

== Series Details == Series: drm/i915: disable pci resize on 32-bit machine URL : https://patchwork.freedesktop.org/series/106708/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106708v1_full Summary

Re: [Intel-gfx] [PATCH v4] drm/i915: stop using swiotlb

On 25/07/2022 15:18, Robert Beckett wrote: Calling swiotlb functions directly is nowadays considered harmful. See https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/ Replace swiotlb_max_segment() calls with dma_max_mapping_size(). In i915_gem_object_get_pages_internal() no longer

[Intel-gfx] [PATCH] drm/i915/tc: Fix PHY ownership programming in HDMI legacy mode

Make sure the TypeC PHY ownership flag is not getting reset during an HDMI modeset on the given port. Besides the WARN this triggered, it didn't cause other issues, since for TypeC legacy mode setting the PHY ownership flag is optional (there is no other user of the PHY besides display). Reported-

Re: [Intel-gfx] [PATCH v4] drm/i915: stop using swiotlb

On 26/07/2022 14:12, Tvrtko Ursulin wrote: On 25/07/2022 15:18, Robert Beckett wrote: Calling swiotlb functions directly is nowadays considered harmful. See https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/ Replace swiotlb_max_segment() calls with dma_max_mapping_size(). In i

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/tc: Fix PHY ownership programming in HDMI legacy mode

== Series Details == Series: drm/i915/tc: Fix PHY ownership programming in HDMI legacy mode URL : https://patchwork.freedesktop.org/series/106718/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106718v1 Su

[Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure

From: Chris Wilson We report object allocation failures to userspace with ENOMEM, yet we still show the memory warning after failing to shrink device allocated pages. While this warning is similar to other system page allocation failures, it is superfluous to the ENOMEM provided directly to users

[Intel-gfx] [PATCH] drm/i915/gem: Remove shared locking on freeing objects

From: Chris Wilson The obj->base.resv may be shared across many objects, some of which may still be live and locked, preventing objects from being freed indefintely. We could individualise the lock during the free, or rely on a freed object having no contention and being able to immediately free

Re: [Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure

Please ignore this one. Nirmoy On 7/26/2022 4:47 PM, Nirmoy Das wrote: From: Chris Wilson We report object allocation failures to userspace with ENOMEM, yet we still show the memory warning after failing to shrink device allocated pages. While this warning is similar to other system page all

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Suppress oom warning for shmemfs object allocation failure (rev3)

== Series Details == Series: drm/i915: Suppress oom warning for shmemfs object allocation failure (rev3) URL : https://patchwork.freedesktop.org/series/106528/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Suppress oom warning for shmemfs object allocation failure (rev3)

== Series Details == Series: drm/i915: Suppress oom warning for shmemfs object allocation failure (rev3) URL : https://patchwork.freedesktop.org/series/106528/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106528v3 ==

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/gem: Remove shared locking on freeing objects

== Series Details == Series: drm/i915/gem: Remove shared locking on freeing objects URL : https://patchwork.freedesktop.org/series/106720/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] [PATCH v5] drm/i915: stop using swiotlb

Calling swiotlb functions directly is nowadays considered harmful. See https://lore.kernel.org/intel-gfx/20220711082614.ga29...@lst.de/ Replace swiotlb_max_segment() calls with dma_max_mapping_size(). In i915_gem_object_get_pages_internal() no longer consider max_segment only if CONFIG_SWIOTLB is

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gem: Remove shared locking on freeing objects

== Series Details == Series: drm/i915/gem: Remove shared locking on freeing objects URL : https://patchwork.freedesktop.org/series/106720/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943 -> Patchwork_106720v1 Summary --

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/tc: Fix PHY ownership programming in HDMI legacy mode

== Series Details == Series: drm/i915/tc: Fix PHY ownership programming in HDMI legacy mode URL : https://patchwork.freedesktop.org/series/106718/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106718v1_full ==

Re: [Intel-gfx] [PATCH] drm/i915: Pass drm_i915_private struct instead of gt for gen11_gu_misc_irq_handler/ack()

Thanks Tvrtko :) @Roper, Matthew D Did you have any other feedback on this patch? Anusha > -Original Message- > From: Tvrtko Ursulin > Sent: Tuesday, July 26, 2022 1:59 AM > To: Srivatsa, Anusha ; intel- > g...@lists.freedesktop.org; Ursulin, Tvrtko > Subject: Re: [Intel-gfx] [PATCH] dr

Re: [Intel-gfx] [PATCH] drm/i915/display: Audio keep alive timestamp cdclk divisors

Hi, On Fri, 22 Jul 2022, Taylor, Clinton A wrote: > Use BSPEC values for the Audio Keep alive M and N values as included in > the cdclk BSPEC pages for display > 13 looks good, only a few very minor style comments. I had a table in my original patch, but Ville preferred calculating on-the-fly

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: stop using swiotlb (rev5)

== Series Details == Series: drm/i915: stop using swiotlb (rev5) URL : https://patchwork.freedesktop.org/series/106589/ State : success == Summary == CI Bug Log - changes from CI_DRM_11944 -> Patchwork_106589v5 Summary --- **SUCCESS*

Re: [Intel-gfx] [PATCH] drm/i915/dp: wait on timeout before retry

On Mon, Jul 04, 2022 at 04:01:23PM +, Murthy, Arun R wrote: > > On Mon, Jul 04, 2022 at 12:53:52PM +0530, Arun R Murthy wrote: > > > On linktraining error/timeout before retry need to wait for 400usec as > > > per the DP CTS spec1.2 > > > > s/CTS// > > > > > Under section 2.7.2 AUX Transactio

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dp: Check for Low voltage IO only for eDP (rev2)

== Series Details == Series: drm/i915/dp: Check for Low voltage IO only for eDP (rev2) URL : https://patchwork.freedesktop.org/series/105573/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_105573v2_full ===

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/ttm: Fix dummy res NULL ptr deref bug

== Series Details == Series: drm/ttm: Fix dummy res NULL ptr deref bug URL : https://patchwork.freedesktop.org/series/106727/ State : warning == Summary == Error: dim checkpatch failed f8fdc80c51ce drm/ttm: Fix dummy res NULL ptr deref bug -:107: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrappe

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Suppress oom warning for shmemfs object allocation failure (rev3)

== Series Details == Series: drm/i915: Suppress oom warning for shmemfs object allocation failure (rev3) URL : https://patchwork.freedesktop.org/series/106528/ State : success == Summary == CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106528v3_full

Re: [Intel-gfx] [PATCH] drm/i915/gem: Remove shared locking on freeing objects

On 26/07/2022 15:48, Nirmoy Das wrote: From: Chris Wilson The obj->base.resv may be shared across many objects, some of which may still be live and locked, preventing objects from being freed indefintely. We could individualise the lock during the free, or rely on a freed object having no conte

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/ttm: Fix dummy res NULL ptr deref bug

== Series Details == Series: drm/ttm: Fix dummy res NULL ptr deref bug URL : https://patchwork.freedesktop.org/series/106727/ State : success == Summary == CI Bug Log - changes from CI_DRM_11945 -> Patchwork_106727v1 Summary --- **SU

Re: [Intel-gfx] [PATCH 1/2] drm/i915/gem: Avoid taking runtime-pm under the shrinker

On 20/07/2022 11:16, Janusz Krzysztofik wrote: From: Chris Wilson Inside the shrinker, we cannot wake the device as that may cause recursion into fs-reclaim, so instead we only unbind vma if the device is currently awake. (In order to provide reclaim while asleep, we do wake the device up durin

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gem: Remove shared locking on freeing objects

== Series Details == Series: drm/i915/gem: Remove shared locking on freeing objects URL : https://patchwork.freedesktop.org/series/106720/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11943_full -> Patchwork_106720v1_full

[Intel-gfx] [PATCH] drm/i915/guc: Cancel GuC engine busyness worker synchronously

The worker is canceled in gt_park path, but earlier it was assumed that gt_park path cannot sleep and the cancel is asynchronous. This caused a race with suspend flow where the worker runs after suspend and causes an unclaimed register access warning. Cancel the worker synchronously since the gt_pa

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Cancel GuC engine busyness worker synchronously

== Series Details == Series: drm/i915/guc: Cancel GuC engine busyness worker synchronously URL : https://patchwork.freedesktop.org/series/106738/ State : warning == Summary == Error: dim checkpatch failed 1dd66d8a76c6 drm/i915/guc: Cancel GuC engine busyness worker synchronously -:32: WARNING:

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/guc: Cancel GuC engine busyness worker synchronously

== Series Details == Series: drm/i915/guc: Cancel GuC engine busyness worker synchronously URL : https://patchwork.freedesktop.org/series/106738/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11945 -> Patchwork_106738v1 Sum

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev5)

== Series Details == Series: drm/i915: stop using swiotlb (rev5) URL : https://patchwork.freedesktop.org/series/106589/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11944_full -> Patchwork_106589v5_full Summary ---

Re: [Intel-gfx] [PATCH 12/15] drm/i915/huc: stall media submission until HuC is loaded

All looks good: Reviewed-by: Alan Previn On Thu, 2022-06-09 at 16:19 -0700, Ceraolo Spurio, Daniele wrote: > Wait on the fence to be signalled to avoid the submissions finding HuC > not yet loaded. > > Signed-off-by: Daniele Ceraolo Spurio > Cc: Tony Ye > --- > drivers/gpu/drm/i915/gt/uc/int

Re: [Intel-gfx] [PATCH 06/15] mei: pxp: support matching with a gfx discrete card

On Thu, 2022-06-09 at 16:19 -0700, Ceraolo Spurio, Daniele wrote: > From: Tomas Winkler > > Support matching with a discrete graphics card. > > Signed-off-by: Tomas Winkler > Cc: Vitaly Lubart > --- > drivers/misc/mei/pxp/mei_pxp.c | 13 ++--- > 1 file changed, 10 insertions(+), 3 de

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/ttm: Fix dummy res NULL ptr deref bug

== Series Details == Series: drm/ttm: Fix dummy res NULL ptr deref bug URL : https://patchwork.freedesktop.org/series/106727/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11945_full -> Patchwork_106727v1_full Summary -

Re: [Intel-gfx] [PATCH 05/15] mei: pxp: add command streamer API to the PXP driver

code looks in order and this patch hasnt too much meat to it anyways. I have 1 question but its not pertaining to the code but rather to the backend firmware expectation, see below: On Thu, 2022-06-09 at 16:19 -0700, Ceraolo Spurio, Daniele wrote: > From: Vitaly Lubart > > Adding command stream

Re: [Intel-gfx] linux-next: manual merge of the drm tree with the drm-misc-fixes tree

Hi all, On Mon, 18 Jul 2022 09:44:53 +1000 Stephen Rothwell wrote: > > On Mon, 11 Jul 2022 10:05:45 +0200 Christian König > wrote: > > > > Am 11.07.22 um 04:47 schrieb Stephen Rothwell: > > > > > > Today's linux-next merge of the drm tree got a conflict in: > > > > > >drivers/gpu/drm/amd

Re: [Intel-gfx] linux-next: manual merge of the drm tree with the drm-misc-fixes tree

On Wed, 27 Jul 2022 at 12:55, Stephen Rothwell wrote: > > Hi all, > > On Mon, 18 Jul 2022 09:44:53 +1000 Stephen Rothwell > wrote: > > > > On Mon, 11 Jul 2022 10:05:45 +0200 Christian König > > wrote: > > > > > > Am 11.07.22 um 04:47 schrieb Stephen Rothwell: > > > > > > > > Today's linux-next

Re: [Intel-gfx] linux-next: manual merge of the drm tree with the drm-misc-fixes tree

Hi Dave, On Wed, 27 Jul 2022 13:24:45 +1000 Dave Airlie wrote: > > My assumption is I fix this on sending my -next tree to Linus with a > resolution I create at that time? > > Is there another option, we have this fixed in out drm-tip tree already. Sounds good, no problem. -- Cheers, Stephen

Re: [Intel-gfx] [PATCH] i915/pmu: Wire GuC backend to per-client busyness

On Fri, Jun 17, 2022 at 09:00:06AM +0100, Tvrtko Ursulin wrote: On 16/06/2022 23:13, Nerlige Ramappa, Umesh wrote: From: John Harrison GuC provides engine_id and last_switch_in ticks for an active context in the pphwsp. The context image provides a 32 bit total ticks which is the accumulated

Re: [Intel-gfx] [PATCH v2] drm/i915/hdmi: Prune modes that require HDMI2.1 FRL

> -Original Message- > From: Intel-gfx On Behalf Of Ankit > Nautiyal > Sent: Thursday, July 21, 2022 2:17 PM > To: intel-gfx@lists.freedesktop.org > Subject: [Intel-gfx] [PATCH v2] drm/i915/hdmi: Prune modes that require > HDMI2.1 > FRL > > HDMI2.1 requires some higher resolution vide