[Intel-gfx] ✓ Fi.CI.BAT: success for Enabling content-type setting for HDMI displays.

2018-04-18 Thread Patchwork
== Series Details == Series: Enabling content-type setting for HDMI displays. URL : https://patchwork.freedesktop.org/series/41876/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4065 -> Patchwork_8730 = == Summary - SUCCESS == No regressions found. External URL: http

Re: [Intel-gfx] [PATCH] drm/i915: Fix LSPCON TMDS output buffer enabling from low-power state

2018-04-18 Thread Jani Nikula
On Mon, 16 Apr 2018, Clint Taylor wrote: > On 04/16/2018 08:53 AM, Imre Deak wrote: >> LSPCON adapters in low-power state may ignore the first I2C write during >> TMDS output buffer enabling, resulting in a blank screen even with an >> otherwise enabled pipe. Fix this by reading back and validatin

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix error checking for wait_var_timeout URL : https://patchwork.freedesktop.org/series/41835/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063_full -> Patchwork_8727_full = == Summary - WARNING == Minor unknown changes c

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enabling content-type setting for HDMI displays.

2018-04-18 Thread Patchwork
== Series Details == Series: Enabling content-type setting for HDMI displays. URL : https://patchwork.freedesktop.org/series/41876/ State : warning == Summary == $ dim checkpatch origin/drm-tip ffb3db0b7c7e drm: content-type property for HDMI connector -:78: CHECK:PARENTHESIS_ALIGNMENT: Alignm

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/crc: make locking and source check more robust

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/crc: make locking and source check more robust URL : https://patchwork.freedesktop.org/series/41821/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4065 -> Patchwork_8729 = == Summary - FAILURE == Serious unknown changes coming with P

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Don't use -ETIMEDOUT from inside a test

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Don't use -ETIMEDOUT from inside a test URL : https://patchwork.freedesktop.org/series/41828/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4065 -> Patchwork_8728 = == Summary - SUCCESS == No regressions found. External

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063_full -> Patchwork_8725_full = == Summary - WARNING == Minor unknown changes comi

Re: [Intel-gfx] [PATCH igt] igt/gem_exec_schedule: Exercise "deep" preemption

2018-04-18 Thread Michał Winiarski
On Wed, Apr 11, 2018 at 11:13:56AM +0100, Chris Wilson wrote: > In investigating the issue with having to force preemption within the > executing ELSP[], we want to trigger preemption between all elements of > that array. To that end, we issue a series of requests with different > priorities to fil

[Intel-gfx] [PATCH igt v3] igt/gem_exec_schedule: Exercise "deep" preemption

2018-04-18 Thread Chris Wilson
In investigating the issue with having to force preemption within the executing ELSP[], we want to trigger preemption between all elements of that array. To that end, we issue a series of requests with different priorities to fill the in-flight ELSP[] and then demand preemption into the middle of t

[Intel-gfx] [PATCH] drm/crc: Only report a single overflow when a CRC fd is opened

2018-04-18 Thread Maarten Lankhorst
This reduces the amount of spam when you debug a CRC reading program. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_debugfs_crc.c | 9 - include/drm/drm_debugfs_crc.h | 3 ++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_debugfs_crc.c

Re: [Intel-gfx] [PATCH v2 2/2] i915: content-type property for HDMI connector

2018-04-18 Thread Lisovskiy, Stanislav
From: Hans Verkuil [hverk...@xs4all.nl] Sent: Wednesday, April 18, 2018 3:35 PM To: Lisovskiy, Stanislav; dri-de...@lists.freedesktop.org Cc: intel-gfx@lists.freedesktop.org Subject: Re: [PATCH v2 2/2] i915: content-type property for HDMI connector >> Is t

Re: [Intel-gfx] [PATCH] drm/i915: Refine the has_audio assignment

