== Series Details ==
Series: Add support for mipi dsi cmd mode (rev7)
URL : https://patchwork.freedesktop.org/series/69290/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8125 -> Patchwork_16947
Summary
---
**FAILURE*
== Series Details ==
Series: drm/i915/gt: Restrict gen7 w/a batch to Haswell
URL : https://patchwork.freedesktop.org/series/74577/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8120_full -> Patchwork_16925_full
Summary
> -Original Message-
> From: Ville Syrjälä
> Sent: 10 March 2020 21:36
> To: Laxminarayan Bharadiya, Pankaj
>
> Cc: jani.nik...@linux.intel.com; dan...@ffwll.ch; intel-
> g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; airl...@linux.ie;
> maarten.lankho...@linux.intel.com;
On Wed, 11 Mar 2020, Daniele Ceraolo Spurio
wrote:
> uC is a component of the GT, so it makes sense for the uC debugfs files
> to be in the GT folder. A subfolder has been used to keep the same
> structure we have for the code.
>
> v2: use intel_* prefix (Jani), rebase on new gt_debugfs_register_
> -Original Message-
> From: Ville Syrjälä
> Sent: 10 March 2020 21:47
> To: Laxminarayan Bharadiya, Pankaj
>
> Cc: jani.nik...@linux.intel.com; dan...@ffwll.ch; intel-
> g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; airl...@linux.ie;
> maarten.lankho...@linux.intel.com;
== Series Details ==
Series: drm/i915/selftests: Add request throughput measurement to perf (rev2)
URL : https://patchwork.freedesktop.org/series/73930/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8120_full -> Patchwork_16926_full
== Series Details ==
Series: drm/i915/gem: Prefer unlocked engine iteration
URL : https://patchwork.freedesktop.org/series/74582/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8120_full -> Patchwork_16927_full
Summary
-
On 11/03/2020 15:30, Chris Wilson wrote:
@@ -2729,16 +2772,19 @@ static const struct i915_perf_stream_ops
i915_oa_stream_ops = {
static int i915_perf_stream_enable_sync(struct i915_perf_stream *stream)
{
- struct i915_request *rq;
+ struct i915_active *active;
+ int err
Am 12.03.20 um 11:19 schrieb Christoph Hellwig:
On Thu, Mar 12, 2020 at 11:14:22AM +0100, Christian König wrote:
The page pointer is set to NULL and only the DMA address,
length and offset values are valid.
NAK. The only valid way to fill DMA address in scatterlists is
dma_map_sg / dma_map_sg_
Since drm_mm_node are intended to be embedded into larger structs, we
can use the DEBUG_OBJECTS facility to help track the lifetime of the
drm_mm_node and ensure that they are not being used after the containing
object has been freed, along with the usual verification that the
drm_mm_nodes are bein
== Series Details ==
Series: series starting with [01/12] drm/i915/selftests: Add request throughput
measurement to perf
URL : https://patchwork.freedesktop.org/series/74586/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8120_full -> Patchwork_16929_full
=
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: 2bd9e989a5653d4cd710e9dd2b42b0a080f1add8
commit: d3bd37f587b4438d47751d0f1d5aaae3d39bd416 [1296/1354] Merge v5.6-rc5
into drm-next
config: riscv-randconfig-a001-20200312 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.2.0
Am 12.03.20 um 11:47 schrieb Christoph Hellwig:
On Thu, Mar 12, 2020 at 11:31:35AM +0100, Christian König wrote:
[SNIP]
I mean we could come up with a new structure for this, but to me that just
looks like reinventing the wheel. Especially since drivers need to be able
to handle both I/O to syst
== Series Details ==
Series: drm/mm: Use debugobject to track lifetimes
URL : https://patchwork.freedesktop.org/series/74638/
State : failure
== Summary ==
CALLscripts/checksyscalls.sh
CALLscripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
CC
Initially all the generated code was per generation. Eventually we
grouped it into a single file to reuse as much as possible equation
code (this reduce binary size by a factor). So many equations are just
the same from generation to generation.
But this generated file is 200k lines long...
This
Gputop had support for generating mathml figures of the post
processing equations. It's not useful here.
Signed-off-by: Lionel Landwerlin
---
lib/i915/perf-configs/perf-codegen.py | 168 +++---
1 file changed, 17 insertions(+), 151 deletions(-)
diff --git a/lib/i915/perf-con
On 2020-03-11 at 10:02:47 +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Enable non-contiguous pipe fusing
> URL : https://patchwork.freedesktop.org/series/74570/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_8113 -> Patchwork_16920
> ==
Since drm_mm_node are intended to be embedded into larger structs, we
can use the DEBUG_OBJECTS facility to help track the lifetime of the
drm_mm_node and ensure that they are not being used after the containing
object has been freed, along with the usual verification that the
drm_mm_nodes are bein
Add documentation for newly introduced KMS plane and CRTC scaling
filter properties.
changes since RFC:
* Add seperate documention for plane and CRTC.
Signed-off-by: Pankaj Bharadiya
---
Documentation/gpu/drm-kms.rst | 12
1 file changed, 12 insertions(+)
diff --git a/Documentatio
Introduce new plane and CRTC scaling filter properties to allow
userspace to select the driver's default scaling filter or
Nearest-neighbor(NN) filter for upscaling operations on CRTC and
plane.
Drivers can set up this property for a plane by calling
drm_plane_enable_scaling_filter() and for a CRT
This series is the continuation for the RFC that I posted earlier [1]
[1] RFC: https://patchwork.freedesktop.org/series/73884/
Integer scaling (IS) is a nearest-neighbor upscaling technique that
simply scales up the existing pixels by an integer (i.e., whole
number) multiplier. Nearest-neighbor (
On Wed, 11 Mar 2020, Rajat Jain wrote:
> I got a "failed to apply" email from the patchwork. Can you please let
> me know on which branch is it trying to apply it? I have currently
> rebased my patchset to drm-intel-next-queued.
drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip
It's kin
Introduce scaler registers and bit fields needed to configure the
scaling filter in prgrammed mode and configure scaling filter
coefficients.
changes since RFC:
* Parametrize scaler coeffient macros by 'set' (Ville)
Signed-off-by: Shashank Sharma
Signed-off-by: Ankit Nautiyal
Signed-off-by: Pan
GEN >= 10 hardware supports the programmable scaler filter.
Attach scaling filter property for CRTC and plane for GEN >= 10
hardwares and program scaler filter based on the selected filter
type.
Changes since RFC:
* Enable properties for GEN >= 10 platforms (Ville)
* Do not round off the crtc co-
Integer scaling (IS) is a nearest-neighbor upscaling technique that
simply scales up the existing pixels by an integer
(i.e., whole number) multiplier.Nearest-neighbor (NN) interpolation
works by filling in the missing color values in the upscaled image
with that of the coordinate-mapped nearest so
== Series Details ==
Series: drm/i915: Enable non-contiguous pipe fusing
URL : https://patchwork.freedesktop.org/series/74570/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8113 -> Patchwork_16920
Summary
---
**SUCCE
Yes, that's a known issue, #656. Re-reported the results and all good now.
Thanks,
Lakshmi.
-Original Message-
From: Gupta, Anshuman
Sent: Thursday, March 12, 2020 1:09 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Enable
== Series Details ==
Series: series starting with [v2,1/3] lib/i915/perf: remove generation code for
mathml render
URL : https://patchwork.freedesktop.org/series/74641/
State : warning
== Summary ==
Did not get list of undocumented tests for this run, something is wrong!
Other than that, pip
On 11/03/2020 19:54, Francisco Jerez wrote:
Tvrtko Ursulin writes:
On 10/03/2020 22:26, Chris Wilson wrote:
Quoting Francisco Jerez (2020-03-10 21:41:55)
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c
b/drivers/gpu/drm/i915/gt/intel_lrc.c
index b9b3f78f1324..a5d7a80b826d 100644
--- a/dr
During driver unload, we have many asserts that we have released our
bookkeeping structs and are idle. In some cases, these struct are
protected by RCU and we do not release them until after an RCU grace
period.
Reported-by: Maarten Lankhorst
Fixes: 130a95e9098e ("drm/i915/gem: Consolidate ctx->e
From: Tvrtko Ursulin
Allow super long OpenCL workloads which cannot be preempted within
the default timeout to run out of the box.
v2:
* Make it stick out more and apply only to RCS. (Chris)
v3:
* Mention platform override in kconfig. (Joonas)
Signed-off-by: Tvrtko Ursulin
Cc: Chris Wilson
From: Tvrtko Ursulin
Allow super long OpenCL workloads which cannot be preempted within
the default timeout to run out of the box.
v2:
* Make it stick out more and apply only to RCS. (Chris)
v3:
* Mention platform override in kconfig. (Joonas)
Signed-off-by: Tvrtko Ursulin
Cc: Chris Wilson
== Series Details ==
Series: series starting with [v2,1/3] lib/i915/perf: remove generation code for
mathml render
URL : https://patchwork.freedesktop.org/series/74641/
State : success
== Summary ==
CI Bug Log - changes from IGT_5506 -> IGTPW_4298
=
== Series Details ==
Series: drm/mm: Use debugobject to track lifetimes (rev2)
URL : https://patchwork.freedesktop.org/series/74638/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
99485e1feb1b drm/mm: Use debugobject to track lifetimes
-:199: WARNING:TYPO_SPELLING: 'compatiblity
Since drm_mm_node are intended to be embedded into larger structs, we
can use the DEBUG_OBJECTS facility to help track the lifetime of the
drm_mm_node and ensure that they are not being used after the containing
object has been freed, along with the usual verification that the
drm_mm_nodes are bein
On Thu, Mar 12, 2020 at 08:58:42AM +, Laxminarayan Bharadiya, Pankaj wrote:
>
>
> > -Original Message-
> > From: Ville Syrjälä
> > Sent: 10 March 2020 21:36
> > To: Laxminarayan Bharadiya, Pankaj
> >
> > Cc: jani.nik...@linux.intel.com; dan...@ffwll.ch; intel-
> > g...@lists.freedes
> -Original Message-
> From: Tvrtko Ursulin
> Sent: Thursday, March 12, 2020 12:58 PM
> To: Intel-gfx@lists.freedesktop.org
> Cc: Ursulin, Tvrtko ; Chris Wilson wilson.co.uk>; Joonas Lahtinen ; Mrozek,
> Michal ; sta...@vger.kernel.org
> Subject: [PATCH v3] drm/i915/gen12: Disable preempt
== Series Details ==
Series: drm/mm: Use debugobject to track lifetimes (rev2)
URL : https://patchwork.freedesktop.org/series/74638/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8126 -> Patchwork_16949
Summary
---
*
== Series Details ==
Series: Introduce drm scaling filter property (rev2)
URL : https://patchwork.freedesktop.org/series/73883/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
38e9b95fbc63 drm: Introduce plane and CRTC scaling filter properties
-:136: CHECK:PARENTHESIS_ALIGNMENT:
== Series Details ==
Series: drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK only (rev3)
URL : https://patchwork.freedesktop.org/series/71525/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8121_full -> Patchwork_16933_full
===
== Series Details ==
Series: Introduce drm scaling filter property (rev2)
URL : https://patchwork.freedesktop.org/series/73883/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8126 -> Patchwork_16950
Summary
---
**FAIL
Am 11.03.20 um 16:28 schrieb Christoph Hellwig:
On Wed, Mar 11, 2020 at 02:51:53PM +0100, Christian König wrote:
This can be used by drivers to setup P2P DMA between device
memory which is not backed by struct pages.
The drivers of the involved devices are responsible for
setting up and tearing
On Thu, Mar 12, 2020 at 11:14:22AM +0100, Christian König wrote:
> > > The page pointer is set to NULL and only the DMA address,
> > > length and offset values are valid.
> > NAK. The only valid way to fill DMA address in scatterlists is
> > dma_map_sg / dma_map_sg_attr.
>
> How can we then map P
On Thu, Mar 12, 2020 at 11:31:35AM +0100, Christian König wrote:
> But how should we then deal with all the existing interfaces which already
> take a scatterlist/sg_table ?
>
> The whole DMA-buf design and a lot of drivers are build around
> scatterlist/sg_table and to me that actually makes quite
On Wed, Mar 11, 2020 at 02:51:53PM +0100, Christian König wrote:
> This can be used by drivers to setup P2P DMA between device
> memory which is not backed by struct pages.
>
> The drivers of the involved devices are responsible for
> setting up and tearing down DMA addresses as necessary
> using
On 11/03/2020 10:49, Chris Wilson wrote:
Under ideal circumstances, the driver should be able to keep the GPU
fully saturated with work. Measure how close to ideal we get under the
harshest of conditions with no user payload.
v2: Also measure throughput using only one thread.
Signed-off-by: C
On 10/03/2020 11:03, Lionel Landwerlin wrote:
On 09/03/2020 23:10, Umesh Nerlige Ramappa wrote:
On running several back to back perf capture sessions involving closing
and opening the perf stream, invalid OA reports are seen in the
beginning of the OA buffer in some sessions. Fix this by invalid
== Series Details ==
Series: drm/i915/gt: Wait for RCUs frees before asserting idle on unload
URL : https://patchwork.freedesktop.org/series/74645/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8126 -> Patchwork_16951
Summa
Hi Lionel,
Thank you for the patch! Perhaps something to improve:
url:
https://github.com/0day-ci/linux/commits/Lionel-Landwerlin/drm-i915-perf-remove-generated-code/20200307-024544
base: git://anongit.freedesktop.org/drm-intel for-linux-next
If you fix the issue, kindly add following tag
On Thu, Mar 12, 2020 at 09:13:24AM +, Laxminarayan Bharadiya, Pankaj wrote:
>
>
> > -Original Message-
> > From: Ville Syrjälä
> > Sent: 10 March 2020 21:47
> > To: Laxminarayan Bharadiya, Pankaj
> >
> > Cc: jani.nik...@linux.intel.com; dan...@ffwll.ch; intel-
> > g...@lists.freedes
On Tue, Feb 25, 2020 at 12:35:40PM +0530, Pankaj Bharadiya wrote:
> Integer scaling (IS) is a nearest-neighbor upscaling technique that
> simply scales up the existing pixels by an integer (i.e., whole
> number) multiplier. Nearest-neighbor (NN) interpolation works by
> filling in the missing color
== Series Details ==
Series: drm/i915/gen12: Disable preemption timeout (rev4)
URL : https://patchwork.freedesktop.org/series/74526/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8126 -> Patchwork_16952
Summary
---
*
Gen11 onwards PG3 is contains functions for pipe B,
external displays, and VGA. It make sense to add
a power well id with name ICL_DISP_PW_3 rather then
TGL_DISP_PW_3, Also PG3 power well id requires to
know if lpsp is enabled.
Signed-off-by: Anshuman Gupta
---
drivers/gpu/drm/i915/display/intel
New i915_pm_lpsp igt solution approach relies on connector specific
debugfs attribute i915_lpsp_info, it exposes whether an output is
capable of driving lpsp and exposes lpsp enablement info.
Signed-off-by: Anshuman Gupta
---
.../drm/i915/display/intel_display_debugfs.c | 65 +++
This series adds i915_lpsp_info connector debugfs.
Test-with: 20200312135642.13845-2-anshuman.gu...@intel.com
Anshuman Gupta (2):
drm/i915: Power well id for ICL PG3
drm/i915: Add i915_lpsp_info debugfs
.../drm/i915/display/intel_display_debugfs.c | 65 +++
.../drm/i915/dis
On 12/03/2020 11:53, Chris Wilson wrote:
During driver unload, we have many asserts that we have released our
bookkeeping structs and are idle. In some cases, these struct are
protected by RCU and we do not release them until after an RCU grace
period.
Reported-by: Maarten Lankhorst
Fixes: 13
== Series Details ==
Series: drm/mm: Use debugobject to track lifetimes (rev3)
URL : https://patchwork.freedesktop.org/series/74638/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c869cbdfdc9f drm/mm: Use debugobject to track lifetimes
-:301: WARNING:TYPO_SPELLING: 'compatiblity
== Series Details ==
Series: drm/mm: Use debugobject to track lifetimes (rev3)
URL : https://patchwork.freedesktop.org/series/74638/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8127 -> Patchwork_16953
Summary
---
*
== Series Details ==
Series: i915 lpsp support for lpsp igt
URL : https://patchwork.freedesktop.org/series/74648/
State : failure
== Summary ==
Couldn't find any build artifact matching "Test-with:
20200312135642.13845-2-anshuman.gu...@intel.com"\nCheck that the msg-id is
correct and make su
> -Original Message-
> From: Ville Syrjälä
> Sent: 12 March 2020 19:35
> To: Laxminarayan Bharadiya, Pankaj
>
> Cc: jani.nik...@linux.intel.com; dan...@ffwll.ch; intel-
> g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; airl...@linux.ie;
> maarten.lankho...@linux.intel.com;
Am 12.03.20 um 15:19 schrieb Jason Gunthorpe:
On Thu, Mar 12, 2020 at 03:47:29AM -0700, Christoph Hellwig wrote:
On Thu, Mar 12, 2020 at 11:31:35AM +0100, Christian König wrote:
But how should we then deal with all the existing interfaces which already
take a scatterlist/sg_table ?
The whole D
Switch igt_vm_isolation() to using igt_random_offset().
Signed-off-by: Chris Wilson
Cc: Matthew Auld
Cc: Akeem G Abodunrin
---
drivers/gpu/drm/i915/gem/selftests/i915_gem_context.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i915/gem/selftests/i9
Chris Wilson writes:
> During driver unload, we have many asserts that we have released our
> bookkeeping structs and are idle. In some cases, these struct are
> protected by RCU and we do not release them until after an RCU grace
> period.
>
> Reported-by: Maarten Lankhorst
> Fixes: 130a95e9098
On Thu, Mar 12, 2020 at 03:37:03PM +, Laxminarayan Bharadiya, Pankaj wrote:
>
>
> > -Original Message-
> > From: Ville Syrjälä
> > Sent: 12 March 2020 19:35
> > To: Laxminarayan Bharadiya, Pankaj
> >
> > Cc: jani.nik...@linux.intel.com; dan...@ffwll.ch; intel-
> > g...@lists.freedes
Quoting Tvrtko Ursulin (2020-03-12 14:18:26)
>
> On 12/03/2020 11:53, Chris Wilson wrote:
> > During driver unload, we have many asserts that we have released our
> > bookkeeping structs and are idle. In some cases, these struct are
> > protected by RCU and we do not release them until after an RC
Matt Roper writes:
> The bspec documents multiple MCR ranges; make sure they're all captured
> by the driver.
>
> Bspec: 13991, 52079
> Fixes: 592a7c5e082e ("drm/i915: Extend non readable mcr range")
Yeah it seems that the ranges drip feed into documentation slowly.
> Cc: Mika Kuoppala
> Signe
Matt Roper writes:
> The register this workaround updates is a render engine register in the
> MCR range, so we should initialize this in rcs_engine_wa_init() rather
> than gt_wa_init().
>
> Closes: https://gitlab.freedesktop.org/drm/intel/issues/1222
> Fixes: 36204d80bacb ("drm/i915/icl: Wa_1406
== Series Details ==
Series: drm/i915/selftests: Use igt_random_offset()
URL : https://patchwork.freedesktop.org/series/74649/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8127 -> Patchwork_16955
Summary
---
**SUCCE
On 2020-03-12 8:19 a.m., Jason Gunthorpe wrote:
> On Thu, Mar 12, 2020 at 03:47:29AM -0700, Christoph Hellwig wrote:
>> On Thu, Mar 12, 2020 at 11:31:35AM +0100, Christian König wrote:
>>> But how should we then deal with all the existing interfaces which already
>>> take a scatterlist/sg_table ?
Matt Roper writes:
> This workaround appears under two different numbers (and with somewhat
> confused stepping applicability on ICL). Ultimately it appears we
> should just implement this for all stepping of ICL and EHL.
>
> Note that this is identical to Wa_1407928979:tgl that already exists i
On Thu, 12 Mar 2020 at 15:47, Chris Wilson wrote:
>
> Switch igt_vm_isolation() to using igt_random_offset().
>
> Signed-off-by: Chris Wilson
> Cc: Matthew Auld
> Cc: Akeem G Abodunrin
> ---
> drivers/gpu/drm/i915/gem/selftests/i915_gem_context.c | 8 +++-
> 1 file changed, 3 insertions(+)
== Series Details ==
Series: drm/i915/gem: Drop relocation slowpath
URL : https://patchwork.freedesktop.org/series/74592/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8124_full -> Patchwork_16934_full
Summary
---
**
Hey,
On Tue, 10 Mar 2020, Ville Syrjälä wrote:
> On Tue, Mar 10, 2020 at 07:18:58PM +0200, Kai Vehmanen wrote:
>> On Tue, 10 Mar 2020, Ville Syrjälä wrote:
>>> audio at init time. And we could maybe try to remove the modeset from the
>>> put_power() so that at least if you get a blink it's just t
On 06/03/2020 10:05, Lionel Landwerlin wrote:
The caller of i915_oa_init_reg_state() already sets this.
Signed-off-by: Lionel Landwerlin
---
drivers/gpu/drm/i915/i915_perf.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i9
On Thu, Mar 12, 2020 at 07:27:58PM +0200, Kai Vehmanen wrote:
> Hey,
>
> On Tue, 10 Mar 2020, Ville Syrjälä wrote:
>
> > On Tue, Mar 10, 2020 at 07:18:58PM +0200, Kai Vehmanen wrote:
> >> On Tue, 10 Mar 2020, Ville Syrjälä wrote:
> >>> audio at init time. And we could maybe try to remove the mode
On Thu, Mar 12, 2020 at 07:27:58PM +0200, Kai Vehmanen wrote:
> Hey,
>
> On Tue, 10 Mar 2020, Ville Syrjälä wrote:
>
> > On Tue, Mar 10, 2020 at 07:18:58PM +0200, Kai Vehmanen wrote:
> >> On Tue, 10 Mar 2020, Ville Syrjälä wrote:
> >>> audio at init time. And we could maybe try to remove the mode
On 06/03/2020 10:05, Lionel Landwerlin wrote:
On Gen11 powergating half the execution units is a functional
requirement when using the VME samplers. Not fullfilling this
requirement can lead to hangs.
This unfortunately plays fairly poorly with the NOA requirements. NOA
requires a stable power
Quoting Matthew Auld (2020-03-12 17:00:58)
> On Thu, 12 Mar 2020 at 15:47, Chris Wilson wrote:
> >
> > Switch igt_vm_isolation() to using igt_random_offset().
> >
> > Signed-off-by: Chris Wilson
> > Cc: Matthew Auld
> > Cc: Akeem G Abodunrin
> > ---
> > drivers/gpu/drm/i915/gem/selftests/i915_
On Wed, 11 Mar 2020 at 16:03, Chris Wilson wrote:
>
> Since the relocations are no longer performed under a global
> struct_mutex, or any other lock, that is also held by pagefault handlers,
> we can relax and allow our fast path to take a fault. As we no longer
> need to abort the fast path for l
== Series Details ==
Series: Gen11 workarounds (rev5)
URL : https://patchwork.freedesktop.org/series/74475/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8127 -> Patchwork_16956
Summary
---
**SUCCESS**
No regressi
== Series Details ==
Series: drm/i915/gem: Take a copy of the engines for context_barrier_task (rev3)
URL : https://patchwork.freedesktop.org/series/74583/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8124_full -> Patchwork_16937_full
=
Add helper functions that can allow i915 to detect and control
an integrated privacy screen via ACPI methods. These shall be used
in the next patch.
Signed-off-by: Rajat Jain
---
v9: same as v8
v8: Initial version. formed by refactoring the previous patch 4.
print the connector name in the de
== Series Details ==
Series: drm/i915 Support for integrated privacy screen
URL : https://patchwork.freedesktop.org/series/74650/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a0d97f65392d intel_acpi: Rename drm_dev local variable to dev
500f89acca9c drm/connector: Add support
On Tue, 03 Mar 2020 14:19:02 -0800, Umesh Nerlige Ramappa wrote:
>
> From: Lionel Landwerlin
>
> This new parameter let's the application choose how often the OA
> buffer should be checked on the CPU side for data availability. Longer
> polling period tend to reduce CPU overhead if the application
== Series Details ==
Series: drm/i915 Support for integrated privacy screen
URL : https://patchwork.freedesktop.org/series/74650/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8127 -> Patchwork_16957
Summary
---
**SU
>-Original Message-
>From: Intel-gfx On Behalf Of Chris
>Wilson
>Sent: Wednesday, March 11, 2020 9:31 AM
>To: intel-gfx@lists.freedesktop.org
>Subject: [Intel-gfx] [PATCH 02/12] drm/i915: Wrap i915_active in a simple
>kreffed struct
>
>For conveniences of callers that just want to use an i
== Series Details ==
Series: drm/i915/gem: Mark up sw-fence notify function
URL : https://patchwork.freedesktop.org/series/74604/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8124_full -> Patchwork_16941_full
Summary
-
On 12/03/2020 21:27, Dixit, Ashutosh wrote:
On Tue, 03 Mar 2020 14:19:02 -0800, Umesh Nerlige Ramappa wrote:
From: Lionel Landwerlin
This new parameter let's the application choose how often the OA
buffer should be checked on the CPU side for data availability. Longer
polling period tend to re
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next linus/master v5.6-rc5 next-20200312]
[if your patch is applied to the wrong git tree, please
On Wed, 2020-03-11 at 09:22 -0700, Matt Roper wrote:
> On gen11 the XY_FAST_COPY_BLT command has some size restrictions on
> its
> usage. Although this instruction is mainly used by userspace, i915
> also
> uses it to copy object contents during some selftests, so let's
> ensure
> the restrictions
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: 2e46e269a2843c5d0b6c72bfb7fa9d9913c15415
commit: 1be88a0837ab2a7e95a5177877a9b344f9e6a3e3 [3/8] Merge remote-tracking
branch 'drm/drm-next' into drm-tip
config: riscv-randconfig-a001-20200312 (attached as .config)
compile
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/gem: Mark up sw-fence notify
function
URL : https://patchwork.freedesktop.org/series/74605/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8125_full -> Patchwork_16942_full
On Wed, Mar 04, 2020 at 05:04:52PM -0800, Lucas De Marchi wrote:
On Wed, Mar 4, 2020 at 2:33 PM Caz Yokoyama wrote:
This reverts commit 36a6b5d964d995b536b1925ec42052ee40ba92c4.
Fixes: 36a6b5d964d9 ("drm/i915/tgl: Add extra hdc flush workaround")
The commit takes care Wa_1604544889 which was
On Wed, 2020-03-11 at 09:22 -0700, Matt Roper wrote:
> v2:
> - Move to context workarounds. ROW_CHICKEN4 is part of the context
>image on gen11 (although it isn't on gen12).
>
> Signed-off-by: Matt Roper
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 3 +++
> drivers/gpu/drm/i915/i9
On Tue, Mar 10, 2020 at 09:07:39PM +0530, Animesh Manna wrote:
> [Why]:
> Aligh with DP spec wanted to follow same naming convention.
>
> [How]:
> Changed the macro name of the dpcd address used for getting requested
> test-pattern.
>
> Cc: Harry Wentland
> Cc: Alex Deucher
> Reviewed-by: Harry
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next linus/master v5.6-rc5 next-20200312]
[if your patch is applied to the wrong git tree, please
On Thu, 12 Mar 2020 13:37:12 -0700, Lionel Landwerlin wrote:
> On 12/03/2020 21:27, Dixit, Ashutosh wrote:
> > On Tue, 03 Mar 2020 14:19:02 -0800, Umesh Nerlige Ramappa wrote:
> >> From: Lionel Landwerlin
> >>
> >> This new parameter let's the application choose how often the OA
> >> buffer should
On Thu, 2020-03-12 at 15:07 -0700, Lucas De Marchi wrote:
> On Wed, Mar 04, 2020 at 05:04:52PM -0800, Lucas De Marchi wrote:
> > On Wed, Mar 4, 2020 at 2:33 PM Caz Yokoyama > > wrote:
> > > This reverts commit 36a6b5d964d995b536b1925ec42052ee40ba92c4.
> > > Fixes: 36a6b5d964d9 ("drm/i915/tgl: Add
On Tue, Mar 10, 2020 at 09:07:40PM +0530, Animesh Manna wrote:
> During phy compliance auto test mode source need to read
> requested test pattern from sink through DPCD. After processing
> the request source need to set the pattern. So set/get method
> added in drm layer as it is DP protocol.
>
>
On Tue, Mar 10, 2020 at 09:07:41PM +0530, Animesh Manna wrote:
> vswing/pre-emphasis adjustment calculation is needed in processing
> of auto phy compliance request other than link training, so have
> made non-static function.
>
> No functional change.
>
> v1: initial patch.
> v2:
> - used "intel
1 - 100 of 123 matches
Mail list logo
