Re: [Intel-gfx] [PATCH v2 1/2] drm/panel: panel-innolux: drop unused variable

2019-05-27 Thread Linus Walleij
On Sun, May 26, 2019 at 8:05 PM Sam Ravnborg wrote: > The num_supplies variable is not used, delete it. > Build tested. > > Signed-off-by: Sam Ravnborg > Cc: Thierry Reding > Cc: David Airlie > Cc: Daniel Vetter Reviewed-by: Linus Walleij Yours, Linus Walleij __

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: adding state checker for gamma lut values (rev10)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: adding state checker for gamma lut values (rev10) URL : https://patchwork.freedesktop.org/series/58039/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6148_full -> Patchwork_13107_full

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6) URL : https://patchwork.freedesktop.org/series/61047/ State : success == Summary == CI Bug Log - changes from CI_DRM_6148_full -> Patchwork_13106_full

Re: [Intel-gfx] [PATCH 2/5] drm/i915/perf: allow holding preemption on filtered ctx

2019-05-27 Thread Lionel Landwerlin
On 24/05/2019 11:07, Chris Wilson wrote: Quoting Lionel Landwerlin (2019-05-24 10:51:49) On 24/05/2019 10:42, Chris Wilson wrote: Quoting Lionel Landwerlin (2019-05-24 10:28:16) On 21/05/2019 17:36, Chris Wilson wrote: Quoting Lionel Landwerlin (2019-05-21 15:08:52) diff --git a/drivers/gpu/

[Intel-gfx] ✗ Fi.CI.BAT: failure for GuC 32.0.3 (rev6)

2019-05-27 Thread Patchwork
== Series Details == Series: GuC 32.0.3 (rev6) URL : https://patchwork.freedesktop.org/series/58760/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6150 -> Patchwork_13108 Summary --- **FAILURE** Serious unknown ch

[Intel-gfx] [PATCH v5 16/17] drm/i915/huc: Define HuC firmware version for Icelake

2019-05-27 Thread Michal Wajdeczko
Define HuC firmware version for Icelake. v2: 8.4.3238 is now available Signed-off-by: Michal Wajdeczko Cc: Daniele Ceraolo Spurio Cc: Joonas Lahtinen Cc: Anusha Srivatsa Cc: Tony Ye Reviewed-by: Tony Ye --- drivers/gpu/drm/i915/intel_huc_fw.c | 12 1 file changed, 12 insertion

[Intel-gfx] [PATCH v5 08/17] drm/i915/guc: New GuC interrupt register for Gen11

2019-05-27 Thread Michal Wajdeczko
Gen11 defines new more flexible Host-to-GuC interrupt register. Now the host can write any 32-bit payload to trigger an interrupt and GuC can additionally read this payload from the register. Current GuC firmware ignores the payload so we just write 0. Bspec: 21043 Signed-off-by: Michal Wajdeczko

[Intel-gfx] [PATCH v5 10/17] drm/i915/huc: New HuC status register for Gen11

2019-05-27 Thread Michal Wajdeczko
Gen11 defines new register for checking HuC authentication status. Look into the right register and bit. v2: use reg/mask/value instead of dedicated functions (Daniele) BSpec: 19686 Signed-off-by: Michal Wajdeczko Cc: Joonas Lahtinen Cc: Rodrigo Vivi Cc: Tony Ye Cc: Vinay Belgaumkar Cc: Joh

[Intel-gfx] [PATCH v5 02/17] drm/i915/guc: Don't allow GuC submission

2019-05-27 Thread Michal Wajdeczko
Due to the upcoming changes to the GuC ABI interface, we must disable GuC submission mode until final ABI will be available on all GuC firmwares. To avoid regressions on systems configured to run with no longer supported configuration "enable_guc=3" or "enable_guc=1" clear GuC submission bit. v2:

[Intel-gfx] [PATCH v5 09/17] drm/i915/guc: New GuC scratch registers for Gen11

2019-05-27 Thread Michal Wajdeczko
Gen11 adds new set of scratch registers that can be used for MMIO based Host-to-Guc communication. Due to limited number of these registers it is expected that host will use them only for command transport buffers (CTB) communication setup if one is available. Bspec: 21044 Signed-off-by: Michal W

[Intel-gfx] [PATCH v5 03/17] drm/i915/guc: Updates for GuC 32.0.3 firmware