2018-04-18 Thread Jani Nikula
On Fri, 13 Apr 2018, Chris Wilson wrote: > Quoting Yang (2018-04-13 05:06:45) >> From: Yang Shi >> >> Refine the has_audio assignment for dp and hdmi. > > s/Refine/Ignore the user override for/ > > Why? Yang, we'll need the explanation before we continue with review or even consider merging. We

Re: [Intel-gfx] [PATCH v2 2/2] i915: content-type property for HDMI connector

2018-04-18 Thread Hans Verkuil
On 04/18/18 14:01, Lisovskiy, Stanislav wrote: > Hi, > > Please see my reply inline: > > From: dri-devel [dri-devel-boun...@lists.freedesktop.org] on behalf of Hans > Verkuil [hverk...@xs4all.nl] > Sent: Wednesday, April 18, 2018 2:35 PM > To: Lisovskiy,

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063_full -> Patchwork_8723_full = == Summary - WARNING == Minor unknown changes comi

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix error checking for wait_var_timeout URL : https://patchwork.freedesktop.org/series/41835/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063_full -> Patchwork_8721_full = == Summary - WARNING == Minor unknown changes c

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Don't use -ETIMEDOUT from inside a test

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Don't use -ETIMEDOUT from inside a test URL : https://patchwork.freedesktop.org/series/41828/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063_full -> Patchwork_8720_full = == Summary - WARNING == Minor unknown changes c

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers

2018-04-18 Thread Patchwork
== Series Details == Series: series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers URL : https://patchwork.freedesktop.org/series/41827/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4063_full -> Patchwork_8719_full = == Summary - FAILURE ==

[Intel-gfx] [PATCH] gpu: drm: i915: Change return type to vm_fault_t

2018-04-18 Thread Souptick Joarder
Use new return type vm_fault_t for fault handler. For now, this is just documenting that the function returns a VM_FAULT value rather than an errno. Once all instances are converted, vm_fault_t will become a distinct type. Reference id -> 1c8f422059ae ("mm: change return type to vm_fault_t") Sign

Re: [Intel-gfx] [PATCH] gpu: drm: i915: Change return type to vm_fault_t

2018-04-18 Thread Souptick Joarder
Not exactly. The plan for these patches is to introduce new vm_fault_t type in vm_operations_struct fault handlers. It's now available in 4.17-rc1. We will push all the required drivers/filesystem changes through different maintainers to linus tree. Once everything is converted into vm_fault_t type

Re: [Intel-gfx] [PATCH] gpu: drm: i915: Change return type to vm_fault_t

2018-04-18 Thread Souptick Joarder
On 17-Apr-2018 9:45 PM, "Matthew Wilcox" wrote: > > On Tue, Apr 17, 2018 at 09:14:32PM +0530, Souptick Joarder wrote: > > Not exactly. The plan for these patches is to introduce new vm_fault_t type > > in vm_operations_struct fault handlers. It's now available in 4.17-rc1. We will > > push all the

[Intel-gfx] [PATCH v2] gpu: drm: i915: Change return type to vm_fault_t

2018-04-18 Thread Souptick Joarder
Use new return type vm_fault_t for fault handler. For now, this is just documenting that the function returns a VM_FAULT value rather than an errno. Once all instances are converted, vm_fault_t will become a distinct type. Reference id -> 1c8f422059ae ("mm: change return type to vm_fault_t") Fixe

Re: [Intel-gfx] [PATCH v4 6/6] drm/i915: Add skl_check_nv12_surface for NV12

2018-04-18 Thread Mika Kahola
On Wed, 2018-04-18 at 09:38 +0530, Vidya Srinivas wrote: > From: Maarten Lankhorst > > We skip src trunction/adjustments for > NV12 case and handle the sizes directly. > Without this, pipe fifo underruns are seen on APL/KBL. > > v2: For NV12, making the src coordinates multiplier of 4 > > v3: M

Re: [Intel-gfx] [PATCH v2 2/2] i915: content-type property for HDMI connector

