[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/helpers: Make the suballocation manager drm generic. (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/helpers: Make the suballocation manager drm generic. (rev2) URL : https://patchwork.freedesktop.org/series/99713/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. -

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/helpers: Make the suballocation manager drm generic. (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/helpers: Make the suballocation manager drm generic. (rev2) URL : https://patchwork.freedesktop.org/series/99713/ State : warning == Summary == $ dim checkpatch origin/drm-tip 18b5ce2eb239 drm: Extract amdgpu_sa.c as a generic suballocation helper -:41:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix cursor coordinates on bigjoiner slave (rev3)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Fix cursor coordinates on bigjoiner slave (rev3) URL : https://patchwork.freedesktop.org/series/100154/ State : success == Summary == CI Bug Log - changes from CI_DRM_11277 -> Patchwork_22384 Summary

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Move bigjoiner refactoring (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Move bigjoiner refactoring (rev2) URL : https://patchwork.freedesktop.org/series/100195/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22383 Summary ---

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/psr: Set "SF Partial Frame Enable" also on full update (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915/psr: Set "SF Partial Frame Enable" also on full update (rev2) URL : https://patchwork.freedesktop.org/series/100633/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22382

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/wm: use REG_FIELD_PREP for PLANE_WM_BLOCKS_MASK (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915/wm: use REG_FIELD_PREP for PLANE_WM_BLOCKS_MASK (rev2) URL : https://patchwork.freedesktop.org/series/100626/ State : success == Summary == CI Bug Log - changes from CI_DRM_11274_full -> Patchwork_22369_full

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/psr: Set "SF Partial Frame Enable" also on full update (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915/psr: Set "SF Partial Frame Enable" also on full update (rev2) URL : https://patchwork.freedesktop.org/series/100633/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked

[Intel-gfx] ✓ Fi.CI.BAT: success for Use drm_clflush* instead of clflush (rev11)

2022-02-23 Thread Patchwork
== Series Details == Series: Use drm_clflush* instead of clflush (rev11) URL : https://patchwork.freedesktop.org/series/99450/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22381 Summary ---

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use drm_clflush* instead of clflush (rev11)

2022-02-23 Thread Patchwork
== Series Details == Series: Use drm_clflush* instead of clflush (rev11) URL : https://patchwork.freedesktop.org/series/99450/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev11)

2022-02-23 Thread Patchwork
== Series Details == Series: Use drm_clflush* instead of clflush (rev11) URL : https://patchwork.freedesktop.org/series/99450/ State : warning == Summary == $ dim checkpatch origin/drm-tip e3cc98e9d310 drm: Add arch arm64 for drm_clflush_virt_range -:18: WARNING:BAD_SIGN_OFF: Duplicate

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] HAX: drm/i915: Clarify vma lifetime (rev3)

2022-02-23 Thread Patchwork
== Series Details == Series: series starting with [1/2] HAX: drm/i915: Clarify vma lifetime (rev3) URL : https://patchwork.freedesktop.org/series/100593/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22380

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] HAX: drm/i915: Clarify vma lifetime (rev3)

2022-02-23 Thread Patchwork
== Series Details == Series: series starting with [1/2] HAX: drm/i915: Clarify vma lifetime (rev3) URL : https://patchwork.freedesktop.org/series/100593/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] HAX: drm/i915: Clarify vma lifetime (rev3)

2022-02-23 Thread Patchwork
== Series Details == Series: series starting with [1/2] HAX: drm/i915: Clarify vma lifetime (rev3) URL : https://patchwork.freedesktop.org/series/100593/ State : warning == Summary == $ dim checkpatch origin/drm-tip 2f07f02c4157 HAX: drm/i915: Clarify vma lifetime -:39:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: fix one mem leak in mmap_offset_attach() (rev3)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: fix one mem leak in mmap_offset_attach() (rev3) URL : https://patchwork.freedesktop.org/series/100532/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22378 Summary

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/adl-n: Add PCH Support for Alder Lake N (rev3)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915/adl-n: Add PCH Support for Alder Lake N (rev3) URL : https://patchwork.freedesktop.org/series/99413/ State : failure == Summary == Applying: drm/i915/adl-n: Add PCH Support for Alder Lake N Using index info to reconstruct a base tree... M

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dg1: Remove require_force_probe protection (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915/dg1: Remove require_force_probe protection (rev2) URL : https://patchwork.freedesktop.org/series/100601/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22377 Summary

[Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v2,1/7] drm/selftests: Move i915 buddy selftests into drm (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: series starting with [v2,1/7] drm/selftests: Move i915 buddy selftests into drm (rev2) URL : https://patchwork.freedesktop.org/series/100598/ State : failure == Summary == Applying: drm/selftests: Move i915 buddy selftests into drm Using index info to reconstruct

Re: [Intel-gfx] [PATCH 5/8] drm/i915/guc: Move lrc desc setup to where it is needed

2022-02-23 Thread Ceraolo Spurio, Daniele
On 2/23/2022 12:23 PM, John Harrison wrote: On 2/22/2022 17:12, Ceraolo Spurio, Daniele wrote: On 2/17/2022 3:52 PM, john.c.harri...@intel.com wrote: From: John Harrison The LRC descriptor was being initialised early on in the context registration sequence. It could then be determined

[Intel-gfx] ✗ Fi.CI.BAT: failure for Move #define wbvind_on_all_cpus (rev5)

2022-02-23 Thread Patchwork
== Series Details == Series: Move #define wbvind_on_all_cpus (rev5) URL : https://patchwork.freedesktop.org/series/1/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22375 Summary ---

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Move #define wbvind_on_all_cpus (rev5)

2022-02-23 Thread Patchwork
== Series Details == Series: Move #define wbvind_on_all_cpus (rev5) URL : https://patchwork.freedesktop.org/series/1/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Move #define wbvind_on_all_cpus (rev5)

2022-02-23 Thread Patchwork
== Series Details == Series: Move #define wbvind_on_all_cpus (rev5) URL : https://patchwork.freedesktop.org/series/1/ State : warning == Summary == $ dim checkpatch origin/drm-tip 2faaf6c21ed1 drm_cache: Add logic for wbvind_on_all_cpus -:13: WARNING:BAD_SIGN_OFF: Duplicate signature #13:

[Intel-gfx] ✗ Fi.CI.BAT: failure for sound/hda/hdac_i915: reduce the timeout for component binding (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: sound/hda/hdac_i915: reduce the timeout for component binding (rev2) URL : https://patchwork.freedesktop.org/series/100592/ State : failure == Summary == Applying: sound/hda/hdac_i915: reduce the timeout for component binding Using index info to reconstruct a base

Re: [Intel-gfx] [PATCH 5/6] drm/rcar_du: changes to rcar-du driver resulting from drm_writeback_connector structure changes

2022-02-23 Thread Abhinav Kumar
Hi Laurent Thanks for responding. On 2/21/2022 11:34 PM, Laurent Pinchart wrote: Hi Dmitry, On Tue, Feb 22, 2022 at 06:32:50AM +0300, Dmitry Baryshkov wrote: On Thu, 10 Feb 2022 at 07:59, Laurent Pinchart wrote: On Wed, Feb 09, 2022 at 05:40:29PM -0800, Abhinav Kumar wrote: Hi Laurent

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Move power well code to a separate file (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Move power well code to a separate file (rev2) URL : https://patchwork.freedesktop.org/series/100591/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22373 Summary

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Move power well code to a separate file (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Move power well code to a separate file (rev2) URL : https://patchwork.freedesktop.org/series/100591/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Use the memcpy_from_wc function from drm (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Use the memcpy_from_wc function from drm (rev2) URL : https://patchwork.freedesktop.org/series/100581/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22372 Summary

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Move power well code to a separate file (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Move power well code to a separate file (rev2) URL : https://patchwork.freedesktop.org/series/100591/ State : warning == Summary == $ dim checkpatch origin/drm-tip 27d38490b3c1 drm/i915: Fix the VDSC_PW2 power domain enum value 5c755c694d9d drm/i915:

[Intel-gfx] [PATCH] drm/i915/cdclk: Add cdclk check to atomic check

2022-02-23 Thread Anusha Srivatsa
Checking cdclk conditions during atomic check and preparing for commit phase so we can have atomic commit as simple as possible. Add the specific steps to be taken during cdclk changes, prepare for squashing, crawling and modeset scenarios. Rename functions intel_cdclk_can_squash() and

[Intel-gfx] [PULL] drm-intel-next

2022-02-23 Thread Rodrigo Vivi
Hi Dave and Daniel, Please notice that this pull request includes the drm-intel-gt-next (drm-intel-gt-next-2022-02-17) that didn't applied cleanly for you due to many conflicts generated by a big divergence from our drm-intel branches. So, please apply this one and ignore the one that Joonas had

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Use the memcpy_from_wc function from drm (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Use the memcpy_from_wc function from drm (rev2) URL : https://patchwork.freedesktop.org/series/100581/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Use the memcpy_from_wc function from drm (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Use the memcpy_from_wc function from drm (rev2) URL : https://patchwork.freedesktop.org/series/100581/ State : warning == Summary == $ dim checkpatch origin/drm-tip 00ae3268a143 drm: Relax alignment constraint for destination address a546db39ed55 drm:

[Intel-gfx] ✓ Fi.CI.BAT: success for Per client GPU utilisation (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: Per client GPU utilisation (rev2) URL : https://patchwork.freedesktop.org/series/100573/ State : success == Summary == CI Bug Log - changes from CI_DRM_11276 -> Patchwork_22370 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/tgl: Simply subplatform detection (rev3)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915/tgl: Simply subplatform detection (rev3) URL : https://patchwork.freedesktop.org/series/100517/ State : failure == Summary == Applying: drm/i915/tgl: Simply subplatform detection Using index info to reconstruct a base tree... M

[Intel-gfx] [CI 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v9)

2022-02-23 Thread Vivek Kasireddy
On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or more framebuffers/scanout buffers results in only one that is mappable/ fenceable. Therefore, pageflipping between these 2 FBs where only one is mappable/fenceable creates latencies large enough to miss alternate vblanks thereby

[Intel-gfx] [CI 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v4)

2022-02-23 Thread Vivek Kasireddy
This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given allocator. It replaces the for loop in drm_mm_insert_node_in_range() and can also be used by drm

[Intel-gfx] [CI 0/2] drm/mm: Add an iterator to optimally walk over holes suitable for an allocation

2022-02-23 Thread Vivek Kasireddy
The first patch is a drm core patch that replaces the for loop in drm_mm_insert_node_in_range() with the iterator and would not cause any functional changes. The second patch is a i915 driver specific patch that also uses the iterator but solves a different problem. v2: - Added a new patch to

[Intel-gfx] ✗ Fi.CI.DOCS: warning for Per client GPU utilisation (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: Per client GPU utilisation (rev2) URL : https://patchwork.freedesktop.org/series/100573/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/gem/i915_gem_context_types.h:417: warning: Function parameter or member

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Per client GPU utilisation (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: Per client GPU utilisation (rev2) URL : https://patchwork.freedesktop.org/series/100573/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Per client GPU utilisation (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: Per client GPU utilisation (rev2) URL : https://patchwork.freedesktop.org/series/100573/ State : warning == Summary == $ dim checkpatch origin/drm-tip 88a2b10167d3 drm/i915: Explicitly track DRM clients -:130: WARNING:FILE_PATH_CHANGES: added, moved or deleted

[Intel-gfx] [PATCH 1/1] drm/i915/dmc: Update DMC to v2.16 on ADL-P

2022-02-23 Thread Madhumitha Tolakanahalli Pradeep
Changes since v2.14: - Release Notes for v2.15 Fix for corruption issue when DC States are enabled. - Release Notes for v2.16 Fix for cases with flip queue and DC6v are enabled. Signed-off-by: Madhumitha Tolakanahalli Pradeep ---

[Intel-gfx] [PATCH 0/1] Bump DMC to v2.16 on ADL-P

2022-02-23 Thread Madhumitha Tolakanahalli Pradeep
Resending the patch to load the latest version of DMC on ADL-P as the previous one had false CI fail postives. Madhumitha Tolakanahalli Pradeep (1): drm/i915/dmc: Update DMC to v2.16 on ADL-P drivers/gpu/drm/i915/display/intel_dmc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[Intel-gfx] [PATCH v5] drm/i915/display/vrr: Reset VRR capable property on a long hpd

2022-02-23 Thread Manasi Navare
With some VRR panels, user can turn VRR ON/OFF on the fly from the panel settings. When VRR is turned OFF ,sends a long HPD to the driver clearing the Ignore MSA bit in the DPCD. Currently the driver parses that onevery HPD but fails to reset the corresponding VRR Capable Connector property.

Re: [Intel-gfx] [PATCH v2] drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-23 Thread Lucas De Marchi
On Wed, Feb 23, 2022 at 11:49:46AM -0800, Jose Souza wrote: Add check for zero usable stolen memory before calling drm_mm_init to support configurations where stolen memory exists but is fully reserved. Also skip memory test in cases that usable stolen is smaller than page size(amount mapped

Re: [Intel-gfx] [PATCH] drm/i915/dmc: Do not try loading wrong DMC version

2022-02-23 Thread Matt Roper
On Wed, Feb 23, 2022 at 01:09:33PM -0800, Lucas De Marchi wrote: > Checking by >= DISPLAY_VER(12) made sense when the support for Tiger > Lake was added. However now it only leads to wrong behavior when adding > more platforms since it's expected they either don't have DMC to load > or they have

[Intel-gfx] [PATCH] drm/i915/dmc: Do not try loading wrong DMC version

2022-02-23 Thread Lucas De Marchi
Checking by >= DISPLAY_VER(12) made sense when the support for Tiger Lake was added. However now it only leads to wrong behavior when adding more platforms since it's expected they either don't have DMC to load or they have their own blob. Logs from DG2 loading on a CFL host, without having a DMC

[Intel-gfx] [PATCH v2] drm/i915/display: Use unions per platform in intel_dpll_hw_state

2022-02-23 Thread José Roberto de Souza
This will save us a few bytes in intel_dpll_hw_state struct now and guarantee that it will not keep growing with each new platform. v2: - grouping skl and ICL+ combo (Imre) Cc: Imre Deak Cc: Ville Syrjälä Signed-off-by: José Roberto de Souza --- drivers/gpu/drm/i915/display/intel_display.c

Re: [Intel-gfx] [PULL] drm-intel-gt-next

2022-02-23 Thread Vivi, Rodrigo
On Tue, 2022-02-22 at 11:44 -0800, Lucas De Marchi wrote: > On Mon, Feb 21, 2022 at 11:21:35AM +0200, Jani Nikula wrote: > > On Mon, 21 Feb 2022, Dave Airlie wrote: > > > On Thu, 17 Feb 2022 at 20:26, Joonas Lahtinen > > > wrote: > > > > > > > > Hi Dave & Daniel, > > > > > > > > Here is the

Re: [Intel-gfx] [PATCH 5/8] drm/i915/guc: Move lrc desc setup to where it is needed

2022-02-23 Thread John Harrison
On 2/22/2022 17:12, Ceraolo Spurio, Daniele wrote: On 2/17/2022 3:52 PM, john.c.harri...@intel.com wrote: From: John Harrison The LRC descriptor was being initialised early on in the context registration sequence. It could then be determined that the actual registration needs to be delayed

Re: [Intel-gfx] [PATCH] drm/i915/display: Use unions per platform in intel_dpll_hw_state

2022-02-23 Thread Souza, Jose
On Wed, 2022-02-23 at 21:58 +0200, Imre Deak wrote: > On Tue, Feb 22, 2022 at 06:20:45AM -0800, José Roberto de Souza wrote: > [...] > > diff --git a/drivers/gpu/drm/i915/display/intel_dpll_mgr.h > > b/drivers/gpu/drm/i915/display/intel_dpll_mgr.h > > index ba2fdfce15792..4360e1c9266d8 100644 > >

Re: [Intel-gfx] [PATCH 2/3] drm/i915/gt: Make the heartbeat play nice with long pre-emption timeouts

2022-02-23 Thread John Harrison
On 2/23/2022 05:58, Tvrtko Ursulin wrote: On 23/02/2022 02:45, John Harrison wrote: On 2/22/2022 03:19, Tvrtko Ursulin wrote: On 18/02/2022 21:33, john.c.harri...@intel.com wrote: From: John Harrison Compute workloads are inherantly not pre-emptible for long periods on current hardware. As

Re: [Intel-gfx] [PATCH v2 12/13] drm/i915: Use bigjoiner_pipes more

2022-02-23 Thread Navare, Manasi
On Wed, Feb 23, 2022 at 03:13:14PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Replace the hardcoded 2 pipe assumptions when we're massaging > pipe_mode and the pipe_src rect to be suitable for bigjoiner. > Instead we can just count the number of pipes in the bitmask. > > v2:

Re: [Intel-gfx] [PATCH] drm/i915/display: Use unions per platform in intel_dpll_hw_state

2022-02-23 Thread Imre Deak
On Tue, Feb 22, 2022 at 06:20:45AM -0800, José Roberto de Souza wrote: [...] > diff --git a/drivers/gpu/drm/i915/display/intel_dpll_mgr.h > b/drivers/gpu/drm/i915/display/intel_dpll_mgr.h > index ba2fdfce15792..4360e1c9266d8 100644 > --- a/drivers/gpu/drm/i915/display/intel_dpll_mgr.h > +++

Re: [Intel-gfx] [PATCH v2 01/13] drm/i915: Avoid negative shift due to bigjoiner_pipes==0

2022-02-23 Thread Navare, Manasi
On Wed, Feb 23, 2022 at 03:13:03PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > bigjoiner_pipes==0 leads bigjoiner_master_pipe() to > do BIT(ffs(0)-1) which is undefined behaviour. The code should > actually still work fine since the only place we provoke > that is

[Intel-gfx] [PATCH 2/2] hda/i915: split the wait for the component binding

2022-02-23 Thread Ramalingam C
Split the wait for component binding from i915 in multiples of sysctl_hung_task_timeout_secs. This helps to avoid the possible kworker thread hung detection given below. <3>[ 60.946316] INFO: task kworker/11:1:104 blocked for more than 30 seconds. <3>[ 60.946479] Tainted: GW

[Intel-gfx] [PATCH 1/2] kernel/hung_task: Exporting sysctl_hung_task_timeout_secs

2022-02-23 Thread Ramalingam C
Exporting sysctl_hung_task_timeout_secs, to make it available for other kernel modules. Signed-off-by: Ramalingam C cc: Lucas De Marchi --- kernel/hung_task.c | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/hung_task.c b/kernel/hung_task.c index db59b6d4f0e7..01120265395d 100644 ---

[Intel-gfx] [PATCH 0/2] hda/i915: split wait for component binding

2022-02-23 Thread Ramalingam C
To avoid the intended wait being reported as kworker hung, split the wait for i915 component bind, in multiples of sysctl_hung_task_timeout_secs. To facilitate this we are exporting sysctl_hung_task_timeout_secs from kernel/hung_task.c for the kernel modules' use. Ramalingam C (2):

[Intel-gfx] [PATCH v2] drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-23 Thread José Roberto de Souza
Add check for zero usable stolen memory before calling drm_mm_init to support configurations where stolen memory exists but is fully reserved. Also skip memory test in cases that usable stolen is smaller than page size(amount mapped and used to test memory). v2: - skiping test if available

[Intel-gfx] [PATCH] drm/i915/display: Allow users to disable PSR2

2022-02-23 Thread José Roberto de Souza
Some users are suffering with PSR2 issues that are under debug or issues that were root caused to panel firmware, to make life of those users easier here adding a option to disable PSR1 with kernel parameter. Using the same enable_psr that is current used to turn PSR1 and PSR2 off or on and

[Intel-gfx] [PULL] drm-misc-fixes

2022-02-23 Thread Thomas Zimmermann
Hi Dave and Daniel, here's drm-misc-fixes for this week. Best regards Thomas drm-misc-fixes-2022-02-23: * edid: Always set RGB444 * imx/dcss: Select GEM CMA helpers * radeon: Fix some variables's type * vc4: Fix codec cleanup; Fix PM reference counting The following changes since commit

Re: [Intel-gfx] [PATCH] Revert "drm/i915/display/vrr: Reset VRR capable property on a long hpd"

2022-02-23 Thread Navare, Manasi
On Wed, Feb 23, 2022 at 10:29:16AM +0200, Jani Nikula wrote: > On Wed, 23 Feb 2022, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > This reverts commit 9bc34b4d0f3cb368241684cc5e0445d435dded44. > > > > Just oopses on most machines. > > > > Cc: Manasi Navare > > Cc: Jani Nikula > >

Re: [Intel-gfx] [PATCH] drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-23 Thread Lucas De Marchi
On Wed, Feb 23, 2022 at 11:12:56AM -0800, Jose Souza wrote: Add check for zero usable stolen memory before calling drm_mm_init to support configurations where stolen memory exists but is fully reserved. Also skip memory test in such case. Cc: Ville Syrjälä Cc: Daniele Ceraolo Spurio Cc:

[Intel-gfx] [PATCH] drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-23 Thread José Roberto de Souza
Add check for zero usable stolen memory before calling drm_mm_init to support configurations where stolen memory exists but is fully reserved. Also skip memory test in such case. Cc: Ville Syrjälä Cc: Daniele Ceraolo Spurio Cc: Lucas De Marchi Signed-off-by: José Roberto de Souza

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/wm: use REG_FIELD_PREP for PLANE_WM_BLOCKS_MASK (rev2)

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915/wm: use REG_FIELD_PREP for PLANE_WM_BLOCKS_MASK (rev2) URL : https://patchwork.freedesktop.org/series/100626/ State : success == Summary == CI Bug Log - changes from CI_DRM_11274 -> Patchwork_22369

Re: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/rps/tgl+: Remove RPS interrupt support

2022-02-23 Thread Souza, Jose
On Sat, 2022-02-19 at 17:35 +, Patchwork wrote: Patch Details Series: drm/i915/rps/tgl+: Remove RPS interrupt support URL:https://patchwork.freedesktop.org/series/100426/ State: success Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22336/index.html CI Bug Log -

Re: [Intel-gfx] [PATCH 1/3] drm/i915/guc: Limit scheduling properties to avoid overflow

2022-02-23 Thread John Harrison
On 2/23/2022 04:13, Tvrtko Ursulin wrote: On 23/02/2022 02:11, John Harrison wrote: On 2/22/2022 01:52, Tvrtko Ursulin wrote: On 18/02/2022 21:33, john.c.harri...@intel.com wrote: From: John Harrison GuC converts the pre-emption timeout and timeslice quantum values into clock ticks

Re: [Intel-gfx] [PATCH] drm/i915/rps/tgl+: Remove RPS interrupt support

2022-02-23 Thread Srivatsa, Anusha
> -Original Message- > From: Intel-gfx On Behalf Of José > Roberto de Souza > Sent: Friday, February 18, 2022 1:04 PM > To: intel-gfx@lists.freedesktop.org > Subject: [Intel-gfx] [PATCH] drm/i915/rps/tgl+: Remove RPS interrupt > support > > TGL+ and newer platforms don't support RPS up

Re: [Intel-gfx] [PATCH v11 1/6] drm: Add arch arm64 for drm_clflush_virt_range

2022-02-23 Thread kernel test robot
submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Michael-Cheng/Use-drm_clflush-instead-of-clflush/20220223-140110 base: git://anongit.freedesktop.org/drm/drm-tip drm-tip config: arm64-defconfig

Re: [Intel-gfx] [PATCH v2] drm/i915/psr: Set "SF Partial Frame Enable" also on full update

2022-02-23 Thread Souza, Jose
On Wed, 2022-02-23 at 14:48 +0200, Jouni Högander wrote: > Currently we are observing occasional screen flickering when > PSR2 selective fetch is enabled. More specifically glitch seems > to happen on full frame update when cursor moves to coords > x = -1 or y = -1. > > According to Bspec SF

Re: [Intel-gfx] [PATCH] drm/i915/dg2: Skip output init on PHY calibration failure

2022-02-23 Thread Lucas De Marchi
On Wed, Feb 23, 2022 at 08:54:21AM -0800, Matt Roper wrote: If one of our PHYs fails to complete calibration, we should skip the general initialization of the corresponding output. Most likely this is going to happen on outputs that don't actually exist on the board; in theory we should have

[Intel-gfx] [PATCH] drm/i915/dg2: Skip output init on PHY calibration failure

2022-02-23 Thread Matt Roper
If one of our PHYs fails to complete calibration, we should skip the general initialization of the corresponding output. Most likely this is going to happen on outputs that don't actually exist on the board; in theory we should have already decided to skip this output based on the VBT, but we

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/tgl: Simply subplatform detection (rev2)

2022-02-23 Thread Souza, Jose
On Wed, 2022-02-23 at 11:03 +, Patchwork wrote: Patch Details Series: drm/i915/tgl: Simply subplatform detection (rev2) URL:https://patchwork.freedesktop.org/series/100517/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22354/index.html CI Bug Log -

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

2022-02-23 Thread broonie
Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/display/intel_bw.c between commit: ec663bca9128f ("drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV") from the drm-intel-fixes tree and commit: 6d8ebef53c2cc ("drm/i915:

Re: [Intel-gfx] [PATCH v2 1/3] drm/mm: Ensure that the entry is not NULL before extracting rb_node

2022-02-23 Thread Tvrtko Ursulin
On 23/02/2022 04:35, Kasireddy, Vivek wrote: Hi Tvrtko, On 18/02/2022 03:47, Kasireddy, Vivek wrote: Hi Tvrtko, On 17/02/2022 07:50, Vivek Kasireddy wrote: While looking for next holes suitable for an allocation, although, it is highly unlikely, make sure that the

Re: [Intel-gfx] [PATCH 2/3] drm/i915/gt: Make the heartbeat play nice with long pre-emption timeouts

2022-02-23 Thread Tvrtko Ursulin
On 23/02/2022 02:45, John Harrison wrote: On 2/22/2022 03:19, Tvrtko Ursulin wrote: On 18/02/2022 21:33, john.c.harri...@intel.com wrote: From: John Harrison Compute workloads are inherantly not pre-emptible for long periods on current hardware. As a workaround for this, the pre-emption

[Intel-gfx] [PATCH] drm/i915: Check input parameter for NULL

2022-02-23 Thread Yongzhi Liu
[why] i915_gem_object_put_pages_phys() frees pages and standard pattern is to allow caller to not care if it's NULL or not. This will reduce burden on the callers to perform this check. [how] Fix it by adding Null check. Signed-off-by: Yongzhi Liu --- drivers/gpu/drm/i915/gem/i915_gem_phys.c |

[Intel-gfx] [PATCH][V2] drm/i915: make a handful of read-only arrays static const

2022-02-23 Thread Colin Ian King
Don't populate the read-only arrays on the stack but instead make them static const and signed 8 bit ints. Also makes the object code a little smaller. Reformat the statements to clear up checkpatch warning. Signed-off-by: Colin Ian King --- V2: Make arrays signed 8 bit integers as requested

[Intel-gfx] [PATCH 3/3] drm/radeon: Use the drm suballocation manager implementation.

2022-02-23 Thread Maarten Lankhorst
Use the generic suballocation helper lifted from amdgpu. Note that the generic suballocator only allows a single alignment, so we may waste a few more bytes for radeon_semaphore, shouldn't be a big deal, could be re-added if needed. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/Kconfig

[Intel-gfx] [PATCH 1/3] drm: Extract amdgpu_sa.c as a generic suballocation helper

2022-02-23 Thread Maarten Lankhorst
Suballocating a buffer object is something that is not driver generic, and is useful for other drivers as well. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/Kconfig| 4 + drivers/gpu/drm/Makefile | 3 + drivers/gpu/drm/drm_suballoc.c | 426

[Intel-gfx] [PATCH 2/3] drm/amd: Convert amdgpu to use suballocation helper.

2022-02-23 Thread Maarten Lankhorst
Now that the suballocation helper is generic, we can use it in amdgpu. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/Kconfig| 1 + drivers/gpu/drm/amd/amdgpu/amdgpu.h| 29 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c | 5 +-

[Intel-gfx] [PATCH 0/3] drm/helpers: Make the suballocation manager drm generic.

2022-02-23 Thread Maarten Lankhorst
Second version of the patch. I didn't fix the copyright (which ame up in the previous version), as I feel the original author should send a patch for that. I've made the suballocator into its own module, and did a cleanup pass on it. The suballocator is generic enough to be useful for any

[Intel-gfx] [v2] drm/i915: Fix cursor coordinates on bigjoiner slave

2022-02-23 Thread Lee Shawn C
From: Ville Syrjälä Adjust the cursor dst coordinates appripriately when it's on the bigjoiner slave pipe. intel_atomic_plane_check_clipping() already did this but with the cursor we discard those results (apart from uapi.visible and error checks) since the hardware will be doing the clipping

[Intel-gfx] ✓ Fi.CI.IGT: success for sound/hda/hdac_i915: reduce the timeout for component binding

2022-02-23 Thread Patchwork
== Series Details == Series: sound/hda/hdac_i915: reduce the timeout for component binding URL : https://patchwork.freedesktop.org/series/100592/ State : success == Summary == CI Bug Log - changes from CI_DRM_11268_full -> Patchwork_22358_full

Re: [Intel-gfx] [PATCH 0/7] drm/i915: Use the memcpy_from_wc function from drm

2022-02-23 Thread Das, Nirmoy
On 23/02/2022 12:08, Balasubramani Vivekanandan wrote: On 23.02.2022 10:02, Das, Nirmoy wrote: On 22/02/2022 15:51, Balasubramani Vivekanandan wrote: drm_memcpy_from_wc() performs fast copy from WC memory type using non-temporal instructions. Now there are two similar implementations of this

[Intel-gfx] [PATCH v2 13/13] drm/i915: Make the PIPESC rect relative to the entire bigjoiner area

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä When using bigjoiner it's useful to know the offset of each individual pipe in the whole set of joined pipes. Let's include that information in our PIPESRC rectangle. With this we can make the plane clipping code blissfully unaware of bigjoiner usage, as all we have to do is

[Intel-gfx] [PATCH v2 12/13] drm/i915: Use bigjoiner_pipes more

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Replace the hardcoded 2 pipe assumptions when we're massaging pipe_mode and the pipe_src rect to be suitable for bigjoiner. Instead we can just count the number of pipes in the bitmask. v2: Introduce intel_bigjoiner_num_pipes() Signed-off-by: Ville Syrjälä ---

[Intel-gfx] [PATCH v2 10/13] drm/i915: Start tracking PIPESRC as a drm_rect

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Instead of just having the pipe_src_{w,h} let's use a full drm_rect for it. This will be particularly useful to astract away some bigjoiner details. v2: No hweight() stuff yet Signed-off-by: Ville Syrjälä --- .../gpu/drm/i915/display/intel_atomic_plane.c | 15 ++--

[Intel-gfx] [PATCH v2 11/13] drm/i915: Eliminate bigjoiner boolean

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Since we now have the bigjoiner_pipes bitmask the boolean is redundant. Get rid of it. Also, populating bigjoiner_pipes already during encoder->compute_config() allows us to use it much earlier during the state calculation as well. The initial aim is to use it in

[Intel-gfx] [PATCH v2 09/13] drm/i915: Fix MSO vs. bigjoiner timings confusion

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä When calculating pipe_mode and when doing readout we need to order our steps correctly. 1. We start with adjusted_mode crtc timings being populated with the transcoder timings (either via readout or compute_config(). These will be per-segment for MSO. 2. For all other

[Intel-gfx] [PATCH v2 08/13] drm/i915: Extract intel_crtc_compute_pipe_mode()

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Pull intel_crtc_compute_pipe_mode() out from intel_crtc_compute_config(). Since it's semi related we'll suck in the max dotclock/double wide checks in as well. And we'll pimp the debugs while at it. Reviewed-by: Manasi Navare Signed-off-by: Ville Syrjälä ---

[Intel-gfx] [PATCH v2 07/13] drm/i915: Extract intel_crtc_compute_pipe_src()

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä intel_crtc_compute_config() doesn't really tell a unified story. Let's chunk it up into pieces. We'll start with intel_crtc_compute_pipe_src(). Reviewed-by: Manasi Navare Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_display.c | 62

[Intel-gfx] [PATCH v2 06/13] drm/i915: Extract intel_bigjoiner_adjust_timings()

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Deduplicate the code to convert the full timings to per-pipe timings for bigjoiner usage. Reviewed-by: Manasi Navare Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_display.c | 41 +--- 1 file changed, 18 insertions(+), 23 deletions(-)

[Intel-gfx] [PATCH v2 05/13] drm/i915: Extract intel_splitter_adjust_timings()

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Let's not replicate the same piece of code to expand the MSO segment timings to full width in many places. Pull it into a helper Reviewed-by: Jani Nikula Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_display.c | 54 ++-- 1 file

[Intel-gfx] [PATCH v2 04/13] drm/i915: Rename variables in intel_crtc_compute_config()

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Do the s/dev_priv/i915/ and s/pipe_config/crtc_state/ renames to intel_crtc_compute_config(). I want to start splitting this up a bit and doing the renames now avoids spreading these old nameing conventions elsewhere. No functional changes. Reviewed-by: Manasi Navare

[Intel-gfx] [PATCH v2 02/13] drm/i915: Fix cursor coordinates on bigjoiner slave

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Adjust the cursor dst coordinates appripriately when it's on the bigjoiner slave pipe. intel_atomic_plane_check_clipping() already did this but with the cursor we discard those results (apart from uapi.visible and error checks) since the hardware will be doing the clipping

[Intel-gfx] [PATCH v2 03/13] drm/i915: Remove nop bigjoiner state copy

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä We just copied over the whole master crtc state, including cpu_transcoder+has_audio. No need to copy those again. Also get rid of the unhelpful comment. Reviewed-by: Ankit Nautiyal Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_display.c | 3 --- 1

[Intel-gfx] [PATCH v2 01/13] drm/i915: Avoid negative shift due to bigjoiner_pipes==0

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä bigjoiner_pipes==0 leads bigjoiner_master_pipe() to do BIT(ffs(0)-1) which is undefined behaviour. The code should actually still work fine since the only place we provoke that is intel_crtc_bigjoiner_slave_pipes() and it'll bitwise AND the result with 0, so doesn't really

[Intel-gfx] [PATCH v2 00/13] drm/i915: Move bigjoiner refactoring

2022-02-23 Thread Ville Syrjala
From: Ville Syrjälä Rebased version of the latest bigjoiner stuff. Also shuffled the hweight() stuff around a bit, and added patch to fix an UBSAN issue. Ville Syrjälä (13): drm/i915: Avoid negative shift due to bigjoiner_pipes==0 drm/i915: Fix cursor coordinates on bigjoiner slave

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Use the memcpy_from_wc function from drm

2022-02-23 Thread Patchwork
== Series Details == Series: drm/i915: Use the memcpy_from_wc function from drm URL : https://patchwork.freedesktop.org/series/100581/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11268_full -> Patchwork_22356_full

[Intel-gfx] [PULL] drm-misc-next

2022-02-23 Thread Maarten Lankhorst
Hi Dave, After few missing, here's the final pull req for -next in v5.18 drm-misc-next-2022-02-23: drm-misc-next for v5.18: UAPI Changes: Cross-subsystem Changes: - Split out panel-lvds and lvds dt bindings . - Put yes/no on/off disabled/enabled strings in linux/string_helpers.h and use it

[Intel-gfx] [PATCH v2] drm/i915/psr: Set "SF Partial Frame Enable" also on full update

2022-02-23 Thread Jouni Högander
Currently we are observing occasional screen flickering when PSR2 selective fetch is enabled. More specifically glitch seems to happen on full frame update when cursor moves to coords x = -1 or y = -1. According to Bspec SF Single full frame should not be set if SF Partial Frame Enable is not

  1   2   >