2019-05-27 Thread Michal Wajdeczko
New GuC 32.0.3 firmware made many changes around its ABI that require driver updates: * FW release version numbering schema now includes patch number * FW release version encoding in CSS header * Boot parameters * Suspend/resume protocol * Sample-forcewake command * Additional Data Structures (ADS

[Intel-gfx] [PATCH v5 13/17] drm/i915/guc: Update GuC CTB response definition

2019-05-27 Thread Michal Wajdeczko
Current GuC firmwares identify response message in a different way. v2: update comments for other H2G bits (Daniele) Signed-off-by: Michal Wajdeczko Cc: Daniele Ceraolo Spurio Cc: Kelvin Gardiner Cc: John Spotswood Reviewed-by: Daniele Ceraolo Spurio --- drivers/gpu/drm/i915/intel_guc_ct.c

[Intel-gfx] [PATCH v5 17/17] HAX: Turn on GuC/HuC auto mode

2019-05-27 Thread Michal Wajdeczko
Run GuC, run! Signed-off-by: Michal Wajdeczko --- drivers/gpu/drm/i915/i915_params.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/i915_params.h b/drivers/gpu/drm/i915/i915_params.h index 3f14e9881a0d..e28ae23de516 100644 --- a/drivers/gpu/drm/i915/i91

[Intel-gfx] [PATCH v5 04/17] drm/i915/guc: Reset GuC ADS during sanitize

2019-05-27 Thread Michal Wajdeczko
GuC stores some data in there, which might be stale after a reset. Reinitialize whole ADS in case any part of it was corrupted during previous GuC run. v2: s/reinit/init, update functions descriptions (Tomek/Michal) v3: reset ADS right before fw upload Signed-off-by: Michal Wajdeczko Cc: Daniele

[Intel-gfx] [PATCH v5 05/17] drm/i915/guc: Always ask GuC to update power domain states

2019-05-27 Thread Michal Wajdeczko
With newer GuC firmware it is always ok to ask GuC to update power domain states. Make it an unconditional initialization step. Signed-off-by: Michal Wajdeczko Cc: Daniele Ceraolo Spurio Cc: John Spotswood Reviewed-by: Daniele Ceraolo Spurio Reviewed-by: John Spotswood --- drivers/gpu/drm/i9

[Intel-gfx] [PATCH v5 01/17] drm/i915/guc: Change platform default GuC mode

2019-05-27 Thread Michal Wajdeczko
Today our most desired GuC configuration is to only enable HuC if it is available (as we need authenticated HuC firmware to enable all media codecs on the hardware) and we really don't care about having GuC submission enabled. Change platform default GuC mode to match our goal, but note that we st

[Intel-gfx] [PATCH v5 15/17] drm/i915/guc: Define GuC firmware version for Icelake

2019-05-27 Thread Michal Wajdeczko
Define GuC firmware version for Icelake. Signed-off-by: Michal Wajdeczko Cc: Daniele Ceraolo Spurio Cc: Joonas Lahtinen Cc: Rodrigo Vivi Cc: Anusha Srivatsa Reviewed-by: Anusha Srivatsa --- drivers/gpu/drm/i915/intel_guc_fw.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/

[Intel-gfx] [PATCH v5 14/17] drm/i915/guc: Enable GuC CTB communication on Gen11

2019-05-27 Thread Michal Wajdeczko
Gen11 GuC firmware expects H2G command messages to be sent over CTB (command transport buffers). Signed-off-by: Michal Wajdeczko Cc: Daniele Ceraolo Spurio Cc: Joonas Lahtinen Cc: John Spotswood Reviewed-by: Daniele Ceraolo Spurio --- drivers/gpu/drm/i915/i915_pci.c | 1 + 1 file changed, 1

[Intel-gfx] [PATCH v5 11/17] drm/i915/guc: Create vfuncs for the GuC interrupts control functions

2019-05-27 Thread Michal Wajdeczko
From: Oscar Mateo Controlling and handling of the GuC interrupts is Gen specific. Create virtual functions to avoid redundant runtime Gen checks. Gen-specific versions of these functions will follow. v2: move vfuncs to struct guc (Daniele) v3: rebased Signed-off-by: Oscar Mateo Signed-off-by:

[Intel-gfx] [PATCH v5 12/17] drm/i915/guc: Correctly handle GuC interrupts on Gen11

2019-05-27 Thread Michal Wajdeczko
From: Oscar Mateo Starting Gen11 GuC shares interrupt registers with SG unit instead of PM. But for now we don't care about SG interrupts. v2: (Chris) v3: rebased (Michal) v4: more bspec pages, use macros, update commit msg (Michal Wi) Bspec: 19820, 19840, 19841, 20176 Signed-off-by: Oscar Mat

[Intel-gfx] [PATCH v5 00/17] GuC 32.0.3

2019-05-27 Thread Michal Wajdeczko
New GuC firmwares (for SKL, BXT, KBL, GLK, ICL) with updated ABI interface. v2: only HuC authentication is supported v3: never allow to turn on GuC submission mode v4: rebased + newer HuC + GLK v5: squashed + last minutes small fixups Cc: Daniele Ceraolo Spurio Cc: Joonas Lahtinen Cc: Martin P

[Intel-gfx] [PATCH v5 07/17] drm/i915/huc: Define HuC firmware version for Geminilake

2019-05-27 Thread Michal Wajdeczko
Define HuC firmware version for Geminilake. Signed-off-by: Michal Wajdeczko Cc: Daniele Ceraolo Spurio Cc: Joonas Lahtinen Cc: Anusha Srivatsa Cc: Tony Ye Reviewed-by: Anusha Srivatsa --- drivers/gpu/drm/i915/intel_huc_fw.c | 12 1 file changed, 12 insertions(+) diff --git a/d

[Intel-gfx] [PATCH v5 06/17] drm/i915/guc: Define GuC firmware version for Geminilake

2019-05-27 Thread Michal Wajdeczko
Define GuC firmware version for Geminilake. Signed-off-by: Michal Wajdeczko Cc: Daniele Ceraolo Spurio Cc: Anusha Srivatsa Reviewed-by: Anusha Srivatsa --- drivers/gpu/drm/i915/intel_guc_fw.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/gpu/drm/i915/intel_guc_fw.c

Re: [Intel-gfx] [PATCH v2 0/7] drm: make headers self-contained and drop drmP.h

2019-05-27 Thread Sam Ravnborg
On Mon, May 27, 2019 at 08:18:35AM +0200, Daniel Vetter wrote: > On Sun, May 26, 2019 at 07:35:28PM +0200, Sam Ravnborg wrote: > > While removing use of drmP.h from files in drm/* I > > noticed that I had to add the same include files due to > > dependencies in the header files. > > > > It is bett

Re: [Intel-gfx] [PATCH v6 2/2] drm/i915: Make sure we have enough memory bandwidth on ICL

2019-05-27 Thread Ville Syrjälä
On Fri, May 24, 2019 at 06:36:14PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > ICL has so many planes that it can easily exceed the maximum > effective memory bandwidth of the system. We must therefore check > that we don't exceed that limit. > > The algorithm is very magic number heav

[Intel-gfx] [RFC PATCH] drm/i915: i9xx_read_luts() can be static

2019-05-27 Thread kbuild test robot
Fixes: 14dcd98a43c8 ("drm/i915: Extract i9xx_read_luts()") Signed-off-by: kbuild test robot --- intel_color.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/intel_color.c b/drivers/gpu/drm/i915/intel_color.c index e8d8167..bf92365 100644 --- a/driver

Re: [Intel-gfx] [v7][PATCH 04/12] drm/i915: Extract i9xx_read_luts()

2019-05-27 Thread kbuild test robot
://github.com/0day-ci/linux/commits/Swati-Sharma/drm-i915-adding-state-checker-for-gamma-lut-values/20190527-214948 base: git://anongit.freedesktop.org/drm-intel for-linux-next reproduce: # apt-get install sparse # sparse version: v0.6.1-rc1-7-g2b96cd8-dirty make ARCH=x86_64

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Daniel Vetter
On Mon, May 27, 2019 at 4:01 PM Thomas Hellstrom wrote: > > On 5/27/19 3:16 PM, Daniel Vetter wrote: > > On Mon, May 27, 2019 at 02:39:18PM +0200, Thomas Hellstrom wrote: > >> On 5/27/19 10:17 AM, Emil Velikov wrote: > >>> From: Emil Velikov > >>> > >>> There are cases (in mesa and applications)

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: adding state checker for gamma lut values (rev10)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: adding state checker for gamma lut values (rev10) URL : https://patchwork.freedesktop.org/series/58039/ State : success == Summary == CI Bug Log - changes from CI_DRM_6148 -> Patchwork_13107 Summary --

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/icl: Fix AUX-B HW not done issue w/o AUX-A

2019-05-27 Thread Imre Deak
On Mon, May 27, 2019 at 06:50:14AM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/icl: Fix AUX-B HW not done issue w/o AUX-A > URL : https://patchwork.freedesktop.org/series/61123/ > State : failure Thanks for the review pushed to -dinq. > > == Summary == > > CI Bug Log

Re: [Intel-gfx] [PATCH v4 17/22] drm/i915/guc: Correctly handle GuC interrupts on Gen11

2019-05-27 Thread Michał Winiarski
On Thu, May 23, 2019 at 11:30:44PM +, Michal Wajdeczko wrote: > From: Oscar Mateo > > The GuC interrupts now get their own interrupt vector (instead of > sharing a register with the PM interrupts) so handle appropriately. > > v2: (Chris) > v3: rebased (Michal) > Bspec: 19820 Bspec: 19820, 1

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: adding state checker for gamma lut values (rev10)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: adding state checker for gamma lut values (rev10) URL : https://patchwork.freedesktop.org/series/58039/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.5.2 Commit: drm/i915: Introduce vfunc read_luts() to create hw lut Okay!

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Thomas Hellstrom
On 5/27/19 3:16 PM, Daniel Vetter wrote: On Mon, May 27, 2019 at 02:39:18PM +0200, Thomas Hellstrom wrote: On 5/27/19 10:17 AM, Emil Velikov wrote: From: Emil Velikov There are cases (in mesa and applications) where one would open the primary node without properly authenticating the client.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: adding state checker for gamma lut values (rev10)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: adding state checker for gamma lut values (rev10) URL : https://patchwork.freedesktop.org/series/58039/ State : warning == Summary == $ dim checkpatch origin/drm-tip d7ec7acfa25a drm/i915: Introduce vfunc read_luts() to create hw lut 729d4500e37f drm/i915

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6) URL : https://patchwork.freedesktop.org/series/61047/ State : success == Summary == CI Bug Log - changes from CI_DRM_6148 -> Patchwork_13106 Summary -

[Intel-gfx] [v7][PATCH 02/12] drm/i915: Enable intel_color_get_config()

2019-05-27 Thread Swati Sharma
In this patch, intel_color_get_config() is enabled and support for read_luts() will be added platform by platform incrementally in the follow-up patches. v4: -Renamed intel_get_color_config to intel_color_get_config [Jani] -Added the user early on such that support for get_color_config()

[Intel-gfx] [v7][PATCH 05/12] drm/i915: Extract chv_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, hw gamma and degamma blob is created for cherryview. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob instead of assigning it internally within the function [Ville] -Renamed function cherryvi

[Intel-gfx] [v7][PATCH 10/12] drm/i915: Extract ivb_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, gamma and degamma hw blobs are created for IVB. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob instead of assigning it internally within the function [Ville] -Renamed ivb_get_color_config() to iv

[Intel-gfx] [v7][PATCH 00/12] drm/i915: adding state checker for gamma lut values

2019-05-27 Thread Swati Sharma
In this patch series, added state checker to validate gamma and will be extended to validate degamma lut values aswell. This reads hardware state, and compares the originally requested state to the state read from hardware. v1: -Implementation done for legacy platforms (removed all the placeh

[Intel-gfx] [v7][PATCH 06/12] drm/i915: Extract i965_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, hw gamma blob is created for i965. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob instead of assigning it internally within the function [Ville] -Renamed i965_get_color_config() to i965_read_lut(

[Intel-gfx] [v7][PATCH 12/12] FOR_TESTING_ONLY: Print rgb values of hw and sw blobs

2019-05-27 Thread Swati Sharma
Signed-off-by: Swati Sharma --- drivers/gpu/drm/i915/intel_color.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/i915/intel_color.c b/drivers/gpu/drm/i915/intel_color.c index 061bdbf..31e5a44 100644 --- a/drivers/gpu/drm/i915/intel_color.c +++ b/drivers/gpu/drm/i915/intel

[Intel-gfx] [v7][PATCH 08/12] drm/i915: Extract glk_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, gamma and degamma hw blobs are created for GLK. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob instead of assigning it internally within the function [Ville] -Renamed glk_get_color_config() to gl

[Intel-gfx] [v7][PATCH 09/12] drm/i915: Extract bdw_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, gamma and degamma hw blobs are created for BDW. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob instead of assigning it internally within the function [Ville] -Renamed bdw_get_color_config() to bd

[Intel-gfx] [v7][PATCH 11/12] drm/i915: Extract ilk_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, hw gamma blob is created for ILK. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob instead of assigning it internally within the function [Ville] -Renamed ilk_get_color_config() to ilk_read_luts()

[Intel-gfx] [v7][PATCH 07/12] drm/i915: Extract icl_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, gamma hw blobs are created for ICL. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob instead of assigning it internally within the function [Ville] -Renamed icl_get_color_config() to icl_read_luts(

[Intel-gfx] [v7][PATCH 04/12] drm/i915: Extract i9xx_read_luts()

2019-05-27 Thread Swati Sharma
In this patch, hw gamma blob is created for the legacy gamma. Also, function intel_color_lut_pack is added to convert hw value with given bit_precision to lut property val. v4: -No need to initialize *blob [Jani] -Removed right shifts [Jani] -Dropped dev local var [Jani] v5: -Returned blob

[Intel-gfx] [v7][PATCH 03/12] drm/i915: Add intel_color_lut_equal() to compare hw and sw gamma/degamma lut values

2019-05-27 Thread Swati Sharma
v3: -Rebase v4: -Renamed intel_compare_color_lut() to intel_color_lut_equal() [Jani] -Added the default label above the correct label [Jani] -Corrected smatch warn "variable dereferenced before check" [Dan Carpenter] v5: -Added condition (!blob1 && !blob2) return true [Jani] -Called PIP

[Intel-gfx] [v7][PATCH 01/12] drm/i915: Introduce vfunc read_luts() to create hw lut

2019-05-27 Thread Swati Sharma
In this patch, a vfunc read_luts() is introduced to create a hw lut i.e. lut having values read from gamma/degamma registers which will later be used to compare with sw lut to validate gamma/degamma lut values. v3: -Rebase v4: -Renamed intel_get_color_config to intel_color_get_config [Jani] -W

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Daniel Vetter
On Mon, May 27, 2019 at 02:39:18PM +0200, Thomas Hellstrom wrote: > On 5/27/19 10:17 AM, Emil Velikov wrote: > > From: Emil Velikov > > > > There are cases (in mesa and applications) where one would open the > > primary node without properly authenticating the client. > > > > Sometimes we don't

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6) URL : https://patchwork.freedesktop.org/series/61047/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.5.2 Commit: drm/i915: Keep user GGTT alive for a minimum of 250ms + +driv

Re: [Intel-gfx] [PATCH] drm/i915/icl: Fix AUX-B HW not done issue w/o AUX-A

2019-05-27 Thread Ville Syrjälä
On Fri, May 24, 2019 at 08:35:32PM +0300, Imre Deak wrote: > Atm AUX-B transfers can fail with the following error if AUX-A is not > enabled: > > [ 594.594108] [drm:intel_dp_aux_xfer [i915]] dp_aux_ch timeout status > 0x7c2003ff > [ 594.615854] [drm:intel_dp_aux_xfer [i915]] *ERROR* dp aux hw d

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: Keep user GGTT alive for a minimum of 250ms (rev6) URL : https://patchwork.freedesktop.org/series/61047/ State : warning == Summary == $ dim checkpatch origin/drm-tip fbf134649c9d drm/i915: Keep user GGTT alive for a minimum of 250ms -:196: CHECK:UNCOMMEN

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Emil Velikov
On 2019/05/27, Thomas Hellstrom wrote: > On 5/27/19 10:17 AM, Emil Velikov wrote: > > From: Emil Velikov > > > > There are cases (in mesa and applications) where one would open the > > primary node without properly authenticating the client. > > > > Sometimes we don't check if the authentication

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/panel: drmP.h removal + small fix

2019-05-27 Thread Patchwork
== Series Details == Series: drm/panel: drmP.h removal + small fix URL : https://patchwork.freedesktop.org/series/61157/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13104_full Summary --- **F

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Thomas Hellstrom
On 5/27/19 10:17 AM, Emil Velikov wrote: From: Emil Velikov There are cases (in mesa and applications) where one would open the primary node without properly authenticating the client. Sometimes we don't check if the authentication succeeds, but there's also cases we simply forget to do it. T

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Koenig, Christian
Am 27.05.19 um 14:10 schrieb Emil Velikov: > On 2019/05/27, Christian König wrote: >> Am 27.05.19 um 10:17 schrieb Emil Velikov: >>> From: Emil Velikov >>> >>> There are cases (in mesa and applications) where one would open the >>> primary node without properly authenticating the client. >>> >>> S

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Emil Velikov
On 2019/05/27, Christian König wrote: > Am 27.05.19 um 10:17 schrieb Emil Velikov: > > From: Emil Velikov > > > > There are cases (in mesa and applications) where one would open the > > primary node without properly authenticating the client. > > > > Sometimes we don't check if the authenticatio

[Intel-gfx] ✓ Fi.CI.IGT: success for drm: make headers self-contained and drop drmP.h

2019-05-27 Thread Patchwork
== Series Details == Series: drm: make headers self-contained and drop drmP.h URL : https://patchwork.freedesktop.org/series/61156/ State : success == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13103_full Summary ---

Re: [Intel-gfx] [PATCH 05/13] drm/i915: drop DRM_AUTH from DRM_RENDER_ALLOW ioctls

2019-05-27 Thread Emil Velikov
On 2019/05/27, Jani Nikula wrote: > On Mon, 27 May 2019, Emil Velikov wrote: > > From: Emil Velikov > > > > The authentication can be circumvented, by design, by using the render > > node. > > > > From the driver POV there is no distinction between primary and render > > nodes, thus we can drop t

Re: [Intel-gfx] [PATCH v4 02/22] drm/i915/guc: Don't allow GuC submission

2019-05-27 Thread Michal Wajdeczko
On Mon, 27 May 2019 13:40:25 +0200, Joonas Lahtinen wrote: Quoting Michal Wajdeczko (2019-05-24 02:30:29) Due to the upcoming changes to the GuC ABI interface, we must disable GuC submission mode until final ABI will be available on all GuC firmwares. To avoid regressions on systems configu

Re: [Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Christian König
Am 27.05.19 um 10:17 schrieb Emil Velikov: From: Emil Velikov There are cases (in mesa and applications) where one would open the primary node without properly authenticating the client. Sometimes we don't check if the authentication succeeds, but there's also cases we simply forget to do it.

Re: [Intel-gfx] [PATCH 00/33] fbcon notifier begone!

2019-05-27 Thread Daniel Vetter
On Mon, May 27, 2019 at 9:17 AM Daniel Vetter wrote: > > On Sat, May 25, 2019 at 07:19:28PM +0200, Sam Ravnborg wrote: > > Hi Daniel. > > > > Good work, nice cleanup all over. > > > > A few comments to a few patches - not something that warrant a > > new series to be posted as long as it is fixed

[Intel-gfx] [CI] drm/i915: Keep user GGTT alive for a minimum of 250ms

2019-05-27 Thread Chris Wilson
Do not allow runtime pm autosuspend to remove userspace GGTT mmaps too quickly. For example, igt sets the autosuspend delay to 0, and so we immediately attempt to perform runtime suspend upon releasing the wakeref. Unfortunately, that involves tearing down GGTT mmaps as they require an active devic

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Keep user GGTT alive for a minimum of 250ms (rev5)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: Keep user GGTT alive for a minimum of 250ms (rev5) URL : https://patchwork.freedesktop.org/series/61047/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6147 -> Patchwork_13105 Summary -

Re: [Intel-gfx] [PATCH v4 02/22] drm/i915/guc: Don't allow GuC submission

2019-05-27 Thread Joonas Lahtinen
Quoting Michal Wajdeczko (2019-05-24 02:30:29) > Due to the upcoming changes to the GuC ABI interface, we must > disable GuC submission mode until final ABI will be available > on all GuC firmwares. > > To avoid regressions on systems configured to run with no longer > supported configuration "ena

Re: [Intel-gfx] [PATCH v4 01/22] drm/i915/guc: Change platform default GuC mode

2019-05-27 Thread Joonas Lahtinen
Quoting Michal Wajdeczko (2019-05-24 02:30:28) > Today our most desired GuC configuration is to only enable HuC > if it is available and we really don't care about GuC submission. > Change platform default GuC mode to match our desire. You should amend here that the HuC authentication is needed to

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Keep user GGTT alive for a minimum of 250ms (rev5)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: Keep user GGTT alive for a minimum of 250ms (rev5) URL : https://patchwork.freedesktop.org/series/61047/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.5.2 Commit: drm/i915: Keep user GGTT alive for a minimum of 250ms + +driv

Re: [Intel-gfx] [PATCH v2] drm/i915/huc: Don't try to check HuC status if it's not loaded

2019-05-27 Thread Michal Wajdeczko
On Fri, 24 May 2019 15:29:22 +0200, Michal Wajdeczko wrote: On Fri, 24 May 2019 15:10:58 +0200, Joonas Lahtinen wrote: Quoting Ye, Tony (2019-05-22 14:32:41) From UMD perspective, when HuC is not working as expected, usually we look into the kernel log and i915_huc_load_status debugfs

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Keep user GGTT alive for a minimum of 250ms (rev5)

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: Keep user GGTT alive for a minimum of 250ms (rev5) URL : https://patchwork.freedesktop.org/series/61047/ State : warning == Summary == $ dim checkpatch origin/drm-tip 6e1b0f65e952 drm/i915: Keep user GGTT alive for a minimum of 250ms -:195: CHECK:UNCOMMEN

[Intel-gfx] [CI] drm/i915: Keep user GGTT alive for a minimum of 250ms

2019-05-27 Thread Chris Wilson
Do not allow runtime pm autosuspend to remove userspace GGTT mmaps too quickly. For example, igt sets the autosuspend delay to 0, and so we immediately attempt to perform runtime suspend upon releasing the wakeref. Unfortunately, that involves tearing down GGTT mmaps as they require an active devic

[Intel-gfx] ✓ Fi.CI.IGT: success for fbcon notifier begone! (rev4)

2019-05-27 Thread Patchwork
== Series Details == Series: fbcon notifier begone! (rev4) URL : https://patchwork.freedesktop.org/series/60843/ State : success == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13102_full Summary --- **SUCCESS**

Re: [Intel-gfx] [PATCH 24/33] Revert "backlight/fbcon: Add FB_EVENT_CONBLANK"

2019-05-27 Thread Bartlomiej Zolnierkiewicz
On 5/24/19 5:28 PM, Daniel Vetter wrote: > Hi Daniel, > > On Fri, May 24, 2019 at 3:14 PM Daniel Thompson > wrote: >> >> On Fri, May 24, 2019 at 10:53:45AM +0200, Daniel Vetter wrote: >>> This reverts commit 994efacdf9a087b52f71e620b58dfa526b0cf928. >>> >>> The justification is that if hw blanki

Re: [Intel-gfx] [PATCH v2 2/2] drm/panel: drop drmP.h usage

2019-05-27 Thread Sam Ravnborg
On Mon, May 27, 2019 at 11:11:18AM +0200, Linus Walleij wrote: > On Sun, May 26, 2019 at 8:05 PM Sam Ravnborg wrote: > > > Drop use of the deprecated drmP.h header file. > > > > While touching the list of include files: > > - Divide include files in blocks of linux/* video/* drm/* etc. > > Be c

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915: Make intel_fuzzy_clock_check available outside of intel_display.c

2019-05-27 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: Make intel_fuzzy_clock_check available outside of intel_display.c URL : https://patchwork.freedesktop.org/series/61127/ State : success == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13098_full ==

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/ehl: Introduce Mule Creek Canyon PCH

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915/ehl: Introduce Mule Creek Canyon PCH URL : https://patchwork.freedesktop.org/series/61137/ State : success == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13101_full Summary --

Re: [Intel-gfx] [PATCH V3 i-g-t] lib: Drop __kms_addfb() wrapper

2019-05-27 Thread Chris Wilson
Quoting Rodrigo Siqueira (2019-05-27 02:19:51) > The function __kms_addfb() and drmModeAddFB2WithModifiers() have a > similar code. Due to this similarity, this commit replaces all the > occurrences of __kms_addfb() by drmModeAddFB2WithModifiers() and adds > the required adaptations. No. There is

Re: [Intel-gfx] [PATCH] drm/i915: make REG_BIT() and REG_GENMASK() work with variables

2019-05-27 Thread Jani Nikula
On Fri, 24 May 2019, Chris Wilson wrote: > Quoting Jani Nikula (2019-05-24 19:52:53) >> REG_BIT() and REG_GENMASK() were intended to work with both constant >> expressions and otherwise, with the former having extra compile time >> checks for the bit ranges. Incredibly, the result of >> __builtin_

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gtt: set err to -ENOMEM on memory allocation failure

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915/gtt: set err to -ENOMEM on memory allocation failure URL : https://patchwork.freedesktop.org/series/61134/ State : success == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13100_full

[Intel-gfx] [PATCH i-g-t] benchmarks/gem_wsim: Tidy manual sizeof VLA calculations

2019-05-27 Thread Chris Wilson
We can use offsetof for the same effect, much tidier with no dummy locals. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin --- benchmarks/gem_wsim.c | 15 ++- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/benchmarks/gem_wsim.c b/benchmarks/gem_wsim.c index db19925b1..

Re: [Intel-gfx] [PATCH v2 2/2] drm/panel: drop drmP.h usage

2019-05-27 Thread Linus Walleij
On Sun, May 26, 2019 at 8:05 PM Sam Ravnborg wrote: > Drop use of the deprecated drmP.h header file. > > While touching the list of include files: > - Divide include files in blocks of linux/* video/* drm/* etc. > Be consistent in the order of the blocks > - Sort individual blocks of include fi

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: make REG_BIT() and REG_GENMASK() work with variables

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915: make REG_BIT() and REG_GENMASK() work with variables URL : https://patchwork.freedesktop.org/series/61129/ State : success == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13099_full ===

Re: [Intel-gfx] [PATCH 05/13] drm/i915: drop DRM_AUTH from DRM_RENDER_ALLOW ioctls

2019-05-27 Thread Jani Nikula
On Mon, 27 May 2019, Emil Velikov wrote: > From: Emil Velikov > > The authentication can be circumvented, by design, by using the render > node. > > From the driver POV there is no distinction between primary and render > nodes, thus we can drop the token. > > Note: the outstanding DRM_AUTH insta

[Intel-gfx] [PATCH i-g-t] prime_vgem: Fix typo in checking for invalid engines

2019-05-27 Thread Chris Wilson
Move the stray ')' from gem_can_store_dword(exec_id) | exec_flags to gem_can_store_dword(exec_id | exec_flags) Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110764 Signed-off-by: Chris Wilson --- tests/prime_vgem.c | 8 1 file changed, 4 insertions(+), 4 dele

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Make intel_fuzzy_clock_check available outside of intel_display.c

2019-05-27 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: Make intel_fuzzy_clock_check available outside of intel_display.c URL : https://patchwork.freedesktop.org/series/61127/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13098_full ==

[Intel-gfx] [PATCH 13/13] drm: allow render capable master with DRM_AUTH ioctls

2019-05-27 Thread Emil Velikov
From: Emil Velikov There are cases (in mesa and applications) where one would open the primary node without properly authenticating the client. Sometimes we don't check if the authentication succeeds, but there's also cases we simply forget to do it. The former was a case for Mesa where it did

[Intel-gfx] [PATCH 05/13] drm/i915: drop DRM_AUTH from DRM_RENDER_ALLOW ioctls

2019-05-27 Thread Emil Velikov
From: Emil Velikov The authentication can be circumvented, by design, by using the render node. From the driver POV there is no distinction between primary and render nodes, thus we can drop the token. Note: the outstanding DRM_AUTH instances are: - legacy DRI1 ioctls, which are already neuter

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/kvmgt: Use struct_size() helper

2019-05-27 Thread Patchwork
== Series Details == Series: drm/i915/kvmgt: Use struct_size() helper URL : https://patchwork.freedesktop.org/series/61124/ State : success == Summary == CI Bug Log - changes from CI_DRM_6142_full -> Patchwork_13096_full Summary ---

Re: [Intel-gfx] [PATCH 32/33] staging/olpc_dcon: Add drm conversion to TODO

2019-05-27 Thread Greg KH
On Mon, May 27, 2019 at 09:11:26AM +0200, Daniel Vetter wrote: > On Fri, May 24, 2019 at 10:53:53AM +0200, Daniel Vetter wrote: > > this driver is pretty horrible from a design pov, and needs a complete > > overhaul. Concrete thing that annoys me is that it looks at > > registered_fb, which is an i

Re: [Intel-gfx] [PATCH 14/33] staging/olpc: lock_fb_info can't fail

2019-05-27 Thread Greg KH
On Mon, May 27, 2019 at 09:10:10AM +0200, Daniel Vetter wrote: > On Fri, May 24, 2019 at 10:53:35AM +0200, Daniel Vetter wrote: > > Simply because olpc never unregisters the damn thing. It also > > registers the framebuffer directly by poking around in fbdev > > core internals, so it's all around r

Re: [Intel-gfx] [PATCH 04/33] vt: More locking checks

2019-05-27 Thread Greg Kroah-Hartman
On Mon, May 27, 2019 at 09:08:58AM +0200, Daniel Vetter wrote: > On Fri, May 24, 2019 at 10:53:25AM +0200, Daniel Vetter wrote: > > I honestly have no idea what the subtle differences between > > con_is_visible, con_is_fg (internal to vt.c) and con_is_bound are. But > > it looks like both vc->vc_di

Re: [Intel-gfx] [PATCH 00/33] fbcon notifier begone!

2019-05-27 Thread Daniel Vetter
On Sat, May 25, 2019 at 07:19:28PM +0200, Sam Ravnborg wrote: > Hi Daniel. > > Good work, nice cleanup all over. > > A few comments to a few patches - not something that warrant a > new series to be posted as long as it is fixed before the patches are > applied. Hm yeah good idea, I'll add that

Re: [Intel-gfx] [PATCH 32/33] staging/olpc_dcon: Add drm conversion to TODO

2019-05-27 Thread Daniel Vetter
On Fri, May 24, 2019 at 10:53:53AM +0200, Daniel Vetter wrote: > this driver is pretty horrible from a design pov, and needs a complete > overhaul. Concrete thing that annoys me is that it looks at > registered_fb, which is an internal thing to fbmem.c and fbcon.c. And > ofc it gets the lifetime ru

Re: [Intel-gfx] [PATCH 14/33] staging/olpc: lock_fb_info can't fail

2019-05-27 Thread Daniel Vetter
On Fri, May 24, 2019 at 10:53:35AM +0200, Daniel Vetter wrote: > Simply because olpc never unregisters the damn thing. It also > registers the framebuffer directly by poking around in fbdev > core internals, so it's all around rather broken. > > Signed-off-by: Daniel Vetter > Cc: Jens Frederich

Re: [Intel-gfx] [PATCH 04/33] vt: More locking checks

2019-05-27 Thread Daniel Vetter
On Fri, May 24, 2019 at 10:53:25AM +0200, Daniel Vetter wrote: > I honestly have no idea what the subtle differences between > con_is_visible, con_is_fg (internal to vt.c) and con_is_bound are. But > it looks like both vc->vc_display_fg and con_driver_map are protected > by the console_lock, so pro