2018-04-18 Thread Lisovskiy, Stanislav
Hi, Please see my reply inline: From: dri-devel [dri-devel-boun...@lists.freedesktop.org] on behalf of Hans Verkuil [hverk...@xs4all.nl] Sent: Wednesday, April 18, 2018 2:35 PM To: Lisovskiy, Stanislav; dri-de...@lists.freedesktop.org Cc: intel-gfx@lists.

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix error checking for wait_var_timeout URL : https://patchwork.freedesktop.org/series/41835/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8727 = == Summary - WARNING == Minor unknown changes coming with

Re: [Intel-gfx] [PATCH v2 1/2] drm: content-type property for HDMI connector

2018-04-18 Thread Hans Verkuil
On 04/18/18 18:51, StanLis wrote: > From: Stanislav Lisovskiy > > Added content_type property to > drm_connector_state in order to properly handle > external HDMI TV content-type setting. > > Signed-off-by: Stanislav Lisovskiy > --- > Documentation/gpu/kms-properties.csv | 1 + > drivers/gpu/

Re: [Intel-gfx] [PATCH v2 2/2] i915: content-type property for HDMI connector

2018-04-18 Thread Hans Verkuil
On 04/18/18 18:51, StanLis wrote: > From: Stanislav Lisovskiy > > Added encoding of drm content_type property from > drm_connector_state within AVI infoframe in order to properly handle > external HDMI TV content-type setting. > > Signed-off-by: Stanislav Lisovskiy > --- > drivers/gpu/drm/i915

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/gmbus: Enable burst read

2018-04-18 Thread Ramalingam C
Thanks ville for reviewing this change. On Wednesday 18 April 2018 12:12 AM, Ville Syrjälä wrote: On Tue, Apr 17, 2018 at 02:25:33PM +0530, Ramalingam C wrote: Support for Burst read in HW is added for HDCP2.2 compliance requirement. This patch enables the burst read for all the gmbus read of

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/audio: Fix audio detection issue on GLK (rev3)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/audio: Fix audio detection issue on GLK (rev3) URL : https://patchwork.freedesktop.org/series/41334/ State : failure == Summary == Applying: drm/i915/audio: Fix audio detection issue on GLK Using index info to reconstruct a base tree... M drivers/gpu

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8725 = == Summary - SUCCESS == No regressions found. External UR

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: set minimum CD clock to twice the BCLK. -O:drivers/gpu/drm/i915/intel_cdclk.c:

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : warning == Summary == $ dim checkpatch origin/drm-tip 25a822b03178 drm/i915: set minimum CD clock to twice the BCLK. -:6: WARNING:COMMIT_LOG_LONG_

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v9,1/2] drm/i915: Implement WaProgramMgsrForCorrectSliceSpecificMmioReads (rev13)

2018-04-18 Thread Patchwork
== Series Details == Series: series starting with [v9,1/2] drm/i915: Implement WaProgramMgsrForCorrectSliceSpecificMmioReads (rev13) URL : https://patchwork.freedesktop.org/series/40503/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8724 = == Summary - FA

Re: [Intel-gfx] [PATCH v3] drm/i915: set minimum CD clock to twice the BCLK.

2018-04-18 Thread Jani Nikula
On Tue, 17 Apr 2018, "Kumar, Abhay" wrote: > On 4/17/2018 12:06 PM, Abhay Kumar wrote: >> In glk when device boots with only 1366x768 panel, HDA codec doesn't comeup. >> This result in no audio forever as cdclk is < 96Mhz. >> This change will ensure CD clock to be twice of BCLK. >> >> v2: >>

Re: [Intel-gfx] [PATCH] drm/i915/icl: Adjust BSD2 semantics to mean any second VCS instance

