[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/gen11: Preempt-to-idle support in execlists. (rev5)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/gen11: Preempt-to-idle support in execlists. (rev5) URL : https://patchwork.freedesktop.org/series/40747/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915/gen11: Preempt-to-idle support in execlists. -drivers/gpu/drm/i915/selftest

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Skip over live context testing when wedged

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 07:42:00AM +0100, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-07-05 21:52:10) > > On Thu, Jul 05, 2018 at 03:58:45PM +0100, Chris Wilson wrote: > > > If the GPU is terminally wedged we cannot submit any requests into a > > > context, completely unfulfilling our purpose

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gen11: Preempt-to-idle support in execlists. (rev5)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/gen11: Preempt-to-idle support in execlists. (rev5) URL : https://patchwork.freedesktop.org/series/40747/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4446 -> Patchwork_9572 = == Summary - SUCCESS == No regressions found. Externa

Re: [Intel-gfx] [PATCH] drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 12:54:02PM +0100, Chris Wilson wrote: > If we have just completed a WC write, we must ensure that the WCB (Write > Combining Buffer) is flushed out to main memory before we can expect to > see the results. This is especially important when mixing WC with GTT as > the physica

Re: [Intel-gfx] [PATCH 3/8] drm/i915: Rewrite mst suspend/resume in terms of encoders

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 01:42:35PM +0300, Ville Syrjälä wrote: > On Thu, Jul 05, 2018 at 02:29:59PM -0700, Rodrigo Vivi wrote: > > On Thu, Jul 05, 2018 at 07:43:52PM +0300, Ville Syrjala wrote: > > > From: Ville Syrjälä > > > > > > Rather than looping over all the ports and picking the encoder ba

Re: [Intel-gfx] [PATCH 2/8] drm/i915: Introduce intel_encoder_is_dig_port()

2018-07-06 Thread Rodrigo Vivi
On Thu, Jul 05, 2018 at 07:43:51PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Add intel_encoder_is_dig_port() to match intel_encoder_is_dp(). > > Signed-off-by: Ville Syrjälä Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/intel_drv.h | 24 +++- > 1 fil

[Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Chris Wilson
Older machines do not have the 128-byte tile width format for I915_TILING_Y and so we must adapt our reference swizzle. Testcase: igt/drv_selftest/live_objects #gdg Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/selftests/i915_gem_object.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion

Re: [Intel-gfx] [BUG] i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Guang Bai
On Fri, 6 Jul 2018 14:44:58 +0800 Chris Chiu wrote: > On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä > wrote: > > On Thu, Jul 05, 2018 at 03:58:36PM +0800, Chris Chiu wrote: > >> Hi, > >> We have few ASUS laptops X705FD (The new WiskyLake), X560UD > >> (intel i5-8250U), X530UN (intel i7-85

[Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Chris Wilson
clflush is an unserialised instruction and the IA manual strongly advises you to serialise it with a mb. To be cautious, apply one before and one after, so that it is serialised with both writes and reads without worrying too much about the required direction. Signed-off-by: Chris Wilson --- ...

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Adjust y-tiling height for older machines URL : https://patchwork.freedesktop.org/series/46084/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9573 = == Summary - SUCCESS == No regressions found. Extern

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Provide full mb() around clflush URL : https://patchwork.freedesktop.org/series/46085/ State : warning == Summary == $ dim checkpatch origin/drm-tip cdfe0eb01ba9 drm/i915/selftests: Provide full mb() around clflush -:24: WARNING:MEMORY_BARRIER:

Re: [Intel-gfx] [PATCH v6] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Ville Syrjälä
On Tue, Jul 03, 2018 at 01:21:02PM -0700, Azhar Shaikh wrote: > On KBL, WHL RVPs, booting up with an external display connected, triggers > below warning, when the BiOS brings up the external display too. > This warning is not seen during hotplug. > > [3.615226] [ cut here ]---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Provide full mb() around clflush URL : https://patchwork.freedesktop.org/series/46085/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9574 = == Summary - SUCCESS == No regressions found. External URL:

[Intel-gfx] [PATCH v7] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Azhar Shaikh
On KBL, WHL RVPs, booting up with an external display connected, triggers below warning, when the BiOS brings up the external display too. This warning is not seen during hotplug. [3.615226] [ cut here ] [3.619829] plane 1A assertion failure (expected on, current of

Re: [Intel-gfx] [PATCH v7] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Shaikh, Azhar
>-Original Message- >From: Shaikh, Azhar >Sent: Friday, July 6, 2018 11:28 AM >To: intel-gfx@lists.freedesktop.org >Cc: ville.syrj...@linux.intel.com; Navare, Manasi D >; Shaikh, Azhar >Subject: [PATCH v7] drm/i915: Fix assert_plane() warning on bootup with >external display > >On KBL, W

[Intel-gfx] [PATCH v8] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-06 Thread Azhar Shaikh
On KBL, WHL RVPs, booting up with an external display connected, triggers below warning, when the BiOS brings up the external display too. This warning is not seen during hotplug. [3.615226] [ cut here ] [3.619829] plane 1A assertion failure (expected on, current of

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix assert_plane() warning on bootup with external display (rev7)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Fix assert_plane() warning on bootup with external display (rev7) URL : https://patchwork.freedesktop.org/series/44909/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9575 = == Summary - SUCCESS == No regressions f

[Intel-gfx] [PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()

2018-07-06 Thread Peter Jones
This was sort of annoying me: random:~$ dmesg | tail -1 [523884.039227] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. random:~$ dmesg | grep -c "Reducing the compressed" 47 Th

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix assert_plane() warning on bootup with external display (rev8)

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Fix assert_plane() warning on bootup with external display (rev8) URL : https://patchwork.freedesktop.org/series/44909/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9576 = == Summary - SUCCESS == No regressions f

[Intel-gfx] ✓ Fi.CI.BAT: success for Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()

2018-07-06 Thread Patchwork
== Series Details == Series: Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE() URL : https://patchwork.freedesktop.org/series/46092/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4448 -> Patchwork_9577 = == Summary - SUCCESS == No regressions fou

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 06:49:26PM +0100, Chris Wilson wrote: > clflush is an unserialised instruction and the IA manual strongly advises > you to serialise it with a mb. To be cautious, apply one before and one > after, my understanding is that we need one before and one after anyways, not just a

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > Older machines do not have the 128-byte tile width format for > I915_TILING_Y and so we must adapt our reference swizzle. > > Testcase: igt/drv_selftest/live_objects #gdg The change below itself makes sense to me, but I'm trying to u

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Chris Wilson
Quoting Rodrigo Vivi (2018-07-06 21:23:00) > On Fri, Jul 06, 2018 at 06:49:26PM +0100, Chris Wilson wrote: > > clflush is an unserialised instruction and the IA manual strongly advises > > you to serialise it with a mb. To be cautious, apply one before and one > > after, > > my understanding is th

Re: [Intel-gfx] [PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 03:04:24PM -0400, Peter Jones wrote: > This was sort of annoying me: > > random:~$ dmesg | tail -1 > [523884.039227] [drm] Reducing the compressed framebuffer size. This may lead > to less power savings than a non-reduced-size. Try to increase stolen memory > size if avai

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Provide full mb() around clflush

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 09:27:47PM +0100, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-07-06 21:23:00) > > On Fri, Jul 06, 2018 at 06:49:26PM +0100, Chris Wilson wrote: > > > clflush is an unserialised instruction and the IA manual strongly advises > > > you to serialise it with a mb. To be cau

Re: [Intel-gfx] [BUG] i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 10:41:18AM -0700, Guang Bai wrote: > On Fri, 6 Jul 2018 14:44:58 +0800 > Chris Chiu wrote: > > > On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä > > wrote: > > > On Thu, Jul 05, 2018 at 03:58:36PM +0800, Chris Chiu wrote: > > >> Hi, > > >> We have few ASUS laptops X7

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Chris Wilson
Quoting Rodrigo Vivi (2018-07-06 21:27:52) > On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > > Older machines do not have the 128-byte tile width format for > > I915_TILING_Y and so we must adapt our reference swizzle. > > > > Testcase: igt/drv_selftest/live_objects #gdg > > The c

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 09:39:14PM +0100, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-07-06 21:27:52) > > On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > > > Older machines do not have the 128-byte tile width format for > > > I915_TILING_Y and so we must adapt our reference swi

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Adjust y-tiling height for older machines

2018-07-06 Thread Chris Wilson
Quoting Rodrigo Vivi (2018-07-06 21:55:37) > On Fri, Jul 06, 2018 at 09:39:14PM +0100, Chris Wilson wrote: > > Quoting Rodrigo Vivi (2018-07-06 21:27:52) > > > On Fri, Jul 06, 2018 at 06:15:37PM +0100, Chris Wilson wrote: > > > > Older machines do not have the 128-byte tile width format for > > > >

[Intel-gfx] [PATCH] drm/i915/selftests: Avoid warning if runtime pm is disabled

2018-07-06 Thread Chris Wilson
Inside the mock GEM device, we try to grab the runtime pm for the fake device to prevent it from ever suspending. However, if CONFIG_PM is not set, trying to obtain the wakref returns an error which we WARN about. Suppress the expected warning. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i91

[Intel-gfx] [CI] drm/i915: Replace nested subclassing with explicit subclasses

2018-07-06 Thread Chris Wilson
In the next patch, we will want a third distinct class of timeline that may overlap with the current pair of client and engine timeline classes. Rather than use the ad hoc markup of SINGLE_DEPTH_NESTING, initialise the different timeline classes with an explicit subclass. Signed-off-by: Chris Wils

[Intel-gfx] [PATCH] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Tarun Vyas
In commit "drm/i915: Wait for PSR exit before checking for vblank evasion", the idea was to limit the PSR IDLE checks when PSR is actually supported. While CAN_PSR does do that check, it doesn't applies on a per-crtc basis. crtc_state->has_psr is a more granular check that avoids everything but pip

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Avoid warning if runtime pm is disabled

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 09:59:47PM +0100, Chris Wilson wrote: > Inside the mock GEM device, we try to grab the runtime pm for the fake > device to prevent it from ever suspending. However, if CONFIG_PM is not > set, trying to obtain the wakref returns an error which we WARN about. > Suppress the ex

Re: [Intel-gfx] [PATCH] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Rodrigo Vivi
On Fri, Jul 06, 2018 at 02:13:18PM -0700, Tarun Vyas wrote: > In commit "drm/i915: Wait for PSR exit before checking for vblank > evasion", the idea was to limit the PSR IDLE checks when PSR is > actually supported. While CAN_PSR does do that check, it doesn't > applies on a per-crtc basis. crtc_st

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [01/27] drm/i915: Squelch very verbose error logging

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [01/27] drm/i915: Squelch very verbose error logging URL : https://patchwork.freedesktop.org/series/46051/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4441_full -> Patchwork_9560_full = == Summary - FAILURE == Serious

[Intel-gfx] ✓ Fi.CI.IGT: success for ICELAKE DSI DRIVER (rev4)

2018-07-06 Thread Patchwork
== Series Details == Series: ICELAKE DSI DRIVER (rev4) URL : https://patchwork.freedesktop.org/series/44823/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4441_full -> Patchwork_9561_full = == Summary - WARNING == Minor unknown changes coming with Patchwork_9561_full nee

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Avoid warning if runtime pm is disabled

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Avoid warning if runtime pm is disabled URL : https://patchwork.freedesktop.org/series/46101/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4449 -> Patchwork_9578 = == Summary - SUCCESS == No regressions found. External

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Replace nested subclassing with explicit subclasses

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Replace nested subclassing with explicit subclasses URL : https://patchwork.freedesktop.org/series/46103/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4449 -> Patchwork_9579 = == Summary - SUCCESS == No regressions found. Extern

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update URL : https://patchwork.freedesktop.org/series/46104/ State : warning == Summary == $ dim checkpatch origin/drm-tip 27f7762e393d drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe upda

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update URL : https://patchwork.freedesktop.org/series/46104/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4449 -> Patchwork_9580 = == Summary - SUCCESS == No regressions found.

Re: [Intel-gfx] [BUG] i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Guang Bai
On Fri, 6 Jul 2018 13:38:06 -0700 Rodrigo Vivi wrote: > On Fri, Jul 06, 2018 at 10:41:18AM -0700, Guang Bai wrote: > > On Fri, 6 Jul 2018 14:44:58 +0800 > > Chris Chiu wrote: > > > > > On Thu, Jul 5, 2018 at 10:40 PM, Ville Syrjälä > > > wrote: > > > > On Thu, Jul 05, 2018 at 03:58:36PM +0

[Intel-gfx] ✗ Fi.CI.BAT: failure for i915 HDMI connector status is connected after disconnection

2018-07-06 Thread Patchwork
== Series Details == Series: i915 HDMI connector status is connected after disconnection URL : https://patchwork.freedesktop.org/series/46108/ State : failure == Summary == Applying: i915 HDMI connector status is connected after disconnection error: patch fragment without header at line 7: @@

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Introduce BITS_PER_TYPE

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Introduce BITS_PER_TYPE URL : https://patchwork.freedesktop.org/series/46055/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4443_full -> Patchwork_9562_full = == Summary - WARNING == Minor unknown changes coming with Patchwork_9562_

Re: [Intel-gfx] [PATCH 2/2] drm/i915: use the ICL stolen memory

2018-07-06 Thread Lucas De Marchi
On Fri, May 4, 2018 at 1:33 PM Paulo Zanoni wrote: > > Now that our stolen memory is already reserved by the x86 subsystem > (since commit "x86/gpu: reserve ICL's graphics stolen memory"), make > use of it. > > Cc: Joonas Lahtinen > Cc: Daniele Ceraolo Spurio > Cc: x...@kernel.org > Signed-off-b

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Record logical context support in driver caps (rev2)

2018-07-06 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: Record logical context support in driver caps (rev2) URL : https://patchwork.freedesktop.org/series/46065/ State : failure == Summary == = CI Bug Log - changes from CI_DRM__full -> Patchwork_9563_full = == Summary - FAILUR

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Skip live_execlists if the GPU is terminally wedged

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Skip live_execlists if the GPU is terminally wedged URL : https://patchwork.freedesktop.org/series/46069/ State : failure == Summary == = CI Bug Log - changes from CI_DRM__full -> Patchwork_9565_full = == Summary - FAILURE == Serious unk

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Flush the WCB following a WC write

2018-07-06 Thread Patchwork
== Series Details == Series: drm/i915: Flush the WCB following a WC write URL : https://patchwork.freedesktop.org/series/46070/ State : failure == Summary == = CI Bug Log - changes from CI_DRM__full -> Patchwork_9566_full = == Summary - FAILURE == Serious unknown changes coming with Pa

Re: [Intel-gfx] [PATCH 0/4] drm/i915/intel_dsi: Read back and use pclk set by the GOP

2018-07-06 Thread Hans de Goede
Hi, On 07/06/2018 03:14 PM, Jani Nikula wrote: On Fri, 29 Jun 2018, Hans de Goede wrote: Hi, On 19-06-18 22:18, Hans de Goede wrote: Hi All, This patch-set is the result of the work I've been doing recently to give people a smooth "flickerfree" boot experience where the display keeps displa

Re: [Intel-gfx] [PATCH 4/4] drm/i915/intel_dsi: Read back pclk set by GOP and use that as pclk

2018-07-06 Thread Hans de Goede
Hi, On 07/06/2018 04:16 PM, Ville Syrjälä wrote: On Tue, Jun 19, 2018 at 10:18:27PM +0200, Hans de Goede wrote: On BYT and CHT the GOP sometimes initializes the pclk at a (slightly) different frequency then the pclk which we've calculated. This commit makes the DSI code read-back the pclk set

<    1   2