Re: [Intel-gfx] [PATCH] drm/i915/audio: do not set Maud/Naud values manually on KBL

>-Original Message- >From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of >Rodrigo Vivi >Sent: Wednesday, February 7, 2018 2:35 AM >To: Nikula, Jani >Cc: Zhang, Keqiao ; Liu, Alice ;

Re: [Intel-gfx] [PATCH v9 6/7] drm/i915/guc: Check the locking status of GuC WOPCM registers

On 02/09/2018 02:47 AM, Joonas Lahtinen wrote: +++ b/drivers/gpu/drm/i915/intel_guc_wopcm.c +static inline bool guc_wopcm_locked(struct intel_guc *guc) +{ + struct drm_i915_private *i915 = guc_to_i915(guc); + bool size_reg_locked = __reg_locked(i915, GUC_WOPCM_SIZE); + bool

Re: [Intel-gfx] [RFC 14/15] drm/i915: Use new IS_GEN range helpers

Quoting Ville Syrjälä (2018-02-09 15:12:58) > On Fri, Feb 09, 2018 at 04:48:43PM +0200, Ville Syrjälä wrote: > > On Fri, Feb 09, 2018 at 01:18:49PM +0200, Jani Nikula wrote: > > > On Thu, 08 Feb 2018, Ville Syrjälä wrote: > > > > On Thu, Feb 08, 2018 at 05:13:02PM

[Intel-gfx] [PATCH igt] igt/gem_exec_capture: MI_STORE_DWORD requires EXEC_SECURE + DRM_MASTER on ctg/ilk

On ctg/ilk, for whatever reason, MI_STORE_DWORD is a privileged operation so we must request a SECURE batch. Signed-off-by: Chris Wilson --- tests/gem_exec_capture.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/tests/gem_exec_capture.c

[Intel-gfx] ✗ Fi.CI.IGT: warning for igt/gem_exec_schedule: Limit smoketest to the desired engines

== Series Details == Series: igt/gem_exec_schedule: Limit smoketest to the desired engines URL : https://patchwork.freedesktop.org/series/38045/ State : warning == Summary == Test kms_vblank: Subgroup pipe-b-accuracy-idle: fail -> PASS (shard-snb) Test

Re: [Intel-gfx] [PATCH] drm/i915: Improve PSR activation timing

Quoting Andy Lutomirski (2018-02-09 17:55:38) > On Fri, Feb 9, 2018 at 7:39 AM, Rodrigo Vivi wrote: > > Rodrigo Vivi writes: > > So, I move the hacked scheduled to 10s and forced psr_activate 10ms > > after that and the result is this: > > > > > >

[Intel-gfx] ✓ Fi.CI.BAT: success for igt/gem_exec_schedule: Limit smoketest to the desired engines

== Series Details == Series: igt/gem_exec_schedule: Limit smoketest to the desired engines URL : https://patchwork.freedesktop.org/series/38045/ State : success == Summary == IGT patchset tested on top of latest successful build 8b9f68a13442c9307ef602cb9f0282e0c4ec43e2 igt/pm_rc6_residency:

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Call i915_pipe_update_start with uncore.lock held.

Quoting Maarten Lankhorst (2018-02-10 08:46:14) > Op 10-02-18 om 00:08 schreef James Ausmus: > > On Fri, Feb 09, 2018 at 10:54:02AM +0100, Maarten Lankhorst wrote: > >> +static u32 i915_get_vblank_counter(struct drm_device *dev, unsigned int > >> pipe) > >> +{ > >> +struct drm_i915_private

Re: [Intel-gfx] [PATCH v8 2/2] drm/i915/icl: Enhanced execution list support

Quoting Daniele Ceraolo Spurio (2018-02-09 23:28:04) > From: Thomas Daniel > > Enhanced Execlists is an upgraded version of execlists which supports > up to 8 ports. The lrcs to be submitted are written to a submit queue > (the ExecLists Submission Queue - ELSQ), which

[Intel-gfx] [PATCH igt] igt/gem_exec_schedule: Limit smoketest to the desired engines

We run the per-engine scheduling smoketests across all engines, the opposite of what was intended! Signed-off-by: Chris Wilson --- tests/gem_exec_schedule.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/tests/gem_exec_schedule.c

Re: [Intel-gfx] [PATCH v4 1/2] drm/i915/icl: new context descriptor support

Quoting Oscar Mateo (2018-02-09 23:48:38) > > > On 02/09/2018 03:28 PM, Daniele Ceraolo Spurio wrote: > > From: "Ceraolo Spurio, Daniele" > > > > Starting from Gen11 the context descriptor format has been updated in > > the HW. The hw_id field has been

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Call i915_pipe_update_start with uncore.lock held.

Op 10-02-18 om 00:08 schreef James Ausmus: > On Fri, Feb 09, 2018 at 10:54:02AM +0100, Maarten Lankhorst wrote: >> This requires being able to read the vblank counter with the >> uncore.lock already held. This is also a preparation for >> being able to run the entire vblank update sequence with >>

Re: [Intel-gfx] [PATCH 4/4] drm/i915: Disable dynamic setup of device_info->num_rings

Quoting Oscar Mateo (2018-02-09 23:46:31) > > On 02/09/2018 02:35 PM, Chris Wilson wrote: > > In order to allow the compiler to use a known constant number of > > available engines, disable modification of intel_device_static_info > > during engine bring up. Instead of trying to gracefully hide