2018-04-18 Thread Joonas Lahtinen
Quoting Tvrtko Ursulin (2018-04-18 12:33:42) > From: Tvrtko Ursulin > > Currently our driver assumes BSD2 means hardware engine instance number > two. This does not work for Icelake parts with two VCS engines, but which > are hardware instances 0 and 2, and not 0 and 1 as with previous parts. >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8723 = == Summary - WARNING == Minor unknown changes coming with Pa

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915: Pack params to engine->schedule() into a struct

2018-04-18 Thread Chris Wilson
Quoting Joonas Lahtinen (2018-04-18 10:46:27) > Quoting Chris Wilson (2018-04-17 17:31:32) > > +static void print_sched_attr(struct drm_printer *m, > > +const struct drm_i915_private *i915, > > +const struct i915_sched_attr *attr) > > +{ > > +

[Intel-gfx] [PATCH] drm/i915/audio: set minimum CD clock to twice the BCLK

2018-04-18 Thread Jani Nikula
From: Abhay Kumar In GLK when the device boots with only 1366x768 panel without audio, HDA codec doesn't come up. In this case, the CDCLK is less than twice the BCLK. Even though audio isn't being enabled, having a too low CDCLK leads to audio probe failing altogether. Require CDCLK to be at lea

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Mika Kuoppala
Chris Wilson writes: > The old wait_on_atomic_t used a custom callback to perform the > schedule(), which used my return semantics of reporting an error code on > timeout. wait_var_event_timeout() uses the schedule() return semantics > of reporting the remaining jiffies (1 if it timed out with 0

Re: [Intel-gfx] [PATCH v2] drm/i915: Pack params to engine->schedule() into a struct

2018-04-18 Thread Joonas Lahtinen
Quoting Chris Wilson (2018-04-18 12:41:49) > Today we only want to pass along the priority to engine->schedule(), but > in the future we want to have much more control over the various aspects > of the GPU during a context's execution, for example controlling the > frequency allowed. As we need an

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : warning == Summary == $ dim checkpatch origin/drm-tip 969c984b9819 drm/i915: set minimum CD clock to twice the BCLK. -:6: WARNING:COMMIT_LOG_LONG_

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: set minimum CD clock to twice the BCLK. (rev4)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915: set minimum CD clock to twice the BCLK. (rev4) URL : https://patchwork.freedesktop.org/series/32657/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: set minimum CD clock to twice the BCLK. -O:drivers/gpu/drm/i915/intel_cdclk.c:

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/audio: Fix audio detection issue on GLK (rev3)

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/audio: Fix audio detection issue on GLK (rev3) URL : https://patchwork.freedesktop.org/series/41334/ State : failure == Summary == Applying: drm/i915/audio: Fix audio detection issue on GLK Using index info to reconstruct a base tree... M drivers/gpu

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Fix error checking for wait_var_timeout URL : https://patchwork.freedesktop.org/series/41835/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8721 = == Summary - WARNING == Minor unknown changes coming with

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Joonas Lahtinen
Quoting Chris Wilson (2018-04-18 12:14:15) > Quoting Joonas Lahtinen (2018-04-18 10:10:17) > > Quoting Chris Wilson (2018-04-17 20:06:38) > > > The old wait_on_atomic_t used a custom callback to perform the > > > schedule(), which used my return semantics of reporting an error code on > > > timeout

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Don't use -ETIMEDOUT from inside a test

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/selftests: Don't use -ETIMEDOUT from inside a test URL : https://patchwork.freedesktop.org/series/41828/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8720 = == Summary - SUCCESS == No regressions found. External

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915: Pack params to engine->schedule() into a struct

2018-04-18 Thread Joonas Lahtinen
Quoting Chris Wilson (2018-04-17 17:31:32) > +++ b/drivers/gpu/drm/i915/intel_display.c > @@ -12839,7 +12839,9 @@ intel_prepare_plane_fb(struct drm_plane *plane, > > ret = intel_plane_pin_fb(to_intel_plane_state(new_state)); > > - i915_gem_object_wait_priority(obj, 0, I915_PRIORIT

[Intel-gfx] [PATCH v2] drm/i915: Pack params to engine->schedule() into a struct

2018-04-18 Thread Chris Wilson
Today we only want to pass along the priority to engine->schedule(), but in the future we want to have much more control over the various aspects of the GPU during a context's execution, for example controlling the frequency allowed. As we need an ever growing number of parameters for scheduling, m

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers

2018-04-18 Thread Patchwork
== Series Details == Series: series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers URL : https://patchwork.freedesktop.org/series/41827/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8719 = == Summary - SUCCESS == No regre

[Intel-gfx] [PATCH] drm/i915/icl: Adjust BSD2 semantics to mean any second VCS instance

2018-04-18 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Currently our driver assumes BSD2 means hardware engine instance number two. This does not work for Icelake parts with two VCS engines, but which are hardware instances 0 and 2, and not 0 and 1 as with previous parts. This makes the second engine not discoverable via HAS_BSD

Re: [Intel-gfx] [PATCH] drm: Print unadorned pointers

2018-04-18 Thread Maarten Lankhorst
Op 18-04-18 om 11:24 schreef Alexey Brodkin: > After commit ad67b74 ("printk: hash addresses printed with %p") > pointers are being hashed when printed. However, this makes > debug output completely useless. Switch to %px in order to see the > unadorned kernel pointers. > > This was done with the f

Re: [Intel-gfx] [PATCH v2 2/3] drm/i915: Rename priotree to sched

2018-04-18 Thread Joonas Lahtinen
Quoting Chris Wilson (2018-04-17 17:31:31) > Having moved the priotree struct into i915_scheduler.h, identify it as > the scheduling element and rebrand into i915_sched. This becomes more > useful as we start attaching more information we require to propagate > through the scheduler. > > Signed-of

[Intel-gfx] [PATCH] drm: Print unadorned pointers

2018-04-18 Thread Alexey Brodkin
After commit ad67b74 ("printk: hash addresses printed with %p") pointers are being hashed when printed. However, this makes debug output completely useless. Switch to %px in order to see the unadorned kernel pointers. This was done with the following one-liner: find drivers/gpu/drm -type f -name

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers

2018-04-18 Thread Patchwork
== Series Details == Series: series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers URL : https://patchwork.freedesktop.org/series/41827/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: Move the priotree struct to its own headers Okay!

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers

2018-04-18 Thread Patchwork
== Series Details == Series: series starting with [v2,1/3] drm/i915: Move the priotree struct to its own headers URL : https://patchwork.freedesktop.org/series/41827/ State : warning == Summary == $ dim checkpatch origin/drm-tip 68659914943f drm/i915: Move the priotree struct to its own heade

Re: [Intel-gfx] [PATCH v2 1/3] drm/i915: Move the priotree struct to its own headers

2018-04-18 Thread Joonas Lahtinen
Quoting Chris Wilson (2018-04-17 17:31:30) > Over time the priotree has grown from a sorted list to a more > complicated structure for propagating constraints along the dependency > chain to try and resolve priority inversion. Start to segregate this > information from the rest of the request/fence

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/crc: make locking and source check more robust

2018-04-18 Thread Patchwork
== Series Details == Series: drm/i915/crc: make locking and source check more robust URL : https://patchwork.freedesktop.org/series/41821/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4063 -> Patchwork_8718 = == Summary - FAILURE == Serious unknown changes coming with P

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Chris Wilson
Quoting Joonas Lahtinen (2018-04-18 10:10:17) > Quoting Chris Wilson (2018-04-17 20:06:38) > > The old wait_on_atomic_t used a custom callback to perform the > > schedule(), which used my return semantics of reporting an error code on > > timeout. wait_var_event_timeout() uses the schedule() return

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Don't use -ETIMEDOUT from inside a test

2018-04-18 Thread Joonas Lahtinen
Quoting Chris Wilson (2018-04-17 17:32:04) > -ETIMEDOUT is reserved in the selftests for use by igt_timeout, and the > errno is magically handled by the test runner to break from inside the > test loop without propagating back to userspace as a failure. So convert > the -ETIMEDOUT from wait_var_eve

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Fix error checking for wait_var_timeout

2018-04-18 Thread Joonas Lahtinen
Quoting Chris Wilson (2018-04-17 20:06:38) > The old wait_on_atomic_t used a custom callback to perform the > schedule(), which used my return semantics of reporting an error code on > timeout. wait_var_event_timeout() uses the schedule() return semantics > of reporting the remaining jiffies (1 if

Re: [Intel-gfx] [PATCH] drm/i915/fbdev: Enable late fbdev initial configuration

2018-04-18 Thread Chris Wilson
Quoting Souza, Jose (2018-04-18 01:07:16) > On Wed, 2018-04-18 at 00:44 +0100, Chris Wilson wrote: > > Quoting José Roberto de Souza (2018-04-17 23:34:18) > > > If the initial fbdev configuration(intel_fbdev_initial_config()) > > > runs and > > > there still no sink connected it will cause > > > dr

Re: [Intel-gfx] [CI i-g-t 1/2] tests/gem_exec_latency: New subtests for checking submission from RT tasks

2018-04-18 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-04-17 09:41:11) > From: Tvrtko Ursulin > > We want to make sure RT tasks which use a lot of CPU times can submit > batch buffers with roughly the same latency (and certainly not worse) > compared to normal tasks. > > Signed-off-by: Tvrtko Ursulin > Cc: Chris Wilson

Re: [Intel-gfx] [PATCH] drm/i915/audio: Fix audio detection issue on GLK

2018-04-18 Thread Jani Nikula
On Wed, 18 Apr 2018, "Singh, Gaurav K" wrote: > On 4/17/2018 11:58 PM, Du,Wenkai wrote: >> >> On 4/17/2018 11:22 AM, Gaurav K Singh wrote: >>> On Geminilake, sometimes audio card is not getting >>> detected after reboot. This is a spurious issue happening on >>> Geminilake. HW codec and HD audio c

[Intel-gfx] [PATCH] drm/i915: Wait for vblank after register read

2018-04-18 Thread Mika Kahola
When reading out CRC's we wait for a vblank on intel_dp_sink_crc_start() function. When we start reading out CRC's in intel_dp_sink_crc() loop we first wait for a vblank yielding that all in all we end up waiting two vblanks on the first iteration round. Therefore, let's move the intel_wait_for_vb

[Intel-gfx] [PATCH v2 2/2] i915: content-type property for HDMI connector

2018-04-18 Thread StanLis
From: Stanislav Lisovskiy Added encoding of drm content_type property from drm_connector_state within AVI infoframe in order to properly handle external HDMI TV content-type setting. Signed-off-by: Stanislav Lisovskiy --- drivers/gpu/drm/i915/intel_atomic.c | 1 + drivers/gpu/drm/i915/intel_hd

[Intel-gfx] [PATCH v2 0/2] Enabling content-type setting for HDMI displays.

2018-04-18 Thread StanLis
From: Stanislav Lisovskiy Added content type setting property to drm_connector(part 1) and enabled transmitting it with HDMI AVI infoframes for i915(part 2). rev 2: Moved helper function which attaches content type property to the drm core, as was suggested. Removed redundant connector state ini

[Intel-gfx] [PATCH v2 1/2] drm: content-type property for HDMI connector

2018-04-18 Thread StanLis
From: Stanislav Lisovskiy Added content_type property to drm_connector_state in order to properly handle external HDMI TV content-type setting. Signed-off-by: Stanislav Lisovskiy --- Documentation/gpu/kms-properties.csv | 1 + drivers/gpu/drm/drm_atomic.c | 4 +++ drivers/gpu/drm/drm

<    1   2