[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Ignore irq enabling on the virtual engines

2020-07-11 Thread Patchwork
== Series Details == Series: drm/i915/gt: Ignore irq enabling on the virtual engines URL : https://patchwork.freedesktop.org/series/79383/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8732_full -> Patchwork_18141_full Summ

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Ignore irq enabling on the virtual engines

2020-07-11 Thread Patchwork
== Series Details == Series: drm/i915/gt: Ignore irq enabling on the virtual engines URL : https://patchwork.freedesktop.org/series/79383/ State : success == Summary == CI Bug Log - changes from CI_DRM_8732 -> Patchwork_18141 Summary --

[Intel-gfx] thinkpad x60: oops in eb_relocate_dma in next-20200710

2020-07-11 Thread Pavel Machek
Hi! I attempted to suspend x60, but it did not work well... Machine is too messed up to pull more debug info from it :-(. Best regards, Pavel [11645.369495] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2) [1

[Intel-gfx] [PATCH] drm/i915/gt: Ignore irq enabling on the virtual engines

2020-07-11 Thread Chris Wilson
We do not use the virtual engines for interrupts (they have physical components), but we do use them to decouple the fence signaling during submission. Currently, when we submit a completed request, we try to enable the interrupt handler for the virtual engine, but we never disarm it. A quick fix i

Re: [Intel-gfx] [PATCH v4 06/16] pwm: lpss: Correct get_state result for base_unit == 0

2020-07-11 Thread Hans de Goede
Hi, On 7/11/20 8:11 AM, Uwe Kleine-König wrote: On Thu, Jul 09, 2020 at 05:47:59PM +0200, Hans de Goede wrote: Hi, On 7/9/20 4:50 PM, Andy Shevchenko wrote: On Wed, Jul 08, 2020 at 11:14:22PM +0200, Hans de Goede wrote: The datasheet specifies that programming the base_unit part of the ctrl

Re: [Intel-gfx] [PATCH v4 16/16] drm/i915: panel: Use atomic PWM API for devs with an external PWM controller

2020-07-11 Thread Hans de Goede
Hi, On 7/11/20 8:32 AM, Uwe Kleine-König wrote: On Wed, Jul 08, 2020 at 11:14:32PM +0200, Hans de Goede wrote: Now that the PWM drivers which we use have been converted to the atomic PWM API, we can move the i915 panel code over to using the atomic PWM API. The removes a long standing FIXME a

Re: [Intel-gfx] [PATCH v4 00/15] acpi/pwm/i915: Convert pwm-crc and i915 driver's PWM code to use the atomic PWM API

2020-07-11 Thread Hans de Goede
Hi, On 7/11/20 8:19 AM, Uwe Kleine-König wrote: Hi Hans, On Thu, Jul 09, 2020 at 04:40:56PM +0200, Hans de Goede wrote: On 7/9/20 4:14 PM, Sam Ravnborg wrote: On Wed, Jul 08, 2020 at 11:14:16PM +0200, Hans de Goede wrote: Here is v4 of my patch series converting the i915 driver's code for c

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Always reset the engine, even if inactive, on execlists failure

2020-07-11 Thread Patchwork
== Series Details == Series: drm/i915/gt: Always reset the engine, even if inactive, on execlists failure URL : https://patchwork.freedesktop.org/series/79378/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8732_full -> Patchwork_18140_full

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Recalculate FBC w/a stride when needed (rev2)

2020-07-11 Thread Patchwork
== Series Details == Series: drm/i915: Recalculate FBC w/a stride when needed (rev2) URL : https://patchwork.freedesktop.org/series/79368/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8732_full -> Patchwork_18139_full Summ

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Always reset the engine, even if inactive, on execlists failure

2020-07-11 Thread Patchwork
== Series Details == Series: drm/i915/gt: Always reset the engine, even if inactive, on execlists failure URL : https://patchwork.freedesktop.org/series/79378/ State : success == Summary == CI Bug Log - changes from CI_DRM_8732 -> Patchwork_18140 ==

[Intel-gfx] [PATCH] drm/i915/gt: Always reset the engine, even if inactive, on execlists failure

2020-07-11 Thread Chris Wilson
If something has gone awry with the CSB processing, we need to pause, unwind and restart the request submission and event processing. However, currently we skip the engine reset if we raise an error but discover no active context, in the mistaken belief that it was merely a glitch in the matrix. Th

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Recalculate FBC w/a stride when needed (rev2)

2020-07-11 Thread Patchwork
== Series Details == Series: drm/i915: Recalculate FBC w/a stride when needed (rev2) URL : https://patchwork.freedesktop.org/series/79368/ State : success == Summary == CI Bug Log - changes from CI_DRM_8732 -> Patchwork_18139 Summary --

[Intel-gfx] [PATCH v2] drm/i915: Recalculate FBC w/a stride when needed

2020-07-11 Thread Ville Syrjala
From: Ville Syrjälä Currently we're failing to recalculate the gen9 FBC w/a stride unless something more drastic than just the modifier itself has changed. This often leaves us with FBC enabled with the linear fbdev framebuffer without the w/a stride enabled. That will cause an immediate underrun