[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Skip waking the device to service pwrite (rev2)

2017-10-19 Thread Patchwork
== Series Details == Series: drm/i915: Skip waking the device to service pwrite (rev2) URL : https://patchwork.freedesktop.org/series/29560/ State : success == Summary == Series 29560v2 drm/i915: Skip waking the device to service pwrite https://patchwork.freedesktop.org/api/1.0/series/29560/re

Re: [Intel-gfx] [CI] drm/i915: Convert timers to use timer_setup()

2017-10-19 Thread Jani Nikula
On Tue, 17 Oct 2017, Joonas Lahtinen wrote: > From: Kees Cook > > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: Daniel Vetter > Cc: Jani Nik

Re: [Intel-gfx] [RFC 1/2] drm/i915: Add connector property to force bpc

2017-10-19 Thread Daniel Vetter
On Wed, Oct 18, 2017 at 03:29:48PM -0700, Sripada, Radhakrishna wrote: > Currently the user space does not have a way to force the bpc. The > default bpc to be programmed is decided by the driver and is run > against connector limitations. Creating a new property for the userspace > to recommend a

Re: [Intel-gfx] [PATCH 06/11] drm/i915/guc: Only release GuC log object during submission_fini

2017-10-19 Thread Tvrtko Ursulin
On 18/10/2017 17:04, Sagar Arun Kamble wrote: On 10/18/2017 6:42 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:46, Sagar Arun Kamble wrote: GuC log runtime/relay channel data is released during i915 unregister, So only GuC log vma needs to be released during submission_fini. Signed-off-by: Saga

Re: [Intel-gfx] [PATCH 1/8] drm/i915: Clean up some cdclk switch statements

2017-10-19 Thread Mika Kahola
On Wed, 2017-10-18 at 23:48 +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Redo some switch statements in the cdclk code to use a common > fall through for the default case. Makes everything look a bit > more uniform > > Cc: Mika Kahola > Cc: Manasi Navare > Cc: Rodrigo Vivi Reviewed-b

Re: [Intel-gfx] [PATCH 04/11] drm/i915/guc: Sanitize module parameter guc_log_level

2017-10-19 Thread Tvrtko Ursulin
On 18/10/2017 16:50, Sagar Arun Kamble wrote: On 10/18/2017 6:29 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:46, Sagar Arun Kamble wrote: Parameter guc_log_level needs to be sanitized based on GuC support and enable_guc_loading parameter since it depends on them like enable_guc_submission. Thi

Re: [Intel-gfx] [PATCH i-g-t] tests/kms_fbcon_fbt: Report fbc_status on error

2017-10-19 Thread Daniel Vetter
On Wed, Oct 18, 2017 at 11:39:15PM -0200, Gabriel Krisman Bertazi wrote: > knowing the assertion triggered on wait_until_enabled() is not that > useful without knowing what exactly caused the failure. It might be an > user error, like too little stolen memory by the bios, or an actual > issue in t

Re: [Intel-gfx] [PATCH igt] igt/prime_mmap_coherency: Remove manual gem_sync() calls

2017-10-19 Thread Daniel Vetter
On Thu, Oct 19, 2017 at 07:23:07AM +0100, Chris Wilson wrote: > Emphasize that we want to test synchronisation using the dmabuf API > (prime_sync_start, prime_sync_end) and so drop the manual > synchronisation using the GEM API (gem_sync). > > Signed-off-by: Chris Wilson Assuming CI approves too

[Intel-gfx] ✓ Fi.CI.BAT: success for igt/prime_mmap_coherency: Remove manual gem_sync() calls

2017-10-19 Thread Patchwork
== Series Details == Series: igt/prime_mmap_coherency: Remove manual gem_sync() calls URL : https://patchwork.freedesktop.org/series/32272/ State : success == Summary == IGT patchset tested on top of latest successful build d4a4fbec0c079c7bec7fa6a2c756eea02314799e igt/prime_mmap_coherency: Cal

Re: [Intel-gfx] [CI] drm/i915: Skip waking the device to service pwrite

2017-10-19 Thread Daniel Vetter
On Thu, Oct 19, 2017 at 07:37:33AM +0100, Chris Wilson wrote: > If the device is in runtime suspend, resuming takes time and reduces our > powersaving. If this was for a small write into an object, that resume > will take longer than any savings in using the indirect GGTT access to > avoid the cpu

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [CI,1/4] lib: Add DROP_IDLE

2017-10-19 Thread Patchwork
== Series Details == Series: series starting with [CI,1/4] lib: Add DROP_IDLE URL : https://patchwork.freedesktop.org/series/32268/ State : success == Summary == Test kms_flip: Subgroup wf_vblank-vs-modeset: dmesg-warn -> PASS (shard-hsw) fdo#102614 Subgro

[Intel-gfx] ✓ Fi.CI.BAT: success for tests/kms_plane_lowres: Rework tests to work without fbcon. (rev3)

2017-10-19 Thread Patchwork
== Series Details == Series: tests/kms_plane_lowres: Rework tests to work without fbcon. (rev3) URL : https://patchwork.freedesktop.org/series/32016/ State : success == Summary == IGT patchset tested on top of latest successful build d4a4fbec0c079c7bec7fa6a2c756eea02314799e igt/prime_mmap_cohe

Re: [Intel-gfx] [PATCH i-g-t 1/4] lib/igt_vgem: extract vgem_create_and_import

2017-10-19 Thread Chris Wilson
Quoting Daniele Ceraolo Spurio (2017-10-12 23:30:41) > The same code to create and import a vgem object is used in a couple of > places and a couple more are coming up in the next patches so extract > the code into a common function > > Signed-off-by: Daniele Ceraolo Spurio > --- > lib/igt_dummy

Re: [Intel-gfx] [PATCH i-g-t 2/4] tests/gem_pread: test reads from a bo not backed by struct page

2017-10-19 Thread Chris Wilson
Quoting Daniele Ceraolo Spurio (2017-10-12 23:30:42) > Using an imported vgem bo we can test reads from an object not backed > by struct page. These reads use different paths in the kernel. > > While at it, extract some common code in an helper function and fix the > src vs dst naming (they are th

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Skip waking the device to service pwrite (rev2)

2017-10-19 Thread Patchwork
== Series Details == Series: drm/i915: Skip waking the device to service pwrite (rev2) URL : https://patchwork.freedesktop.org/series/29560/ State : success == Summary == Test perf: Subgroup polling: pass -> FAIL (shard-hsw) fdo#102252 Subgroup oa-ex

[Intel-gfx] [PATCH resend v3 1/3] drm/i915: Fix false-positive assert_rpm_wakelock_held in i915_pmic_bus_access_notifier

2017-10-19 Thread Hans de Goede
assert_rpm_wakelock_held is triggered from i915_pmic_bus_access_notifier even though it gets unregistered on (runtime) suspend, this is caused by a race happening under the following circumstances: intel_runtime_pm_put does: atomic_dec(&dev_priv->pm.wakeref_count); pm_runtime_mark_last_bus

[Intel-gfx] [PATCH resend v3 2/3] drm/i915: Re-register PMIC bus access notifier on runtime resume

2017-10-19 Thread Hans de Goede
intel_uncore_suspend() unregisters the uncore code's PMIC bus access notifier and gets called on both normal and runtime suspend. intel_uncore_resume_early() re-registers the notifier, but only on normal resume. Add a new intel_uncore_runtime_resume() function which only re-registers the notifier

[Intel-gfx] [PATCH resend v3 3/3] drm/i915: Call uncore_suspend before platform suspend handlers

2017-10-19 Thread Hans de Goede
Quoting Ville: "the forcewake timer might still be active until the uncore suspend, and having active forcewakes while we've already told the GT wake stuff to stop acting normally doesn't seem quite right to me." Reported-by: Ville Syrjälä Suggested-by: Imre Deak Signed-off-by: Hans de Goede Re

[Intel-gfx] [PATCH resend v3 0/3] drm/i915: Misc. PMIC bus access notifier fixes

2017-10-19 Thread Hans de Goede
Hi All, Here is a resend of the first 3 of the 4 patches in my Misc. PMIC bus access notifier fixes series. I'm leaving out the 4th patch this time, because that includes some changes to the iosf_mbi code under arch/x86 and that has been blocking this series from getting upstream sofar. I will se

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Misc. PMIC bus access notifier fixes

2017-10-19 Thread Patchwork
== Series Details == Series: drm/i915: Misc. PMIC bus access notifier fixes URL : https://patchwork.freedesktop.org/series/32274/ State : success == Summary == Series 32274v1 drm/i915: Misc. PMIC bus access notifier fixes https://patchwork.freedesktop.org/api/1.0/series/32274/revisions/1/mbox/

Re: [Intel-gfx] [PATCH i-g-t v2 0/6] Drop tests for object creation from stolen

2017-10-19 Thread Chris Wilson
Quoting Joonas Lahtinen (2017-10-13 12:22:26) > On Thu, 2017-10-12 at 15:29 -0700, Daniele Ceraolo Spurio wrote: > > Respin with review fixes for meson build and gem_concurrent_all. > > I'll send the new tests for pread/pwrite suggested by Chris as a > > separated series as they depend on the other

Re: [Intel-gfx] [PATCH i-g-t v2 02/14] lib/igt_kms: Rework plane properties to be more atomic, v5.

2017-10-19 Thread Mika Kahola
On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: > In the future I want to allow tests to commit more properties, > but for this to work I have to fix all properties to work better > with atomic commit. Instead of special casing each > property make a bitmask for all property changed fla

[Intel-gfx] [PATCH] hax: moar padding

2017-10-19 Thread Maarten Lankhorst
Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/i915/intel_drv.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h index a05ab3a1ab27..bfd743892458 100644 --- a/drivers/gpu/drm/i915/intel_drv.h +++ b/drivers/gpu/drm/i91

Re: [Intel-gfx] [PATCH i-g-t v2 02/14] lib/igt_kms: Rework plane properties to be more atomic, v5.

2017-10-19 Thread Maarten Lankhorst
Op 19-10-17 om 11:08 schreef Mika Kahola: > On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: >> In the future I want to allow tests to commit more properties, >> but for this to work I have to fix all properties to work better >> with atomic commit. Instead of special casing each >> prop

[Intel-gfx] ✓ Fi.CI.BAT: success for hax: moar padding

2017-10-19 Thread Patchwork
== Series Details == Series: hax: moar padding URL : https://patchwork.freedesktop.org/series/32278/ State : success == Summary == Series 32278v1 hax: moar padding https://patchwork.freedesktop.org/api/1.0/series/32278/revisions/1/mbox/ Test chamelium: Subgroup dp-crc-fast:

[Intel-gfx] [PATCH i-g-t] tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Daniel Vetter
CI gets upset about it resulting in an incomplete, let's skip it until that's fixed to avoid havoc in the CI farm. Of course this should/will be reverted as soon as we have a fix (similar to how we dealt with the snb-dies-in-blt-hangs issue). Cc: Joonas Lahtinen Cc: Chris Wilson Cc: "Lofstedt, M

[Intel-gfx] ✓ Fi.CI.IGT: success for tests/kms_plane_lowres: Rework tests to work without fbcon. (rev3)

2017-10-19 Thread Patchwork
== Series Details == Series: tests/kms_plane_lowres: Rework tests to work without fbcon. (rev3) URL : https://patchwork.freedesktop.org/series/32016/ State : success == Summary == Test kms_setmode: Subgroup basic: fail -> PASS (shard-hsw) fdo#99912 Test kms_

Re: [Intel-gfx] [PATCH i-g-t] tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Daniel Vetter
On Thu, Oct 19, 2017 at 11:51:51AM +0200, Daniel Vetter wrote: > CI gets upset about it resulting in an incomplete, let's skip it until > that's fixed to avoid havoc in the CI farm. Of course this should/will > be reverted as soon as we have a fix (similar to how we dealt with the > snb-dies-in-blt

Re: [Intel-gfx] [CI] drm/i915: Skip waking the device to service pwrite

2017-10-19 Thread Tvrtko Ursulin
On 19/10/2017 07:37, Chris Wilson wrote: If the device is in runtime suspend, resuming takes time and reduces our powersaving. If this was for a small write into an object, that resume will take longer than any savings in using the indirect GGTT access to avoid the cpu cache. Commit talks abou

Re: [Intel-gfx] [PATCH 07/11] drm/i915/guc: Grab RPM wakelock while disabling GuC interrupts

2017-10-19 Thread Tvrtko Ursulin
On 18/10/2017 07:46, Sagar Arun Kamble wrote: Disabling GuC interrupts involves access to GuC IRQ control registers hence ensure device is RPM awake. v2: Add comment about need to synchronize flush work and log runtime destroy Signed-off-by: Sagar Arun Kamble Cc: Michal Wajdeczko Cc: Da

[Intel-gfx] ✗ Fi.CI.BAT: failure for tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Patchwork
== Series Details == Series: tests/gem_eio: Skip in-flight-suspend on snb URL : https://patchwork.freedesktop.org/series/32280/ State : failure == Summary == IGT patchset tested on top of latest successful build abc08cba366a64a07f7f4deb167ae7d6ae059958 lib: Free all internal buffers before me

Re: [Intel-gfx] [PATCH 08/11] drm/i915/guc: Add client support to enable/disable GuC interrupts

2017-10-19 Thread Tvrtko Ursulin
On 18/10/2017 07:46, Sagar Arun Kamble wrote: This patch adds support to enable/disable GuC interrupts for different features without impacting others needs. Currently GuC log capture and CT buffer receive mechanisms use the GuC interrupts. GuC interrupts are currently enabled and disabled in di

Re: [Intel-gfx] [CI] drm/i915: Skip waking the device to service pwrite

2017-10-19 Thread Chris Wilson
Quoting Tvrtko Ursulin (2017-10-19 11:02:05) > > On 19/10/2017 07:37, Chris Wilson wrote: > > If the device is in runtime suspend, resuming takes time and reduces our > > powersaving. If this was for a small write into an object, that resume > > will take longer than any savings in using the indir

Re: [Intel-gfx] [PATCH 09/11] drm/i915/guc: Fix GuC interrupts disabling with Logging

2017-10-19 Thread Tvrtko Ursulin
On 18/10/2017 07:47, Sagar Arun Kamble wrote: With guc_log_unregister disabling runtime logging and interrupts there is no need to disable interrupts during uc_fini_hw hence it is removed. With GuC CT buffer mechanism, interrupt disabling can be added at a point where CT mechanism ceases. Signe

[Intel-gfx] "BUG: unable to handle kernel NULL pointer dereference at 0000000000000070" in [i915] reset_common_ring

2017-10-19 Thread Bjørn Mork
Hello, I get these Oopses from time to time, but unfortunately(?) not often enough to be anywhere near reproducible. But they seem to be related to whatever activites my laptop/X-server/driver/gpu/screen is doing while I'm not present. The oops happens when I'm away for a while. So I guess it mi

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Chris Wilson
Ah, domains. It is a real bug, but the quickest way to paper over it is to s/TEST_DEVICES/TEST_NONE/ (that way we still have the test in arguably a more realistic mode), we have other reset tests that also trigger the death. The bug tells us reset on snb is unreliable (writing to GDRST causes a ma

Re: [Intel-gfx] [PATCH 10/11] drm/i915/guc: Skip interrupt enabling if logging is already enabled

2017-10-19 Thread Tvrtko Ursulin
On 18/10/2017 07:47, Sagar Arun Kamble wrote: To balance the GuC interrupt references we don't allow enabling interrupts If logging was enabled earlier with different verbosity. I've noticed in a couple of your previous commits words in the middle of sentences starting with upper case which i

Re: [Intel-gfx] "BUG: unable to handle kernel NULL pointer dereference at 0000000000000070" in [i915] reset_common_ring

2017-10-19 Thread Bjørn Mork
Here's another one I had lying around in pstore. Note that this one has slighty older kernel and BIOS version, possibly eliminating a couple of variables. <6>[18285.732012] [drm] GPU HANG: ecode 9:0:0xfffe, in Xorg [842], reason: Hang on render ring, action: reset <6>[18285.732024] [drm] GP

Re: [Intel-gfx] [PATCH i-g-t v2 03/14] lib/igt_kms: Rework pipe properties to be more atomic, v7.

2017-10-19 Thread Mika Kahola
Reviewed-by: Mika Kahola On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: > In the future I want to allow tests to commit more properties, > but for this to work I have to fix all properties to work better > with atomic commit. Instead of special casing each > property make a bitmask f

Re: [Intel-gfx] "BUG: unable to handle kernel NULL pointer dereference at 0000000000000070" in [i915] reset_common_ring

2017-10-19 Thread Chris Wilson
Quoting Bjørn Mork (2017-10-19 11:24:57) > Hello, > > I get these Oopses from time to time, but unfortunately(?) not often > enough to be anywhere near reproducible. But they seem to be related to > whatever activites my laptop/X-server/driver/gpu/screen is doing while > I'm not present. The oops

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: Misc. PMIC bus access notifier fixes

2017-10-19 Thread Patchwork
== Series Details == Series: drm/i915: Misc. PMIC bus access notifier fixes URL : https://patchwork.freedesktop.org/series/32274/ State : warning == Summary == Test perf: Subgroup oa-exponents: fail -> PASS (shard-hsw) fdo#102254 Test kms_flip: Subgr

Re: [Intel-gfx] [PATCH v2 06/10] drm/i915: Pass encoder type to cnl_ddi_vswing_sequence() explicitly

2017-10-19 Thread Ville Syrjälä
On Wed, Oct 18, 2017 at 02:11:46PM -0700, Manasi Navare wrote: > On Mon, Oct 16, 2017 at 05:57:01PM +0300, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > encoder->type is unreliable for DP/HDMI, so pass it in explicity into > > cnl_ddi_vswing_sequence(). This matches what we do for BXT. > >

Re: [Intel-gfx] "BUG: unable to handle kernel NULL pointer dereference at 0000000000000070" in [i915] reset_common_ring

2017-10-19 Thread Bjørn Mork
Chris Wilson writes: > Quoting Bjørn Mork (2017-10-19 11:24:57) >> Hello, >> >> I get these Oopses from time to time, but unfortunately(?) not often >> enough to be anywhere near reproducible. But they seem to be related to >> whatever activites my laptop/X-server/driver/gpu/screen is doing whi

Re: [Intel-gfx] [PATCH 7/8] drm/i915: Use cdclk_state->voltage on CNL

2017-10-19 Thread Ville Syrjälä
On Wed, Oct 18, 2017 at 02:50:59PM -0700, Rodrigo Vivi wrote: > On Wed, Oct 18, 2017 at 08:48:24PM +, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Track the system agent voltage we request from pcode in the cdclk state > > on CNL. Annoyingly we can't actually read out the current valu

[Intel-gfx] [PATCH] drm: Hold idr_mutex for _drm_lease_revoke

2017-10-19 Thread Chris Wilson
_drm_lease_revoke() requires it callers to hold the idr_mutex, but its only caller did not. Every device release would then trigger: WARNING: CPU: 7 PID: 4169 at drivers/gpu/drm/drm_lease.c:313 _drm_lease_revoke+0x12c/0x140 Modules linked in: vgem snd_hda_codec_hdmi snd_hda_codec_generic i915

Re: [Intel-gfx] "BUG: unable to handle kernel NULL pointer dereference at 0000000000000070" in [i915] reset_common_ring

2017-10-19 Thread Bjørn Mork
Bjørn Mork writes: > Chris Wilson writes: > >> and at a guess >> intel_iommu=igfx_off to avoid the hangs in the first place. > > Thanks for the tip. I'll try that My memory is more than a bit flakey, but this did eventually ring a bell.,. And googling I see that I have tried that tip before wit

Re: [Intel-gfx] "BUG: unable to handle kernel NULL pointer dereference at 0000000000000070" in [i915] reset_common_ring

2017-10-19 Thread Chris Wilson
Quoting Bjørn Mork (2017-10-19 11:43:17) > Chris Wilson writes: > > > Quoting Bjørn Mork (2017-10-19 11:24:57) > >> Hello, > >> > >> I get these Oopses from time to time, but unfortunately(?) not often > >> enough to be anywhere near reproducible. But they seem to be related to > >> whatever ac

Re: [Intel-gfx] [PATCH i-g-t v2 04/14] lib/igt_kms: Allow setting any plane property through the universal path

2017-10-19 Thread Mika Kahola
Reviewed-by: Mika Kahola On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: > Blacklist some explicit atomic properties. We could theoretically set > them but that's not what the legacy path is for. :) > > When adding new properties, this means we could test those through > the legacy c

Re: [Intel-gfx] [PATCH 7/8] drm/i915: Use cdclk_state->voltage on CNL

2017-10-19 Thread Mika Kahola
On Thu, 2017-10-19 at 13:48 +0300, Ville Syrjälä wrote: > On Wed, Oct 18, 2017 at 02:50:59PM -0700, Rodrigo Vivi wrote: > > > > On Wed, Oct 18, 2017 at 08:48:24PM +, Ville Syrjala wrote: > > > > > > From: Ville Syrjälä > > > > > > Track the system agent voltage we request from pcode in the

Re: [Intel-gfx] [PATCH 11/11] drm/i915/guc: Restore GuC interrupts across suspend/reset if enabled

2017-10-19 Thread Tvrtko Ursulin
On 18/10/2017 07:47, Sagar Arun Kamble wrote: In order to override the disable/enable control of GuC interrupts during suspend/reset cycle we are creating two new functions suspend/restore guc_interrupts which check if interrupts were enabled and disable them on suspend and enable them on resume

Re: [Intel-gfx] "BUG: unable to handle kernel NULL pointer dereference at 0000000000000070" in [i915] reset_common_ring

2017-10-19 Thread Chris Wilson
Quoting Bjørn Mork (2017-10-19 11:55:18) > Bjørn Mork writes: > > Chris Wilson writes: > > > >> and at a guess > >> intel_iommu=igfx_off to avoid the hangs in the first place. > > > > Thanks for the tip. I'll try that > > My memory is more than a bit flakey, but this did eventually ring a > bell

Re: [Intel-gfx] [CI] drm/i915: Skip waking the device to service pwrite

2017-10-19 Thread Tvrtko Ursulin
On 19/10/2017 11:19, Chris Wilson wrote: Quoting Tvrtko Ursulin (2017-10-19 11:02:05) On 19/10/2017 07:37, Chris Wilson wrote: If the device is in runtime suspend, resuming takes time and reduces our powersaving. If this was for a small write into an object, that resume will take longer than

[Intel-gfx] ✗ Fi.CI.IGT: warning for hax: moar padding

2017-10-19 Thread Patchwork
== Series Details == Series: hax: moar padding URL : https://patchwork.freedesktop.org/series/32278/ State : warning == Summary == Test perf: Subgroup oa-exponents: fail -> PASS (shard-hsw) fdo#102254 Test kms_busy: Subgroup extended-modeset-hang-new

[Intel-gfx] [PATCH i-g-t] tests/kms_concurrent: Fix testcase fails.

2017-10-19 Thread Maarten Lankhorst
igt_pipe_refresh was added for the forked helper, we could just call it from the fork to prevent races against MODE_ID. The static 1024x768 mode is allocated on the stack and returned, which will result in a garbage mode. Make the fallback mode global to prevent this. igt_output_set_pipe is unnee

[Intel-gfx] [PATCH v5 1/2] x86 / i915 iosf_mbi / PMIC bus access fixes

2017-10-19 Thread Hans de Goede
Hi All, Here is a split-up version of my "drm/i915: Acquire PUNIT->PMIC bus for intel_uncore_forcewake_reset()" patch, this time with the arch/x86/platform/intel/iosf_mbi.c split out into a separate patch. Since the iosf_mbi changes are fairly isolated, ideally this entire series would go upstrea

[Intel-gfx] [PATCH v5 1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister

2017-10-19 Thread Hans de Goede
For race free unregistration drivers may need to acquire PMIC bus access through iosf_mbi_punit_acquire() and then (un)register the notifier without dropping the lock. This commit adds an unlocked variant of iosf_mbi_unregister_pmic_bus_access_notifier for this use case. Signed-off-by: Hans de Go

[Intel-gfx] [PATCH v5 2/2] drm/i915: Acquire PUNIT->PMIC bus for intel_uncore_forcewake_reset()

2017-10-19 Thread Hans de Goede
intel_uncore_forcewake_reset() does forcewake puts and gets as such we need to make sure that no-one tries to access the PUNIT->PMIC bus (on systems where this bus is shared) while it runs, otherwise bad things happen. Normally this is taken care of by the i915_pmic_bus_access_notifier() which doe

Re: [Intel-gfx] [PATCH i-g-t v2 06/14] lib/igt_kms: Export property blob functions for output/pipe/plane, v2.

2017-10-19 Thread Mika Kahola
Reviewed-by: Mika Kahola On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: > With the replace_prop_blob functions we can safely replace the blob > for > any property, without having to care about error handling ourselves. > > This will for example allow overriding color management blob

Re: [Intel-gfx] [PATCH i-g-t v2 07/14] lib/igt_kms: Unexport broadcast rgb API.

2017-10-19 Thread Mika Kahola
Reviewed-by: Mika Kahola On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: > Setting broadcast rgb was only used by chamelium, but is now handled > in igt_display by default. This means that chamelium doesn't need to > set it, and this can be hidden. The broadcast RGB property is intel

Re: [Intel-gfx] [PATCH i-g-t] tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Lofstedt, Marta
> -Original Message- > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel > Vetter > Sent: Thursday, October 19, 2017 12:57 PM > To: Intel Graphics Development > Cc: Daniel Vetter ; Joonas Lahtinen > ; Chris Wilson ; > Lofstedt, Marta ; Martin Peres > > Subject: Re:

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister

2017-10-19 Thread Patchwork
== Series Details == Series: series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister URL : https://patchwork.freedesktop.org/series/32288/ State : failure == Summary == Series 32288v1 series starting with [v5,1/2] x86/platform/intel/iosf_mbi

[Intel-gfx] ✗ Fi.CI.BAT: warning for tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Patchwork
== Series Details == Series: tests/gem_eio: Skip in-flight-suspend on snb URL : https://patchwork.freedesktop.org/series/32280/ State : warning == Summary == IGT patchset tested on top of latest successful build abc08cba366a64a07f7f4deb167ae7d6ae059958 lib: Free all internal buffers before me

Re: [Intel-gfx] [PATCH i-g-t v2] lib/igt_kms: Add igt_$obj_has_prop functions, v2.

2017-10-19 Thread Mika Kahola
Reviewed-by: Mika Kahola On Thu, 2017-10-12 at 17:33 +0200, Maarten Lankhorst wrote: > This allows test to test whether a property is supported, in > a nice and clean way. It removes the need for special case > functions like igt_plane_supports_rotation. > > Convert the users of igt_plane_suppor

[Intel-gfx] ✓ Fi.CI.BAT: success for tests/kms_concurrent: Fix testcase fails.

2017-10-19 Thread Patchwork
== Series Details == Series: tests/kms_concurrent: Fix testcase fails. URL : https://patchwork.freedesktop.org/series/32287/ State : success == Summary == IGT patchset tested on top of latest successful build abc08cba366a64a07f7f4deb167ae7d6ae059958 lib: Free all internal buffers before measu

Re: [Intel-gfx] [PATCH 7/8] drm/i915: Use cdclk_state->voltage on CNL

2017-10-19 Thread Ville Syrjälä
On Thu, Oct 19, 2017 at 01:56:38PM +0300, Mika Kahola wrote: > On Thu, 2017-10-19 at 13:48 +0300, Ville Syrjälä wrote: > > On Wed, Oct 18, 2017 at 02:50:59PM -0700, Rodrigo Vivi wrote: > > > > > > On Wed, Oct 18, 2017 at 08:48:24PM +, Ville Syrjala wrote: > > > > > > > > From: Ville Syrjälä

Re: [Intel-gfx] [PATCH] drm: Hold idr_mutex for _drm_lease_revoke

2017-10-19 Thread Chris Wilson
Quoting Chris Wilson (2017-10-19 11:53:44) > _drm_lease_revoke() requires it callers to hold the idr_mutex, but its > only caller did not. Every device release would then trigger: > > WARNING: CPU: 7 PID: 4169 at drivers/gpu/drm/drm_lease.c:313 > _drm_lease_revoke+0x12c/0x140 > Modules linked i

Re: [Intel-gfx] [PATCH v2 10/10] drm/i915: Drop the redundant hdmi prefix/suffix from a lot of variables

2017-10-19 Thread Ville Syrjälä
On Wed, Oct 18, 2017 at 12:59:05PM -0700, James Ausmus wrote: > On Wed, Oct 18, 2017 at 09:19:58PM +0300, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > A bunch of functions are now exclusively used for HDMI, so naming the > > variables with hdmi prefix/suffix is redundant. Also use int rat

Re: [Intel-gfx] [RFC 1/2] drm/i915: Add connector property to force bpc

2017-10-19 Thread Jani Nikula
On Thu, 19 Oct 2017, Daniel Vetter wrote: > On Wed, Oct 18, 2017 at 03:29:48PM -0700, Sripada, Radhakrishna wrote: >> Currently the user space does not have a way to force the bpc. The >> default bpc to be programmed is decided by the driver and is run >> against connector limitations. Creating a

Re: [Intel-gfx] [PATCH i-g-t v2 09/14] lib/igt_kms: Add igt_$obj_get_prop functions

2017-10-19 Thread Mika Kahola
Reviewed-by: Mika Kahola On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: > Some tests need to get the current kernel value for properties > as part of the test. Add get_prop functions that will retrieve > the current kernel value. > > Signed-off-by: Maarten Lankhorst > --- >  lib/ig

[Intel-gfx] [PATCH] drm/i915: Add Guc/HuC firmware details to error state

2017-10-19 Thread Michal Wajdeczko
Include GuC and HuC firmware details in captured error state to provide additional debug information. To reuse existing uc firmware pretty printer, introduce new drm-printer variant that works with our i915_error_state_buf output. Suggested-by: Chris Wilson Signed-off-by: Michal Wajdeczko Cc: Ch

[Intel-gfx] ✓ Fi.CI.IGT: success for tests/kms_concurrent: Fix testcase fails.

2017-10-19 Thread Patchwork
== Series Details == Series: tests/kms_concurrent: Fix testcase fails. URL : https://patchwork.freedesktop.org/series/32287/ State : success == Summary == Test kms_setmode: Subgroup basic: fail -> PASS (shard-hsw) fdo#99912 Test drv_module_reload: Su

Re: [Intel-gfx] [PATCH i-g-t] tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Daniel Vetter
On Thu, Oct 19, 2017 at 1:37 PM, Lofstedt, Marta wrote: > > >> -Original Message- >> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel >> Vetter >> Sent: Thursday, October 19, 2017 12:57 PM >> To: Intel Graphics Development >> Cc: Daniel Vetter ; Joonas Lahtinen >> ;

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister

2017-10-19 Thread Hans de Goede
Hi, On 19-10-17 13:50, Patchwork wrote: == Series Details == Series: series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister URL : https://patchwork.freedesktop.org/series/32288/ State : failure This seems to be a random failure getting a

[Intel-gfx] [CI PATCH i-g-t] Run gem_eio@in-flight-suspend on farm1

2017-10-19 Thread Petri Latvala
...to see if it's problematic elsewhere than just SNB (as seen on shards). Signed-off-by: Petri Latvala --- tests/intel-ci/fast-feedback.testlist | 298 +- 1 file changed, 2 insertions(+), 296 deletions(-) diff --git a/tests/intel-ci/fast-feedback.testlist b/t

Re: [Intel-gfx] [PATCH i-g-t v2 10/14] lib/igt_kms: Remove igt_pipe_get_property

2017-10-19 Thread Mika Kahola
Reviewed-by: Mika Kahola On Thu, 2017-10-12 at 13:54 +0200, Maarten Lankhorst wrote: > igt_pipe_get_property has been replaced by igt_pipe_obj_get_prop. > > Signed-off-by: Maarten Lankhorst > --- >  lib/igt_kms.c | 10 -- >  lib/igt_kms.h |  3 --- >  2 files changed, 13 deletions(-) > >

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister

2017-10-19 Thread Hans de Goede
Hi, On 19-10-17 15:04, Hans de Goede wrote: Hi, On 19-10-17 13:50, Patchwork wrote: == Series Details == Series: series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister URL   : https://patchwork.freedesktop.org/series/32288/ State : failure

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Add Guc/HuC firmware details to error state

2017-10-19 Thread Patchwork
== Series Details == Series: drm/i915: Add Guc/HuC firmware details to error state URL : https://patchwork.freedesktop.org/series/32293/ State : failure == Summary == Series 32293v1 drm/i915: Add Guc/HuC firmware details to error state https://patchwork.freedesktop.org/api/1.0/series/32293/rev

Re: [Intel-gfx] [PATCH i-g-t] tests/gem_eio: Skip in-flight-suspend on snb

2017-10-19 Thread Martin Peres
On 19/10/17 12:51, Daniel Vetter wrote: CI gets upset about it resulting in an incomplete, let's skip it until that's fixed to avoid havoc in the CI farm. Of course this should/will be reverted as soon as we have a fix (similar to how we dealt with the snb-dies-in-blt-hangs issue). Cc: Joonas La

Re: [Intel-gfx] [PATCH] drm/i915: Add Guc/HuC firmware details to error state

2017-10-19 Thread Chris Wilson
Quoting Michal Wajdeczko (2017-10-19 13:57:06) > diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c > b/drivers/gpu/drm/i915/i915_gpu_error.c > index 653fb69..0105b87 100644 > --- a/drivers/gpu/drm/i915/i915_gpu_error.c > +++ b/drivers/gpu/drm/i915/i915_gpu_error.c > @@ -30,6 +30,8 @@ > #include

Re: [Intel-gfx] [PATCH] drm/i915: Add Guc/HuC firmware details to error state

2017-10-19 Thread Chris Wilson
Quoting Michal Wajdeczko (2017-10-19 13:57:06) > @@ -774,6 +793,11 @@ int i915_error_state_to_str(struct > drm_i915_error_state_buf *m, > err_print_capabilities(m, &error->device_info); > err_print_params(m, &error->params); > > + if (HAS_GUC(dev_priv)) { Could we not peek

[Intel-gfx] [PATCH 01/10] drm/i915: Don't use encoder->type in intel_ddi_set_pipe_settings()

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä encoder->type isn't reliable for DP/HDMI so instead extract the correct type from the crtc state in intel_ddi_set_pipe_settings(). Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_ddi.c | 47 1 file changed, 24 insertions(

[Intel-gfx] [PATCH 00/10] drm/i915: Last part of DDI encoder->type cleanup

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä Here's the last chunk of my DDI encoder->type frobbery elimnination. Afterwards DP/HDMI DDI encoders will have "DDI" as their type permanently, and instead one needs to consult the crtc state output_types to determine in which mode we're driving the port. For eDP DDI encoder w

[Intel-gfx] [PATCH 08/10] drm/i915: Pass a crtc state to ddi post_disable from MST code

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä Pass an old crtc state to intel_ddi_post_disable() from the MST code. Note that this crtc state won't necessaitly match the one that was passed to intel_ddi_pre_enable() if the first stream to be enabled isn't the last stream to be disabled. But this is fine since the states

[Intel-gfx] [PATCH v5 05/10] drm/i915: Stop frobbing with DDI encoder->type

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä Currently the DDI encoder->type will change at runtime depending on what kind of hotplugs we've processed. That's quite bad since we can't really trust that that current value of encoder->type actually matches the type of signal we're trying to drive through it. Let's elimina

[Intel-gfx] [PATCH 06/10] drm/i915: Nuke intel_ddi_get_encoder_port()

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä encoder->port works for FDI, and it also works for MST (regardless of whether we're dealing with the "fake" MST encoder, or mst->primary). So let's eliminate intel_ddi_get_encoder_port(). Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_ddi.c | 50 ++

[Intel-gfx] [PATCH 02/10] drm/i915: Pass crtc state to intel_prepare_dp_ddi_buffers()

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä Eliminate intel_prepare_dp_ddi_buffers()'s reliance on the encoder->type by passing in the crtc state. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_ddi.c | 25 + 1 file changed, 9 insertions(+), 16 deletions(-) diff --git a/drivers/gp

[Intel-gfx] [PATCH 04/10] drm/i915: Stop using encoder->type in intel_ddi_enable_transcoder_func()

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä intel_ddi_enable_transcoder_func() already has the crtc state so we can use that instead of the untrustworthy encoder->type. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_ddi.c | 15 +-- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git

[Intel-gfx] [PATCH 07/10] drm/i915: Eliminate pll->state usage from bxt_calc_pll_link()

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä We should be using the DPLL hw state we got from the current crtc state to determine the corresponding port clock frequency rather than getting it via the current state programmed into the DPLL. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_ddi.c | 17 +---

[Intel-gfx] [PATCH 10/10] drm/i915: Use intel_crtc_has_dp_encoder() for LPE audio

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä Reduce our general reliance on encoder->type and instead use output_types from the crtc state when enabling LPE audio. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_audio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i91

[Intel-gfx] [PATCH 03/10] drm/i915: Start using output_types for DPLL selection

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä encoder->type is not realiable for DP/HDMI so let's switch the DPLL selection over to using output_types. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_dpll_mgr.c | 36 +-- 1 file changed, 13 insertions(+), 23 deletions(-) diff

[Intel-gfx] [PATCH 09/10] drm/i915: Use intel_ddi_get_config() for MST

2017-10-19 Thread Ville Syrjala
From: Ville Syrjälä Eliminate the partially duplicated DDI readout code from MST, and instead just call intel_ddi_get_config(). As a nice bonus we get more cross checking as intel_ddi_get_config() will populate output_types based on the actual mode of the DDI port. Additonally intel_ddi_get_conf

[Intel-gfx] ✓ Fi.CI.BAT: success for Run gem_eio@in-flight-suspend on farm1

2017-10-19 Thread Patchwork
== Series Details == Series: Run gem_eio@in-flight-suspend on farm1 URL : https://patchwork.freedesktop.org/series/32296/ State : success == Summary == IGT patchset tested on top of latest successful build abc08cba366a64a07f7f4deb167ae7d6ae059958 lib: Free all internal buffers before measurin

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Last part of DDI encoder->type cleanup

2017-10-19 Thread Patchwork
== Series Details == Series: drm/i915: Last part of DDI encoder->type cleanup URL : https://patchwork.freedesktop.org/series/32298/ State : success == Summary == Series 32298v1 drm/i915: Last part of DDI encoder->type cleanup https://patchwork.freedesktop.org/api/1.0/series/32298/revisions/1/m

Re: [Intel-gfx] [PATCH RESEND FOR CI] drm/i915: remove g4x lowfreq_avail and has_pipe_cxsr

2017-10-19 Thread Jani Nikula
On Tue, 17 Oct 2017, Jani Nikula wrote: > They're unused and unsupported. Leave the reduced_clock pointers in > place still, should they prove useful later on. > > v2: go from nuking DDI lowfreq_avail to nuking it entirely (Ville) > > Cc: Daniel Vetter > Cc: Ville Syrjälä > Suggested-by: Ville S

Re: [Intel-gfx] [PATCH RESEND FOR CI] drm/i915/crt: split compute_config hook by platforms

2017-10-19 Thread Jani Nikula
On Tue, 17 Oct 2017, Jani Nikula wrote: > Only the DDI hook has some actual content. > > Cc: Daniel Vetter > Cc: Ville Syrjälä > Reviewed-by: Ville Syrjälä > Signed-off-by: Jani Nikula Pushed to dinq, thanks for the review. BR, Jani. > --- > drivers/gpu/drm/i915/intel_crt.c | 26 ++

Re: [Intel-gfx] [RFC 1/2] drm/i915: Add connector property to force bpc

2017-10-19 Thread Ville Syrjälä
On Thu, Oct 19, 2017 at 03:56:37PM +0300, Jani Nikula wrote: > On Thu, 19 Oct 2017, Daniel Vetter wrote: > > On Wed, Oct 18, 2017 at 03:29:48PM -0700, Sripada, Radhakrishna wrote: > >> Currently the user space does not have a way to force the bpc. The > >> default bpc to be programmed is decided b

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

2017-10-19 Thread Jani Nikula
Hi Dave, I hoped this was going to be the last pull, but there's some pressure for another. I'll tag more this week, and we can see next week if you'd be willing to still take it. BR, Jani. drm-intel-next-2017-10-12: Last batch of drm/i915 features for v4.15: - transparent huge pages support (M

[Intel-gfx] ✗ Fi.CI.IGT: warning for Run gem_eio@in-flight-suspend on farm1

2017-10-19 Thread Patchwork
== Series Details == Series: Run gem_eio@in-flight-suspend on farm1 URL : https://patchwork.freedesktop.org/series/32296/ State : warning == Summary == Test drv_module_reload: Subgroup basic-no-display: pass -> DMESG-WARN (shard-hsw) fdo#102707 Test kms_busy:

[Intel-gfx] [PATCH 2/2] drm/i915: Move execlists port head instead of memmoving array

2017-10-19 Thread Mika Kuoppala
From: Mika Kuoppala As all our access to execlist ports are through head and tail helpers, we can now move the head instead of memmoving the array. Cc: Michał Winiarski Cc: Joonas Lahtinen Cc: Chris Wilson Signed-off-by: Mika Kuoppala --- drivers/gpu/drm/i915/intel_ringbuffer.h | 9 +---

[Intel-gfx] [PATCH 1/2] drm/i915: Introduce execlist_port_* accessors

2017-10-19 Thread Mika Kuoppala
From: Mika Kuoppala Instead of trusting that first available port is at index 0, use accessor to hide this. This is a preparation for a following patches where head can be at arbitrary location in the port array. v2: improved commit message, elsp_ready readability (Chris) v3: s/execlist_port_ind

  1   2   3   >