There were few system hung observed while running i915_pm_rpm igt test.
FDO https://bugs.freedesktop.org/show_bug.cgi?id=108840
Root cause is believed to due to page fault in ACPI idle driver.
(FDO comment 18).
It has been suggested by Daniel Vetter to disable ACPI idle
driver for Core-for-CI, only
== Series Details ==
Series: series starting with [1/2] drm/i915/guc: Implement reset locally
URL : https://patchwork.freedesktop.org/series/59199/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5891_full -> Patchwork_12733_full
=
Hi all,
After merging the drm-misc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpu/drm/cirrus/cirrus.c: In function 'cirrus_fb_blit_rect':
drivers/gpu/drm/cirrus/cirrus.c:310:25: error: implicit declaration of function
'__io_virt'; did you mean '__do_irq'? [-W
Hi Anshuman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v5.1-rc4 next-20190408]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi,
This includes various code refinement and cleanups, with proper
async/sync display flip handling, and also some changes required
for recent drm-intel-next as guest kernel, details below.
Thanks
--
The following changes since commit a01b2c6f47d86c7d1a9fa822b3b91ec233b61784:
drm/i915: Updat
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev5)
URL : https://patchwork.freedesktop.org/series/59174/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5891_full -> Patchwork_12732_full
=
Hi all,
Today's linux-next merge of the drm-misc tree got conflicts in:
drivers/gpu/drm/cirrus/cirrus_drv.h
drivers/gpu/drm/cirrus/cirrus_ttm.c
between commits:
aa8e2435b3d4 ("drm/ttm: Define a single DRM_FILE_PAGE_OFFSET constant")
7d1500f9fbfc ("drm/ttm: Remove file_page_offset parame
Hi Anshuman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v5.1-rc4 next-20190408]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
== Series Details ==
Series: IRQ initialization debloat and conversion to uncore
URL : https://patchwork.freedesktop.org/series/59202/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5891 -> Patchwork_12734
Summary
---
== Series Details ==
Series: IRQ initialization debloat and conversion to uncore
URL : https://patchwork.freedesktop.org/series/59202/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7f73d1fe31bb drm/i915: refactor the IRQ init/reset macros
-:114: CHECK:MACRO_ARG_REUSE: Macro arg
The whole point of having macros here is for the token pasting
necessary to automatically have IMR, IIR and IER selected. We don't
really need or want all the inlining that happens as a consequence.
The good thing about the current code is that it works regardless of
the relative offsets between th
Make them take the uncore argument from the caller instead of passing
the implicit &dev_priv->uncore directly. This will allow us to finally
pass something that's not dev_priv->uncore in the future, and gets rid
of the implicit variables in register macros.
Signed-off-by: Paulo Zanoni
---
driver
The first patch is a simple refactor to try to debloat our IRQ
initialization and the second is a tiny conversion to the new
intel_uncore model. I'm not sure how much we want patch 3 right now,
but my understanding is that we want to move in that direction anyway,
so why not now.
Cc: Daniele Cerao
The IRQ initialization helpers are simple and self-contained. Continue
the transition started in the recent uncore rework to get us rid of
I915_READ/WRITE and the implicit dev_priv variables.
While the implicit dev_priv is removed from the IRQ initialization
helpers, we didn't get rid of them in t
== Series Details ==
Series: series starting with [1/2] drm/i915/guc: Implement reset locally
URL : https://patchwork.freedesktop.org/series/59199/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5891 -> Patchwork_12733
Summa
== Series Details ==
Series: series starting with [1/2] drm/i915/guc: Implement reset locally
URL : https://patchwork.freedesktop.org/series/59199/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ed8431824b19 drm/i915/guc: Implement reset locally
8b244698e9bc drm/i915/execlists:
During reset, we try and stop the active ring. This has the consequence
that we often clobber the RING registers within the context image. When
we find an active request, we update the context image to rerun that
request (if it was guilty, we replace the hanging user payload with
NOPs). However, we
Before causing guc and execlists to diverge further (breaking guc in the
process), take a copy of the current reset procedure and make it local to
the guc submission backend
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/intel_guc_submission.c | 102
drivers/gpu/drm/i9
On Thu, Apr 04, 2019 at 04:04:26PM -0700, Lucas De Marchi wrote:
> Separate the two comments: one is a workaround and the other is a sanity
> check. We could just compare != 1, but let's treat them differently due
> to having different meaning.
>
> Signed-off-by: Lucas De Marchi
Reviewed-by: Rod
On Thu, Apr 04, 2019 at 04:04:25PM -0700, Lucas De Marchi wrote:
> Reorder if/else so we check for gen >= 11 first, similar to most of
> other checks in the driver.
>
> Signed-off-by: Lucas De Marchi
Reviewed-by: Rodrigo Vivi
> ---
> drivers/gpu/drm/i915/intel_pm.c | 11 ++-
> 1 file
On Thu, Apr 04, 2019 at 04:04:24PM -0700, Lucas De Marchi wrote:
> At some point the spec was changed and we never updated the numbers to
> match it. Let's try once more to keep them in sync.
or maybe we just copied the numers from CNL ones?
Anyway let's keep in sync with spec:
Reviewed-by: Rod
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev5)
URL : https://patchwork.freedesktop.org/series/59174/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5891 -> Patchwork_12732
S
On Monday, 2019-04-08 13:44:17 +, Ayan Halder wrote:
> Generated using make headers_install from the drm-next
> tree - git://anongit.freedesktop.org/drm/drm
> branch - drm-next
> commit - 14d2bd53a47a7e1cb3e03d00a6b952734cf90f3f
>
> The changes were as follows :-
>
> core: (drm.h, drm_fourcc.
Quoting Jani Nikula (2018-10-22 10:00:39)
> On Mon, 22 Oct 2018, Chris Wilson wrote:
> > Quoting Jani Nikula (2018-10-22 09:25:45)
> >> On Fri, 12 Oct 2018, José Roberto de Souza wrote:
> >> > Display features should not be initialized or deinitialized when
> >> > display is disabled.
> >
> > I c
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev5)
URL : https://patchwork.freedesktop.org/series/59174/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9c116a9c7203 drm/i915/execlists: Always reset the context's RING registers
-:17:
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev4)
URL : https://patchwork.freedesktop.org/series/59174/
State : failure
== Summary ==
CALLscripts/checksyscalls.sh
CALLscripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/
During reset, we try and stop the active ring. This has the consequence
that we often clobber the RING registers within the context image. When
we find an active request, we update the context image to rerun that
request (if it was guilty, we replace the hanging user payload with
NOPs). However, we
During reset, we try and stop the active ring. This has the consequence
that we often clobber the RING registers within the context image. When
we find an active request, we update the context image to rerun that
request (if it was guilty, we replace the hanging user payload with
NOPs). However, we
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev3)
URL : https://patchwork.freedesktop.org/series/59174/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5891 -> Patchwork_12730
S
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev3)
URL : https://patchwork.freedesktop.org/series/59174/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
bd2bb565e3c4 drm/i915/execlists: Always reset the context's RING registers
-:17:
On Sun, 2019-04-07 at 02:45 +, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/4] drm/i915/psr: Update PSR2 SU
> corruption workaround comment
> URL : https://patchwork.freedesktop.org/series/59087/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes fr
== Series Details ==
Series: Core-for-CI:ICL_only Disable ACPI idle driver
URL : https://patchwork.freedesktop.org/series/59170/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5888_full -> Patchwork_12727_full
Summary
--
On 4/7/19 12:26 PM, Chris Wilson wrote:
A couple of machines in the farm show quite frequent errors in the
powerwells not being released. Either there is an external agent
interferring with the powerwells, or the powerwell doesn't quite behave
as we anticipate -- either way, the test is not rel
Quoting Ville Syrjälä (2019-04-08 17:06:01)
> On Mon, Apr 08, 2019 at 04:49:13PM +0100, Chris Wilson wrote:
> > Quoting Ville Syrjala (2019-04-08 16:27:02)
> > > - /*
> > > -* Adjust the original formula to delay the division by 2^22 in
> > > order to
> > > -* minimize possib
On Fri, Apr 05, 2019 at 09:34:42AM -0700, Clinton Taylor wrote:
> What happened to the reset of the patch?
It should have been a separate patch. Also I think this [1] oneliner
might be all we need.
[1] https://lists.freedesktop.org/archives/intel-gfx/2019-April/194708.html
>
> -Clint
>
>
> On
== Series Details ==
Series: series starting with [1/2] drm/i915: Use mul_u32_u32() more
URL : https://patchwork.freedesktop.org/series/59180/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5888 -> Patchwork_12729
Summary
--
Quoting Ville Syrjälä (2019-04-08 17:06:01)
> On Mon, Apr 08, 2019 at 04:49:13PM +0100, Chris Wilson wrote:
> > Quoting Ville Syrjala (2019-04-08 16:27:02)
> > > - /*
> > > -* Adjust the original formula to delay the division by 2^22 in
> > > order to
> > > -* minimize possib
On Mon, Apr 08, 2019 at 03:59:51PM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf
> >Of Ville
> >Syrjälä
> >Sent: Monday, April 8, 2019 9:15 PM
> >To: Shankar, Uma
> >Cc: dcasta...@chromium.org; intel-gf
On Mon, Apr 08, 2019 at 04:49:13PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2019-04-08 16:27:02)
> > - /*
> > -* Adjust the original formula to delay the division by 2^22 in
> > order to
> > -* minimize possible rounding errors.
> > -*/
> > - tmp = (u
On 08/04/2019 16:57, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2019-04-08 15:54:01)
On 08/04/2019 10:17, Chris Wilson wrote:
As we push for better compartmentalisation, it is more convenient to
copy the default sseu configuration from the engine into the derived
logical context, than it is
Quoting Tvrtko Ursulin (2019-04-08 15:56:39)
>
> On 08/04/2019 10:17, Chris Wilson wrote:
> > Split out the powermanagement portion (GT wakeref, suspend/resume) of
> > GEM from i915_gem.c into its own file.
>
> This is the same patch I gave r-b on before? Judging from the title and
> commit mess
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ville
>Syrjälä
>Sent: Monday, April 8, 2019 9:15 PM
>To: Shankar, Uma
>Cc: dcasta...@chromium.org; intel-gfx@lists.freedesktop.org; dri-
>de...@lists.freedesktop.org; seanp...@chromium.or
Quoting Tvrtko Ursulin (2019-04-08 15:54:01)
>
> On 08/04/2019 10:17, Chris Wilson wrote:
> > As we push for better compartmentalisation, it is more convenient to
> > copy the default sseu configuration from the engine into the derived
> > logical context, than it is to dig it out from i915->runti
Quoting Ville Syrjala (2019-04-08 16:27:02)
> - /*
> -* Adjust the original formula to delay the division by 2^22 in order
> to
> -* minimize possible rounding errors.
> -*/
> - tmp = (u64)m1 * m2_int * ref_clock +
> - (((u64)m1 * m2_frac * ref_clock
During reset, we try and stop the active ring. This has the consequence
that we often clobber the RING registers within the context image. When
we find an active request, we update the context image to rerun that
request (if it was guilty, we replace the hanging user payload with
NOPs). However, we
On Mon, Apr 08, 2019 at 03:40:39PM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
> >Sent: Monday, April 8, 2019 8:27 PM
> >To: Shankar, Uma
> >Cc: dcasta...@chromium.org; intel-gfx@lists.freedesktop.org; dri-
> >de...@l
Quoting Ville Syrjala (2019-04-08 16:27:01)
> From: Ville Syrjälä
>
> We have a lot of '(u64)foo * bar' everywhere. Replace with
> mul_u32_u32() to avoid gcc failing to use a regular 32x32->64
> multiply for this.
>
> Signed-off-by: Ville Syrjälä
As a purely mechanical translation,
Reviewed-by
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Monday, April 8, 2019 8:27 PM
>To: Shankar, Uma
>Cc: dcasta...@chromium.org; intel-gfx@lists.freedesktop.org; dri-
>de...@lists.freedesktop.org; seanp...@chromium.org; Syrjala, Ville
>; Lankhorst, Maar
On Sun, Apr 07, 2019 at 02:40:18PM +, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [v2,1/2] drm/i915: Get power refs in
> encoder->get_power_domains() (rev2)
> URL : https://patchwork.freedesktop.org/series/59071/
> State : failure
Thanks for the review, pushed
== Series Details ==
Series: series starting with [1/2] drm/i915: Use mul_u32_u32() more
URL : https://patchwork.freedesktop.org/series/59180/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Use mul_u32_u32() more
-O:drivers/gpu/drm/i915/intel
Quoting Chris Wilson (2019-04-08 14:40:25)
> During reset, we try and stop the active ring. This has the consequence
> that we often clobber the RING registers within the context image. When
> we find an active request, we update the context image to rerun that
> request (if it was guilty, we repla
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev2)
URL : https://patchwork.freedesktop.org/series/59174/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5888 -> Patchwork_12728
S
From: Ville Syrjälä
Write some icl pll calculations in a more straightforward way.
We have just enough bits for the full divisor.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_ddi.c | 15 ---
drivers/gpu/drm/i915/intel_dpll_mgr.c | 2 +-
2 files changed, 5 inser
From: Ville Syrjälä
We have a lot of '(u64)foo * bar' everywhere. Replace with
mul_u32_u32() to avoid gcc failing to use a regular 32x32->64
multiply for this.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_fixed.h | 6 +++---
drivers/gpu/drm/i915/intel_display.c | 10 +--
On 08/04/2019 10:17, Chris Wilson wrote:
In order to separate the reservation phase of building a request from
its emission phase, we need to pull some of the request alloc activities
from deep inside i915_request to the surface, GEM_EXECBUFFER.
I had some comments and gave conditional r-b on
== Series Details ==
Series: drm/i915/execlists: Always reset the context's RING registers (rev2)
URL : https://patchwork.freedesktop.org/series/59174/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
032a44d4e5e1 drm/i915/execlists: Always reset the context's RING registers
-:17:
== Series Details ==
Series: Core-for-CI:ICL_only Disable ACPI idle driver
URL : https://patchwork.freedesktop.org/series/59170/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5888 -> Patchwork_12727
Summary
---
**SUC
== Series Details ==
Series: snd/hda: Detangle unwind to avoid double release of display powerwell
(rev2)
URL : https://patchwork.freedesktop.org/series/59158/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5887_full -> Patchwork_12725_full
On 08/04/2019 10:17, Chris Wilson wrote:
Simply the setup slightly for the sseu selftests to use the actual
kernel_context.
Signed-off-by: Chris Wilson
---
.../gpu/drm/i915/selftests/i915_gem_context.c | 17 -
1 file changed, 4 insertions(+), 13 deletions(-)
diff --git a/
On Thu, Apr 04, 2019 at 09:38:03PM +, Jim Zhang wrote:
> Dear Sir/Madam:
>
> I am having an issue with intel Baytrail GPU DRM driver.
>
> Description:
> Linux kernel version 3.10.61:
> Afer calling function
> properties = drmModeObjectGetProperties(drmfd, plane_id,
> DRM_MODE_OBJECT_PLANE);
On 08/04/2019 10:17, Chris Wilson wrote:
Circumvent the dance we currently perform to find the preempt_client and
lookup its HW context for this engine, as we know we have already pinned
the preempt_context on the engine.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/intel_guc_submiss
On Mon, Apr 08, 2019 at 02:40:51PM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
> >Sent: Monday, April 8, 2019 6:01 PM
> >To: Shankar, Uma
> >Cc: dcasta...@chromium.org; intel-gfx@lists.freedesktop.org; dri-
> >de...@l
On 08/04/2019 10:17, Chris Wilson wrote:
Split out the powermanagement portion (GT wakeref, suspend/resume) of
GEM from i915_gem.c into its own file.
This is the same patch I gave r-b on before? Judging from the title and
commit message I'd say yes. But I know it is not, don't worry.
Regard
On 08/04/2019 10:17, Chris Wilson wrote:
As we push for better compartmentalisation, it is more convenient to
copy the default sseu configuration from the engine into the derived
logical context, than it is to dig it out from i915->runtime_info.
Why it is more convenient?
Signed-off-by: Chr
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 7769db588384 drm/i915/dp: optimize eDP 1.4+ link config fast and
narrow.
The bot has tested the following trees: v5.0.7.
v5.0.7: Failed to apply! Possible dependencies:
204474
>-Original Message-
>From: Sam Ravnborg [mailto:s...@ravnborg.org]
>Sent: Tuesday, April 2, 2019 12:07 AM
>To: Shankar, Uma
>Cc: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
>dcasta...@chromium.org; emil.l.veli...@gmail.com; seanp...@chromium.org;
>Syrjala, Ville ; L
On Thu, 04 Apr 2019, Jim Zhang wrote:
> Dear Sir/Madam:
>
> I am having an issue with intel Baytrail GPU DRM driver.
>
> Description:
> Linux kernel version 3.10.61:
> Afer calling function
> properties = drmModeObjectGetProperties(drmfd, plane_id,
> DRM_MODE_OBJECT_PLANE);
> it only returns onl
== Series Details ==
Series: drm/i915: Clean up cherryview_load_luts()
URL : https://patchwork.freedesktop.org/series/59169/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5888 -> Patchwork_12726
Summary
---
**FAILURE
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Sam
>Ravnborg
>Sent: Tuesday, April 2, 2019 12:03 AM
>To: Shankar, Uma
>Cc: dcasta...@chromium.org; intel-gfx@lists.freedesktop.org;
>emil.l.veli...@gmail.com; dri-de...@lists.freedesktop
On 08/04/2019 10:17, Chris Wilson wrote:
The timeline is strictly ordered, so by inserting the timeline->barrier
request into the timeline->last_request it naturally provides the same
barrier. Consolidate the pair of barriers into one as they serve the
same purpose.
Signed-off-by: Chris Wilson
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Monday, April 8, 2019 6:01 PM
>To: Shankar, Uma
>Cc: dcasta...@chromium.org; intel-gfx@lists.freedesktop.org; dri-
>de...@lists.freedesktop.org; seanp...@chromium.org; Syrjala, Ville
>; Lankhorst, Maar
On 08/04/2019 10:17, Chris Wilson wrote:
In order to avoid the malloc inside i915_globals_park() occurring
underneath a lock connected to the shrinker (thus causing circular
lockdeps warnings), move the rcu_worker to a global.
<4> [39.085073]
On 08/04/2019 10:17, Chris Wilson wrote:
Replace the WARN with a simple if() + error message to squech the sparse
warning that entire wait_for() macro was being stringified:
drivers/gpu/drm/i915/intel_guc_submission.c:658:9: error: too long token
expansion
Signed-off-by: Chris Wilson
---
d
Generated using make headers_install from the drm-next
tree - git://anongit.freedesktop.org/drm/drm
branch - drm-next
commit - 14d2bd53a47a7e1cb3e03d00a6b952734cf90f3f
The changes were as follows :-
core: (drm.h, drm_fourcc.h, drm_mode.h)
- Added 'struct drm_syncobj_transfer', 'struct drm_syncobj
During reset, we try and stop the active ring. This has the consequence
that we often clobber the RING registers within the context image. When
we find an active request, we update the context image to rerun that
request (if it was guilty, we replace the hanging user payload with
NOPs). However, we
During reset, we try and stop the active ring. This has the consequence
that we often clobber the RING registers within the context image. When
we find an active request, we update the context image to rerun that
request (if it was guilty, we replace the hanging user payload with
NOPs). However, we
+ Rafael, Mika.
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
> Anshuman Gupta
> Sent: maanantai 8. huhtikuuta 2019 15.22
> To: intel-gfx@lists.freedesktop.org
> Cc: Peres, Martin ; Vetter, Daniel
>
> Subject: [Intel-gfx] [PATCH] Cor
Quoting Patchwork (2019-04-08 13:51:08)
> Warnings
>
> * igt@i915_pm_rpm@module-reload:
> - fi-glk-dsi: DMESG-WARN [fdo#105538] / [fdo#107732] /
> [fdo#109513] -> INCOMPLETE [fdo#103359] / [k.org#198133]
In other words, no that wasn't the fix it purported to be.
-Chris
__
== Series Details ==
Series: snd/hda: Detangle unwind to avoid double release of display powerwell
(rev2)
URL : https://patchwork.freedesktop.org/series/59158/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5887 -> Patchwork_12725
==
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Monday, April 8, 2019 3:50 PM
>To: Shankar, Uma
>Cc: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
>dcasta...@chromium.org; seanp...@chromium.org; Syrjala, Ville
>; harry.wentl...@a
On Mon, Apr 08, 2019 at 12:26:23PM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf
> >Of Ville
> >Syrjälä
> >Sent: Friday, April 5, 2019 9:42 PM
> >To: Shankar, Uma
> >Cc: dcasta...@chromium.org; intel-gf
>-Original Message-
>From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
>Sent: Monday, April 8, 2019 3:39 PM
>To: Shankar, Uma
>Cc: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
>Lankhorst,
>Maarten ; Syrjala, Ville
>;
>Sharma, Shashank ; emil.l.veli...@gmai
/commits/Chris-Wilson/snd-hda-Detangle-unwind-to-avoid-double-release-of-display-powerwell/20190408-185235
base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
config: i386-randconfig-x012-201914 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Ville
>Syrjälä
>Sent: Friday, April 5, 2019 9:42 PM
>To: Shankar, Uma
>Cc: dcasta...@chromium.org; intel-gfx@lists.freedesktop.org; dri-
>de...@lists.freedesktop.org; seanp...@chromium.or
There were system hung observed while running i915_pm_rpm test.
FDO https://bugs.freedesktop.org/show_bug.cgi?id=108840
Root cause is believed to due to page fault in ACPI idle (FDO comment 18)
driver, it has been suggested by Daniel to disable ACPI idle
driver for CI system, this patch only meant
== Series Details ==
Series: snd/hda: Detangle unwind to avoid double release of display powerwell
(rev2)
URL : https://patchwork.freedesktop.org/series/59158/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c354dafa354d snd/hda: Detangle unwind to avoid double release of displa
From: Ville Syrjälä
I like my functions simple, so split up the low level bits from
cherryview_load_luts() into separate functions. Also rename the
whole thing to chv_load_luts() to match the new world order.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_color.c | 98
On Mon, Apr 08, 2019 at 09:16:34AM +0300, Jani Nikula wrote:
> On Fri, 05 Apr 2019, Imre Deak wrote:
> > On Fri, Apr 05, 2019 at 05:13:49PM +0300, Ville Syrjala wrote:
> >> From: Ville Syrjälä
> >>
> >> The only bpc information in pipe registers for BXT/GLK DSI
> >> is the PIPEMISC dither bpc. L
<4> [265.019572] Unmatched wakeref (tracking 3), count 3
<4> [265.019680] WARNING: CPU: 1 PID: 163 at
drivers/gpu/drm/i915/intel_runtime_pm.c:162
cancel_intel_runtime_pm_wakeref+0x87/0x160 [i915]
<4> [265.019682] Modules linked in: snd_hda_intel i915 vgem snd_hda_codec_hdmi
snd_hda_codec_realtek
== Series Details ==
Series: snd/hda: Detangle unwind to avoid double release of display powerwell
URL : https://patchwork.freedesktop.org/series/59158/
State : failure
== Summary ==
CALLscripts/checksyscalls.sh
CALLscripts/atomic/check-atomics.sh
DESCEND objtool
CHK include
Quoting Patchwork (2019-04-08 11:28:00)
> == Series Details ==
>
> Series: series starting with [01/29] drm/i915: Mark up ips for RCU protection
> URL : https://patchwork.freedesktop.org/series/59155/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5887 -> Patchwork_12
== Series Details ==
Series: series starting with [01/29] drm/i915: Mark up ips for RCU protection
URL : https://patchwork.freedesktop.org/series/59155/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5887 -> Patchwork_12723
On Mon, Apr 01, 2019 at 11:00:09PM +0530, Uma Shankar wrote:
> Gen11 introduced a new gamma mode i.e, multi segmented
> gamma mode. Added support for the same.
>
> Signed-off-by: Uma Shankar
> ---
> drivers/gpu/drm/i915/intel_color.c | 161
> -
> include/drm/
On 2019-04-02 22:20, Uma Shankar wrote:
> This patch adds a blob property to get HDR metadata
> information from userspace. This will be send as part
> of AVI Infoframe to panel.
>
> It also implements get() and set() functions for HDR output
> metadata property.The blob data is received from users
== Series Details ==
Series: series starting with [01/29] drm/i915: Mark up ips for RCU protection
URL : https://patchwork.freedesktop.org/series/59155/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Mark up ips for RCU protection
-drivers/gp
From: Tvrtko Ursulin
Signed-off-by: Tvrtko Ursulin
---
lib/igt_dummyload.c | 39 +--
lib/igt_gt.c| 14 --
lib/igt_gt.h| 2 --
tests/perf_pmu.c| 44
4 files changed, 73 insertions(+)
On Mon, Apr 01, 2019 at 11:00:06PM +0530, Uma Shankar wrote:
> From: Ville Syrjälä
>
> This defines the color lut ranges for 10bit and multi
> segmented gamma range for ICL.
>
> Signed-off-by: Ville Syrjälä
> Signed-off-by: Uma Shankar
> ---
> drivers/gpu/drm/i915/intel_color.c | 301
> +
== Series Details ==
Series: series starting with [01/29] drm/i915: Mark up ips for RCU protection
URL : https://patchwork.freedesktop.org/series/59155/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
17875d38d33a drm/i915: Mark up ips for RCU protection
bb6133046abe drm/i915/guc
On Fri, Apr 05, 2019 at 03:48:21PM -0700, Manasi Navare wrote:
> Currently we use force_dsc_enable to force DSC from IGT, but
> we dont expose this value to userspace through debugfs.
> This patch exposes this through the same dsc_fec_support
> debugfs node per connector so that we can restore its
<4> [265.019572] Unmatched wakeref (tracking 3), count 3
<4> [265.019680] WARNING: CPU: 1 PID: 163 at
drivers/gpu/drm/i915/intel_runtime_pm.c:162
cancel_intel_runtime_pm_wakeref+0x87/0x160 [i915]
<4> [265.019682] Modules linked in: snd_hda_intel i915 vgem snd_hda_codec_hdmi
snd_hda_codec_realtek
1 - 100 of 134 matches
Mail list logo
