== Series Details ==
Series: drm/i915/gt conversion to new drm logging macros.
URL : https://patchwork.freedesktop.org/series/72643/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16290_full
Summary
== Series Details ==
Series: Introduce CAP_PERFMON to secure system performance monitoring and
observability (rev2)
URL : https://patchwork.freedesktop.org/series/72273/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16289_full
== Series Details ==
Series: series starting with [1/2] drm/i915/display/fbc: Make fences a
nice-to-have for GEN9+
URL : https://patchwork.freedesktop.org/series/72698/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16309
== Series Details ==
Series: drm/i915/gt: Trim default context register state for gen9
URL : https://patchwork.freedesktop.org/series/72697/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16308
Summary
== Series Details ==
Series: series starting with [1/6] drm/i915: Skip capturing errors from
internal contexts
URL : https://patchwork.freedesktop.org/series/72639/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16288_full
== Series Details ==
Series: drm/i915/gt: Trim default context register state for gen9
URL : https://patchwork.freedesktop.org/series/72697/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
01bc69209e01 drm/i915/gt: Trim default context register state for gen9
-:12:
== Series Details ==
Series: series starting with [1/5] drm/i915/execlist: Mark up racy read of
execlists->pending[0]
URL : https://patchwork.freedesktop.org/series/72690/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16307
== Series Details ==
Series: series starting with [1/5] drm/i915/execlist: Mark up racy read of
execlists->pending[0]
URL : https://patchwork.freedesktop.org/series/72690/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
82aa4207ae44 drm/i915/execlist: Mark up racy read of
== Series Details ==
Series: drm/i915/selftests/perf: measure memcpy bw between regions (rev2)
URL : https://patchwork.freedesktop.org/series/72621/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16306
== Series Details ==
Series: series starting with [1/8] drm/i915/gt: Expose engine properties via
sysfs
URL : https://patchwork.freedesktop.org/series/72638/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16287_full
On 1/28/20 4:49 PM, Matthew Brost wrote:
On Fri, Jan 24, 2020 at 04:55:31PM -0800, Daniele Ceraolo Spurio wrote:
Note: this applies on top of my series to commit early to GuC [1].
Picking up from the feedback from my RFC series about splitting
up intel_lrc.c [2], this series introduces GuC
== Series Details ==
Series: drm/i915/selftests/perf: measure memcpy bw between regions (rev2)
URL : https://patchwork.freedesktop.org/series/72621/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d20c84c0e130 drm/i915/selftests/perf: measure memcpy bw between regions
-:242:
== Series Details ==
Series: drm: Introduce struct drm_device based WARN* and use them in i915 (rev5)
URL : https://patchwork.freedesktop.org/series/72035/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16305
== Series Details ==
Series: drm: Introduce struct drm_device based WARN* and use them in i915 (rev5)
URL : https://patchwork.freedesktop.org/series/72035/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6f71daf153b5 drm/i915/display/icl_dsi: Make WARN* drm specific where
== Series Details ==
Series: drm/i915/selftests: Lock the drm_mm as we search
URL : https://patchwork.freedesktop.org/series/72685/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16304
Summary
---
== Series Details ==
Series: drm/i915/tgl: Suppress DC5/DC6 around DSB usage (rev3)
URL : https://patchwork.freedesktop.org/series/72549/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16285_full
On Fri, Jan 24, 2020 at 04:55:31PM -0800, Daniele Ceraolo Spurio wrote:
Note: this applies on top of my series to commit early to GuC [1].
Picking up from the feedback from my RFC series about splitting
up intel_lrc.c [2], this series introduces GuC submission versions
of most of the engine and
== Series Details ==
Series: drm/i915/execlist: Mark up racy read of execlists->pending[0]
URL : https://patchwork.freedesktop.org/series/72681/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16303
Summary
== Series Details ==
Series: series starting with [1/3] drm/i915: move pipe, pch and vblank enable
to encoders on DDI platforms
URL : https://patchwork.freedesktop.org/series/72678/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16302
== Series Details ==
Series: drm/i915: Adding YUV444 packed format support for skl+ (rev3)
URL : https://patchwork.freedesktop.org/series/66770/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16284_full
== Series Details ==
Series: drm/i915/hdcp: move update pipe code to hdcp
URL : https://patchwork.freedesktop.org/series/72679/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16301
Summary
---
From: Radhakrishna Sripada
dgfx platforms do not support CPU fence and FBC host tracking so
lets avoid write to removed registers.
Cc: Rodrigo Vivi
Cc: Matt Roper
Cc: Dhinakaran Pandiyan
Signed-off-by: Radhakrishna Sripada
Signed-off-by: Lucas De Marchi
Signed-off-by: José Roberto de Souza
dGFX have local memory so it do not have aperture and do not support
CPU fences but even for iGFX it have a small number of fences.
As replacement for fences to track frontbuffer modifications by CPU
we have a software tracking that is already in used by FBC and PSR.
PSR don't support fences so
On 1/28/20 12:43 PM, Chris Wilson wrote:
Extract the core functions for setting up the machine dependent logical
ring context to intel_lrc.c. This will be shared by all submission
backends that utilise logical ring contexts.
Signed-off-by: Chris Wilson
Cc: Daniele Ceraolo Spurio
Cc: Tvrtko
On Tue, Jan 28, 2020 at 03:15:30PM -0800, Matt Roper wrote:
> On Fri, Jan 24, 2020 at 10:44:54AM +0200, Stanislav Lisovskiy wrote:
> > Added proper DBuf slice mapping to correspondent
> > pipes, depending on pipe configuration as stated
> > in BSpec.
> >
> > v2:
> > - Remove unneeded braces
>
On Fri, Jan 24, 2020 at 10:44:56AM +0200, Stanislav Lisovskiy wrote:
> During full modeset, global state(i.e dev_priv) is protected
> by locking the crtcs in state, otherwise global state is not
> serialized. Also if it is not a full modeset, we anyway
> don't need to change DBuf slice
== Series Details ==
Series: series starting with [v2,1/4] drm/i915: Nuke pre-production GLK HDMI
w/a 1139
URL : https://patchwork.freedesktop.org/series/72675/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16300
On Fri, Jan 24, 2020 at 10:44:55AM +0200, Stanislav Lisovskiy wrote:
> Now using power_domain mutex to protect from race condition, which
> can occur because intel_dbuf_slices_update might be running in
> parallel to gen9_dc_off_power_well_enable being called from
> intel_dp_detect for instance,
== Series Details ==
Series: drm/i915/display: mass conversion to intel_de_*() register accessors
(rev2)
URL : https://patchwork.freedesktop.org/series/72533/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16283_full
On Fri, Jan 24, 2020 at 10:44:54AM +0200, Stanislav Lisovskiy wrote:
> Added proper DBuf slice mapping to correspondent
> pipes, depending on pipe configuration as stated
> in BSpec.
>
> v2:
> - Remove unneeded braces
> - Stop using macro for DBuf assignments as
> it seems to reduce
== Series Details ==
Series: drm/i915/debugfs: remove VBT data about DRRS
URL : https://patchwork.freedesktop.org/series/72672/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16299
Summary
---
Now that it appears we have tamed the mystery hang on module reload, we
can relax some of the counter-measures we employed to help stabilise and
debug gen9. As we have aggressive poisoning of the context image, we can
confidently reduce the default context state in gen9 to match the limits
of the
On 1/28/20 2:08 PM, Chris Wilson wrote:
Quoting Daniele Ceraolo Spurio (2020-01-28 21:55:02)
On 1/28/20 12:43 PM, Chris Wilson wrote:
Extract the core functions for setting up the machine dependent logical
ring context to intel_lrc.c. This will be shared by all submission
backends that
== Series Details ==
Series: drm/hdcp: optimizing the srm handling (rev2)
URL : https://patchwork.freedesktop.org/series/72312/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16282_full
Summary
On Tue, 28 Jan 2020, Alexey Budankov wrote:
>
> Open access to monitoring via kprobes and uprobes and eBPF tracing for
> CAP_PERFMON privileged process. Providing the access under CAP_PERFMON
> capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes
> chances to misuse the
On Tue, 28 Jan 2020, Alexey Budankov wrote:
> Signed-off-by: Alexey Budankov
> ---
> arch/powerpc/perf/imc-pmu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/perf/imc-pmu.c b/arch/powerpc/perf/imc-pmu.c
> index cb50a9e1fd2d..e837717492e4 100644
>
On Tue, 28 Jan 2020, Alexey Budankov wrote:
>
> Open access to monitoring for CAP_PERFMON privileged process. Providing
> the access under CAP_PERFMON capability singly, without the rest of
> CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and
> makes operation more secure.
On Tue, 28 Jan 2020, Alexey Budankov wrote:
>
> Signed-off-by: Alexey Budankov
> ---
> include/linux/capability.h | 4
> include/uapi/linux/capability.h | 8 +++-
> security/selinux/include/classmap.h | 4 ++--
> 3 files changed, 13 insertions(+), 3 deletions(-)
On Tue, 28 Jan 2020, Alexey Budankov wrote:
>
> Open access to monitoring for CAP_PERFMON privileged process.
> Providing the access under CAP_PERFMON capability singly, without the
> rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the
> credentials and makes operation more secure.
On Tue, 28 Jan 2020, Alexey Budankov wrote:
>
> Open access to monitoring for CAP_PERFMON privileged process.
> Providing the access under CAP_PERFMON capability singly, without the
> rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the
> credentials and makes operation more secure.
== Series Details ==
Series: drm/i915/trace: i915_request.prio is a signed value
URL : https://patchwork.freedesktop.org/series/72671/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16298
Summary
---
On Tue, 28 Jan 2020, Alexey Budankov wrote:
>
> Signed-off-by: Alexey Budankov
> ---
> kernel/trace/bpf_trace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
> index e5ef4ae9edb5..334f1d71ebb1 100644
> ---
On Mon, Jan 27, 2020 at 12:50:57PM -0800, Matt Roper wrote:
> There are reports of unexpected DSB busy/timeout happening after IGT
> tests finish running that apparently go away when the DMC firmware isn't
> loaded. The bspec doesn't say anything specific about DSB needing us to
> exit DC5/DC6,
Quoting Daniele Ceraolo Spurio (2020-01-28 21:55:02)
>
>
> On 1/28/20 12:43 PM, Chris Wilson wrote:
> > Extract the core functions for setting up the machine dependent logical
> > ring context to intel_lrc.c. This will be shared by all submission
> > backends that utilise logical ring contexts.
== Series Details ==
Series: drm/i915/gt: Hook up CS_MASTER_ERROR_INTERRUPT
URL : https://patchwork.freedesktop.org/series/72669/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16297
Summary
---
== Series Details ==
Series: drm/i915/dp: Modeset only the tiled connectors with CRTC (rev2)
URL : https://patchwork.freedesktop.org/series/72559/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16281_full
On 1/28/20 12:43 PM, Chris Wilson wrote:
We want to separate the utility functions for controlling the logical
ring context from the execlists submission mechanism (which is an
overgrown scheduler).
This is similar to Daniele's work to split up the files, but being
selfish I wanted to base
== Series Details ==
Series: series starting with [1/2] drm/i915: Nuke pre-production GLK HDMI w/a
1139
URL : https://patchwork.freedesktop.org/series/72668/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16296
On Tue, Jan 28, 2020 at 07:30:59PM +0200, Ville Syrjälä wrote:
> On Tue, Jan 28, 2020 at 07:05:38PM +0200, Ville Syrjälä wrote:
> > On Fri, Jan 17, 2020 at 04:16:28AM -0500, Matt Atwood wrote:
> > > On Tiger Lake we do not support source keying in the pixel formats P010,
> > > P012, P016.
> > >
>
== Series Details ==
Series: drm/i915/gt: Lift set-wedged engine dumping out of user paths (rev2)
URL : https://patchwork.freedesktop.org/series/72611/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16279_full
On Tue, Jan 28, 2020 at 07:30:59PM +0200, Ville Syrjälä wrote:
> On Tue, Jan 28, 2020 at 07:05:38PM +0200, Ville Syrjälä wrote:
> > On Fri, Jan 17, 2020 at 04:16:28AM -0500, Matt Atwood wrote:
> > > On Tiger Lake we do not support source keying in the pixel formats P010,
> > > P012, P016.
> > >
>
We want to separate the utility functions for controlling the logical
ring context from the execlists submission mechanism (which is an
overgrown scheduler).
This is similar to Daniele's work to split up the files, but being
selfish I wanted to base it after my own changes to intel_lrc.c petered
Now that we have offline error capture and can reset an engine from
inside an atomic context while also preserving the GPU state for
post-mortem analysis, it is time to handle error interrupts thrown by
the command parser.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
We write to execlists->pending[0] in process_csb() to acknowledge the
completion of the ESLP update, outside of the main spinlock. When we
check the current status of the previous submission in
__execlists_submission_tasklet() we should therefore use READ_ONCE() to
reflect and document the
If we find ourselves waiting on a MI_SEMAPHORE_WAIT, either within the
user batch or in our own preamble, the engine raises a
GT_WAIT_ON_SEMAPHORE interrupt. We can unmask that interrupt and so
respond to a semaphore wait by yielding the timeslice, if we have
another context to yield to!
The only
== Series Details ==
Series: drm/i915/execlists: Move trace in/out to submission and completion
URL : https://patchwork.freedesktop.org/series/72665/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16295
== Series Details ==
Series: drm/i915/dsi: Enable dsi as part of encoder->enable
URL : https://patchwork.freedesktop.org/series/72619/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7827_full -> Patchwork_16277_full
Summary
== Series Details ==
Series: series starting with [1/4] drm: Complain if drivers still use the
->load callback
URL : https://patchwork.freedesktop.org/series/72652/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16292
Quoting Matthew Auld (2020-01-28 18:38:06)
> + sort(t, ARRAY_SIZE(t), sizeof(*t), wrap_ktime_compare, NULL);
> + pr_info("%s src(%s, %s) -> dst(%s, %s) %s %llu KiB copy: %lld
> MiB/s\n",
pr_info("%s src(%s, %s) -> dst(%s, %s) %14s %4llu KiB copy: %5lld MiB/s\n",
== Series Details ==
Series: drm/i915: Skip capturing errors from internal contexts
URL : https://patchwork.freedesktop.org/series/72656/
State : failure
== Summary ==
Applying: drm/i915: Skip capturing errors from internal contexts
Using index info to reconstruct a base tree...
M
Measure the memcpy bw between our CPU accessible regions, trying all
supported mapping combinations(WC, WB) across various sizes.
v2:
use smaller sizes
throw in memcpy32/memcpy64/memcpy_from_wc
Signed-off-by: Matthew Auld
Cc: Chris Wilson
---
Quoting Chris Wilson (2020-01-28 18:54:18)
> Quoting Matthew Auld (2020-01-28 18:38:06)
> > + sort(t, ARRAY_SIZE(t), sizeof(*t), wrap_ktime_compare,
> > NULL);
> > + pr_info("%s src(%s, %s) -> dst(%s, %s) %s %llu KiB copy:
> > %lld MiB/s\n",
> > +
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion
Quoting Matthew Auld (2020-01-28 18:38:06)
> Measure the memcpy bw between our CPU accessible regions, trying all
> supported mapping combinations(WC, WB) across various sizes.
>
> v2:
> use smaller sizes
> throw in memcpy32/memcpy64/memcpy_from_wc
>
> Signed-off-by: Matthew Auld
> Cc:
From: Ramalingam C
Call function gem_class_can_store_dword instead of legacy function
gem_can_store_dword. This requires that e->class be available in the
calling function.
Instead of passing "engine" (== "e->flags") to functions, pass "e".
This makes e->class available where it is needed.
Switch from the existing engine iteration to using macro
__for_each_physical_engine which all engines that are actually present.
The invocation of __for_each_physical_engine sets the engine mapping
for context 0 to be all existing engines. Subsequent context creation
is done via
i915/gem_ctx_isolation: __for_each_physical_engine and gem_engine_topology
V2: Use new function gem_context_clone_with_engines
V3: Revise commit messages including titles
Use __for_each_physical_engine with gem_engine_topology.
Iterates through the definitive list of all engines
present.
Patch
On Tue, 28 Jan 2020 at 18:35, Chris Wilson wrote:
>
> Hold onto the vm->mutex (to lock the drm_mm) to ensure that the rbtree
> is table as we search it for our scratch node.
>
> Signed-off-by: Chris Wilson
Reviewed-by: Matthew Auld
___
Intel-gfx
== Series Details ==
Series: series starting with [1/4] drm: Complain if drivers still use the
->load callback
URL : https://patchwork.freedesktop.org/series/72652/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
4b3af837d222 drm: Complain if drivers still use the ->load
Hold onto the vm->mutex (to lock the drm_mm) to ensure that the rbtree
is table as we search it for our scratch node.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/gem/selftests/i915_gem_context.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git
Drm specific drm_WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion
Quoting Jani Nikula (2020-01-28 13:48:10)
> On Tue, 28 Jan 2020, Tvrtko Ursulin wrote:
> >> -DRM_DEBUG(
> >> +drm_dbg(>drm,
> >
> > This changes DRM_UT_CORE to DRM_UT_DRIVER so our typical drm.debug=0xe
> > becomes much more spammy.
>
> This is what I've instructed Wambui to do in i915. It's my
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
Drm specific drm_WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done
Device specific dev_WARN and dev_WARN_ONCE macros available in kernel
include device information in the backtrace, so we know what device
the warnings originate from.
Similar to this, add new struct drm_device based drm_WARN* macros. These
macros include device information in the backtrace, so we
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion
== Series Details ==
Series: drm/i915: Move cec_notifier to intel_connector
URL : https://patchwork.freedesktop.org/series/72649/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16291
Summary
---
On Fri, Jan 24, 2020 at 10:44:52AM +0200, Stanislav Lisovskiy wrote:
> Now start using parameterized DBUF_CTL instead
> of hardcoded, this would allow shorter access
> functions when reading or storing entire state.
>
> Tried to implement it in a MMIO_PIPE manner, however
> DBUF_CTL1 address is
On Tue, Jan 28, 2020 at 07:05:38PM +0200, Ville Syrjälä wrote:
> On Fri, Jan 17, 2020 at 04:16:28AM -0500, Matt Atwood wrote:
> > On Tiger Lake we do not support source keying in the pixel formats P010,
> > P012, P016.
> >
> > Bspec: 52890
> > Cc: Matt Roper
> > Signed-off-by: Matt Atwood
> >
== Series Details ==
Series: drm/auth: Drop master_create/destroy hooks
URL : https://patchwork.freedesktop.org/series/72609/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7826_full -> Patchwork_16274_full
Summary
---
We write to execlists->pending[0] in process_csb() to acknowledge the
completion of the ESLP update, outside of the main spinlock. When we
check the current status of the previous submission in
__execlists_submission_tasklet() we should therefore use READ_ONCE() to
reflect and document the
On Fri, Jan 17, 2020 at 04:16:28AM -0500, Matt Atwood wrote:
> On Tiger Lake we do not support source keying in the pixel formats P010,
> P012, P016.
>
> Bspec: 52890
> Cc: Matt Roper
> Signed-off-by: Matt Atwood
> ---
> drivers/gpu/drm/i915/display/intel_sprite.c | 13 +
> 1 file
intel_dp_set_m_n() has a clear place in the DDI DP specific pre-enable
hook.
Cc: Ville Syrjala
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/intel_ddi.c | 2 ++
drivers/gpu/drm/i915/display/intel_display.c | 3 ---
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git
On Tue, 28 Jan 2020, "Kulkarni, Vandita" wrote:
>> -Original Message-
>> From: Jani Nikula
>> Sent: Monday, January 27, 2020 5:34 PM
>> To: Kulkarni, Vandita ; intel-
>> g...@lists.freedesktop.org
>> Cc: Kulkarni, Vandita
>> Subject: Re: [PATCH] drm/i915/dsi: Enable dsi as part of
1 - 100 of 180 matches
Mail list logo
