== Series Details ==
Series: HDCP1.4 Fixes - II
URL : https://patchwork.freedesktop.org/series/53493/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5261_full -> Patchwork_11012_full
Summary
---
**FAILURE**
Hi Jani,
I've tried previously with branch icl-dsi-2018-12-03 for your github repo.
I think it has everything except this 4.12.2018 "fix transcoder state readout"
commit.
I will apply it and try with that now, thanks.
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC
On 04.12.2018 20:02, Ville Syrjälä wrote:
> On Tue, Dec 04, 2018 at 08:03:53AM +0100, Andrzej Hajda wrote:
>> On 03.12.2018 22:48, Ville Syrjälä wrote:
>>> On Thu, Nov 29, 2018 at 09:46:16AM +0100, Andrzej Hajda wrote:
Quite late, hopefully not too late.
On 21.11.2018 12:51,
Hi Ville,
On Tuesday, 4 December 2018 21:13:20 EET Ville Syrjälä wrote:
> On Tue, Dec 04, 2018 at 08:46:53AM +0100, Andrzej Hajda wrote:
> > On 03.12.2018 22:38, Ville Syrjälä wrote:
> >> On Thu, Nov 29, 2018 at 10:08:07AM +0100, Andrzej Hajda wrote:
> >>> On 21.11.2018 19:19, Laurent Pinchart
== Series Details ==
Series: drm/i915: Dial down workaround debug messages
URL : https://patchwork.freedesktop.org/series/53490/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5260_full -> Patchwork_11011_full
Summary
== Series Details ==
Series: drm/i915/fbc/cnl: Add GLK and CNL+ hardware tracking area
URL : https://patchwork.freedesktop.org/series/53515/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5263 -> Patchwork_11016
Summary
GLK and CNL+ supports a bigger FBC tracking area.
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/intel_fbc.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_fbc.c b/drivers/gpu/drm/i915/intel_fbc.c
index
== Series Details ==
Series: drm/i915/icl: combo port vswing programming changes per BSPEC (rev3)
URL : https://patchwork.freedesktop.org/series/53340/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5263 -> Patchwork_11015
== Series Details ==
Series: drm/i915/icl: combo port vswing programming changes per BSPEC (rev3)
URL : https://patchwork.freedesktop.org/series/53340/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9a181831a873 drm/i915/icl: combo port vswing programming changes per BSPEC
From: Clint Taylor
In August 2018 the BSPEC changed the ICL port programming sequence to
closely resemble earlier gen programming sequence.
v2: remove debug code that Imre found
v3: simplify translation table if-else
BSpec: 21257
Cc: Ville Syrjälä
Cc: Imre Deak
Cc: Rodrigo Vivi
== Series Details ==
Series: series starting with [1/5] drm/i915/psr: Allow PSR2 to be enabled when
debugfs asks
URL : https://patchwork.freedesktop.org/series/53510/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5263 -> Patchwork_11014
== Series Details ==
Series: series starting with [1/5] drm/i915/psr: Allow PSR2 to be enabled when
debugfs asks
URL : https://patchwork.freedesktop.org/series/53510/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7d15d6359a35 drm/i915/psr: Allow PSR2 to be enabled when
This register contains how many blocks was sent in the past selective
updates.
Those registers are not kept set all the times but pulling it after flip
can show that the expected values are set for the current frame and the
previous ones too.
Cc: Rodrigo Vivi
Cc: Dhinakaran Pandiyan
The value of this registers will be used to test if PSR2 is doing
selective update and if the number of blocks match with the expected.
Cc: Rodrigo Vivi
Cc: Dhinakaran Pandiyan
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/i915_debugfs.c | 42 ++---
1
For now PSR2 is still disabled by default for all platforms but is
our intention to let debugfs to enable it for debug and tests
proporses, so intel_psr2_enabled() that is also used by debugfs to
decide if PSR2 is going to be enabled needs to take in consideration
the debug field.
Cc: Dhinakaran
PSR2 only trigger interruptions for AUX error, so let's not print
useless information in debugsfs.
Also adding a comment to intel_psr_irq_handler() about that.
Cc: Rodrigo Vivi
Cc: Dhinakaran Pandiyan
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
The old debugfs fields was not following a naming partern and it was
a bit confusing.
So it went from:
~$ sudo more /sys/kernel/debug/dri/0/i915_edp_psr_status
Sink_Support: yes
PSR mode: PSR1
Enabled: yes
Busy frontbuffer bits: 0x000
Main link in standby mode: no
HW Enabled & Active bit: yes
== Series Details ==
Series: series starting with [1/7] drm/i915: Allocate a common scratch page
URL : https://patchwork.freedesktop.org/series/53477/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5256_full -> Patchwork_11010_full
On Thu, 2018-11-15 at 12:57 -0800, Souza, Jose wrote:
> On Mon, 2018-11-12 at 11:17 +0100, Maarten Lankhorst wrote:
> > Op 09-11-18 om 21:20 schreef José Roberto de Souza:
> > > If panel supports DRRS and PSR and if driver is loaded without
> > > PSR
> > > enabled, driver will enable DRRS as
On Tue, 2018-12-04 at 10:52 -0800, Souza, Jose wrote:
> On Mon, 2018-12-03 at 18:58 -0800, Dhinakaran Pandiyan wrote:
> > On Mon, 2018-12-03 at 17:54 -0800, Souza, Jose wrote:
> > > On Mon, 2018-12-03 at 17:33 -0800, Dhinakaran Pandiyan wrote:
> > > > On Thu, 2018-11-29 at 18:31 -0800, José
Patches merged to drm-intel-next-queued, thanks for the reviews DK and
Rodrigo.
On Tue, 2018-12-04 at 03:05 +, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [v4,1/9] drm/i915: Disable PSR in Apple
> panels
> URL : https://patchwork.freedesktop.org/series/53448/
>
== Series Details ==
Series: drm/i915/dsc: Add Per connector debugfs node for DSC support/enable
(rev2)
URL : https://patchwork.freedesktop.org/series/53449/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5262 -> Patchwork_11013
== Series Details ==
Series: drm/i915/dsc: Add Per connector debugfs node for DSC support/enable
(rev2)
URL : https://patchwork.freedesktop.org/series/53449/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
60eb08c39119 drm/i915/dsc: Add Per connector debugfs node for DSC
On Tue, 2018-12-04 at 12:02 -0800, Dhinakaran Pandiyan wrote:
> On Mon, 2018-12-03 at 16:34 -0800, José Roberto de Souza wrote:
> > According to eDP spec, sink can required specific selective update
> > granularity that source must comply.
> > Here caching the value if required and checking if
On Mon, 2018-12-03 at 16:34 -0800, José Roberto de Souza wrote:
> According to eDP spec, sink can required specific selective update
> granularity that source must comply.
> Here caching the value if required and checking if source supports
> it.
>
> v3:
> - Returning the default granularity in
DSC can be supported per DP connector. This patch adds a per connector
debugfs node to expose DSC support capability by the kernel.
The same node can be used from userspace to force DSC enable.
force_dsc_en written through this debugfs node is used to force
DSC even for lower resolutions.
v6:
*
On Tue, Dec 04, 2018 at 11:46:39AM +0200, Mika Kahola wrote:
> Occasionally, we get the following error in our CI runs
>
> [853.132830] Workqueue: events i915_hotplug_work_func [i915]
> [853.132844] RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0
> [853.132852] Code: fe ff ff e8 b7 4e a6 ff 48 89 e6 4c
On Tue, Dec 04, 2018 at 11:37:05PM +0530, Ramalingam C wrote:
> HDCP1.4 is enabled and validated only on GEN9+ platforms.
>
> Signed-off-by: Ramalingam C
> Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/i915/intel_hdcp.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git
On Tue, Dec 04, 2018 at 08:46:53AM +0100, Andrzej Hajda wrote:
> On 03.12.2018 22:38, Ville Syrjälä wrote:
> > On Thu, Nov 29, 2018 at 10:08:07AM +0100, Andrzej Hajda wrote:
> >> On 21.11.2018 19:19, Laurent Pinchart wrote:
> >>> Hi Ville,
> >>>
> >>> Thank you for the patch.
> >>>
> >>> On
On Tue, Dec 04, 2018 at 08:03:53AM +0100, Andrzej Hajda wrote:
> On 03.12.2018 22:48, Ville Syrjälä wrote:
> > On Thu, Nov 29, 2018 at 09:46:16AM +0100, Andrzej Hajda wrote:
> >> Quite late, hopefully not too late.
> >>
> >>
> >> On 21.11.2018 12:51, Ville Syrjälä wrote:
> >>> On Wed, Nov 21, 2018
Quoting Patchwork (2018-12-04 18:35:08)
> == Series Details ==
>
> Series: drm/i915: Dial down workaround debug messages
> URL : https://patchwork.freedesktop.org/series/53490/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5260 -> Patchwork_11011
>
== Series Details ==
Series: HDCP1.4 Fixes - II
URL : https://patchwork.freedesktop.org/series/53493/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5261 -> Patchwork_11012
Summary
---
**SUCCESS**
No regressions
On Mon, 2018-12-03 at 18:58 -0800, Dhinakaran Pandiyan wrote:
> On Mon, 2018-12-03 at 17:54 -0800, Souza, Jose wrote:
> > On Mon, 2018-12-03 at 17:33 -0800, Dhinakaran Pandiyan wrote:
> > > On Thu, 2018-11-29 at 18:31 -0800, José Roberto de Souza wrote:
> > > > Changing the i915_edp_psr_debug was
== Series Details ==
Series: drm/i915: Dial down workaround debug messages
URL : https://patchwork.freedesktop.org/series/53490/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5260 -> Patchwork_11011
Summary
---
HDCP1.4 key load process varies between Intel platform to platform.
For Gen9 platforms except BXT and GLK, HDCP1.4 key is loaded using
the GT Driver Mailbox interface. So all GEN9_BC platforms will use
the GT Driver Mailbox interface for HDCP1.4 key load.
v2:
Using the IS_GEN9_BC for filtering
HDCP1.4 is enabled and validated only on GEN9+ platforms.
Signed-off-by: Ramalingam C
Reviewed-by: Sean Paul
---
drivers/gpu/drm/i915/intel_hdcp.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_hdcp.c
b/drivers/gpu/drm/i915/intel_hdcp.c
index
At enable/disable of the HDCP encryption, for encryption status change
we need minimum one frame duration. And we might program this bit any
point(start/End) in the previous frame.
With 20mSec, observed the timeout for change in encryption status.
Since this is not time critical operation and we
Adding a debug log when the DP_AUX_NATIVE_REPLY_ACK is missing
for aksv write. This helps to locate the possible non responding
DP HDCP sinks.
v2:
Rewritten for readability [Sean Paul]
Signed-off-by: Ramalingam C
Reviewed-by: Sean Paul
---
drivers/gpu/drm/i915/intel_dp.c | 7 ++-
1 file
Couple of more HDCP1.4 fixes on
- Key load process for CFL
- Encryption status change time
- debug log addition
- active platform coverage
v1 and v2 went into old series https://patchwork.freedesktop.org/series/38978/
as v8 and v9, due to the same series title. Now changed the title.
(2018-11-22 16:49:47 +0200)
are available in the git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2018-12-04
for you to fetch changes up to 4377d4e0d3d511986033ba7b4182d5a80b7f9ea2:
drm/i915: Update DRIVER_DATE to 20181204 (2018-12-04 19:26:17 +0200
Hello,
I'm having an issue with my Dell laptop detecting an HDMI TV. My laptop is
running Ubuntu 18.04. Are you able to help me?
Regards,
Daniel
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
Quoting Tvrtko Ursulin (2018-12-04 17:15:30)
> From: Tvrtko Ursulin
>
> For selftests like live_hangcheck, which does thousands of reset per
> second, it is too verbose to log every time we re-apply the workarounds.
>
> Remove those messages since, coupled with the dedicated selftest, it is
>
From: Tvrtko Ursulin
For selftests like live_hangcheck, which does thousands of reset per
second, it is too verbose to log every time we re-apply the workarounds.
Remove those messages since, coupled with the dedicated selftest, it is
sufficient to only log the number of recorded workarounds at
On Tue, 04 Dec 2018, "Lisovskiy, Stanislav"
wrote:
> Hi,
>
> Currently ICL DSI panel seems to work fine, however I still face
> mainly two issues, which probably need to be addressed:
Please try with current drm-tip with
commit 0716931a82b4d0e211d2ef66616ad7130107e455
Author: Jani Nikula
On Tue, 04 Dec 2018, Imre Deak wrote:
> On Tue, Dec 04, 2018 at 12:19:26PM +0200, Jani Nikula wrote:
>> Commit 2ca711caeca2 ("drm/i915/icl: Consider DSI for getting transcoder
>> state") clobbers the previously read TRANS_DDI_FUNC_CTL_EDP register
>> contents with TRANS_DDI_FUNC_CTL_DSI0
Hi,
Currently ICL DSI panel seems to work fine, however I still face mainly two
issues,
which probably need to be addressed:
1) There is still pipe_config mismatch assertion:
[ 13.119965] [drm:pipe_config_err [i915]] *ERROR* mismatch in
base.adjusted_mode.crtc_hdisplay (expected 1440, found
Quoting Mika Kuoppala (2018-12-04 15:07:01)
> Chris Wilson writes:
>
> > Currently we allocate a scratch page for each engine, but since we only
> > ever write into it for post-sync operations, it is not exposed to
> > userspace nor do we care for coherency. As we then do not care about its
> >
Quoting Patchwork (2018-12-04 14:48:15)
> == Series Details ==
>
> Series: series starting with [1/7] drm/i915: Allocate a common scratch page
> URL : https://patchwork.freedesktop.org/series/53477/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5256 ->
Chris Wilson writes:
> Currently we allocate a scratch page for each engine, but since we only
> ever write into it for post-sync operations, it is not exposed to
> userspace nor do we care for coherency. As we then do not care about its
> contents, we can use one page for all, reducing our
== Series Details ==
Series: drm/i915/icl: fix transcoder state readout
URL : https://patchwork.freedesktop.org/series/53465/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5251_full -> Patchwork_11009_full
Summary
---
== Series Details ==
Series: series starting with [1/7] drm/i915: Allocate a common scratch page
URL : https://patchwork.freedesktop.org/series/53477/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5256 -> Patchwork_11010
== Series Details ==
Series: series starting with [1/7] drm/i915: Allocate a common scratch page
URL : https://patchwork.freedesktop.org/series/53477/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Allocate a common scratch page
== Series Details ==
Series: series starting with [1/7] drm/i915: Allocate a common scratch page
URL : https://patchwork.freedesktop.org/series/53477/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
2fc4093e46e8 drm/i915: Allocate a common scratch page
90bafab654fd drm/i915:
Currently we face a severe problem on Braswell that manifests as invalid
ppGTT accesses. The code tries to maintain the PDP (page directory
pointers) inside the context in two ways, direct write into the context
and a pipelined LRI update. The direct write into the context is
fundamentally racy as
Impose a restraint that we have all vma pinned for a request prior to
its allocation. This is to simplify request construction, and should
facilitate unravelling the lock interdependencies later.
Signed-off-by: Chris Wilson
Reviewed-by: Tvrtko Ursulin
---
Currently we allocate a scratch page for each engine, but since we only
ever write into it for post-sync operations, it is not exposed to
userspace nor do we care for coherency. As we then do not care about its
contents, we can use one page for all, reducing our allocations and
avoid complications
Adding an extra MI_STORE_DWORD_IMM to the gpu relocation path for gen3
was good, but still not good enough. To survive 24+ hours under test we
needed to perform not one, not two but three extra store-dw. Doing so
for each GPU relocation was a little unsightly and since we need to
worry about
Since commit 93065ac753e4 ("mm, oom: distinguish blockable mode for mmu
notifiers") we have been able to report failure from
mmu_invalidate_range_start which allows us to use a trylock on the
struct_mutex to avoid potential recursion and report -EBUSY instead.
Furthermore, this allows us to pull
We want to exclude any GGTT objects from being present on our internal
lists to avoid the deadlock we may run into with our requirement for
struct_mutex during invalidate. However, if the gup_fast fails, we put
the userptr onto the workqueue and mark it as active, so that we
remember to serialise
Ignore trying to shrink from i915 if we fail to acquire the struct_mutex
in the shrinker while performing direct-reclaim. The trade-off being
(much) lower latency for non-i915 clients at an increased risk of being
unable to obtain a page from direct-reclaim without hitting the
oom-notifier. The
On Tue, 2018-12-04 at 11:41 +, Chris Wilson wrote:
> Quoting Mika Kahola (2018-12-04 09:46:39)
> > Occasionally, we get the following error in our CI runs
> >
> > [853.132830] Workqueue: events i915_hotplug_work_func [i915]
> > [853.132844] RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0
> >
== Series Details ==
Series: drm/i915: Wait one vblank before sending hotplug event to userspace
URL : https://patchwork.freedesktop.org/series/53463/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5250_full -> Patchwork_11008_full
On 04/12/2018 08:41, Patchwork wrote:
== Series Details ==
Series: Restore workarounds after engine reset and unify their handling (rev8)
URL : https://patchwork.freedesktop.org/series/53313/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5247 -> Patchwork_11000
On Thu, 29 Nov 2018, Stanislav Lisovskiy wrote:
> Currently kernel might allocate different connector ids
> for the same outputs in case of DP MST, which seems to
> confuse userspace. There are can be different connector
> ids in the list, which could be assigned to the same
> output, while being
Quoting Patchwork (2018-12-04 09:42:41)
> == Series Details ==
>
> Series: Restore workarounds after engine reset and unify their handling (rev9)
> URL : https://patchwork.freedesktop.org/series/53313/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5250_full ->
Quoting Tvrtko Ursulin (2018-12-04 11:53:22)
>
> On 03/12/2018 11:37, Chris Wilson wrote:
> > Currently we face a severe problem on Braswell that manifests as invalid
> > ppGTT accesses. The code tries to maintain the PDP (page directory
> > pointers) inside the context in two ways, direct write
On 03/12/2018 11:37, Chris Wilson wrote:
Currently we face a severe problem on Braswell that manifests as invalid
ppGTT accesses. The code tries to maintain the PDP (page directory
pointers) inside the context in two ways, direct write into the context
and a pipelined LRI update. The direct
Quoting Mika Kahola (2018-12-04 09:46:39)
> Occasionally, we get the following error in our CI runs
>
> [853.132830] Workqueue: events i915_hotplug_work_func [i915]
> [853.132844] RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0
> [853.132852] Code: fe ff ff e8 b7 4e a6 ff 48 89 e6 4c 89 ff e8 6c 5f ab
On Tue, Dec 04, 2018 at 12:19:26PM +0200, Jani Nikula wrote:
> Commit 2ca711caeca2 ("drm/i915/icl: Consider DSI for getting transcoder
> state") clobbers the previously read TRANS_DDI_FUNC_CTL_EDP register
> contents with TRANS_DDI_FUNC_CTL_DSI0 contents. Fix the state readout,
> and handle DSI 1
On 03/12/2018 22:55, Vivi, Rodrigo wrote:
> On Mon, Dec 03, 2018 at 04:29:17AM -0800, Peres, Martin wrote:
>> On 30/11/2018 19:27, Vivi, Rodrigo wrote:
>>> On Fri, Nov 30, 2018 at 03:04:40PM +0200, Martin Peres wrote:
On 29/11/2018 19:36, Rodrigo Vivi wrote:
> On Wed, Nov 28,
== Series Details ==
Series: series starting with [1/8] drm/i915/breadcrumbs: Reduce
missed-breadcrumb false positive rate (rev2)
URL : https://patchwork.freedesktop.org/series/53396/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5247_full -> Patchwork_11001_full
== Series Details ==
Series: drm/i915/icl: fix transcoder state readout
URL : https://patchwork.freedesktop.org/series/53465/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5251 -> Patchwork_11009
Summary
---
On 03/12/2018 11:37, Chris Wilson wrote:
Impose a restraint that we have all vma pinned for a request prior to
its allocation. This is to simplify request construction, and should
facilitate unravelling the lock interdependencies later.
Signed-off-by: Chris Wilson
---
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it
(rev2)
URL : https://patchwork.freedesktop.org/series/53341/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5247_full -> Patchwork_11002_full
On 03/12/2018 17:36, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2018-12-03 17:11:59)
On 03/12/2018 11:36, Chris Wilson wrote:
We inspect the requests under the assumption that they will be marked as
completed when they are removed from the queue. Currently however, in the
process of wedging
== Series Details ==
Series: drm/i915: Wait one vblank before sending hotplug event to userspace
URL : https://patchwork.freedesktop.org/series/53463/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5250 -> Patchwork_11008
Commit 2ca711caeca2 ("drm/i915/icl: Consider DSI for getting transcoder
state") clobbers the previously read TRANS_DDI_FUNC_CTL_EDP register
contents with TRANS_DDI_FUNC_CTL_DSI0 contents. Fix the state readout,
and handle DSI 1 while at it.
Use a bitmask for iterating and logging transcoders,
Quoting Mika Kahola (2018-12-04 09:46:39)
> Occasionally, we get the following error in our CI runs
What's the actual warn here? This looks to be trimmed too much.
> [853.132830] Workqueue: events i915_hotplug_work_func [i915]
> [853.132844] RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0
> 15 ff ff
Occasionally, we get the following error in our CI runs
[853.132830] Workqueue: events i915_hotplug_work_func [i915]
[853.132844] RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0
[853.132852] Code: fe ff ff e8 b7 4e a6 ff 48 89 e6 4c 89 ff e8 6c 5f ab ff 45
85 ed 0f 85
15 ff ff ff 89 ee 48 c7 c7 e8 03
== Series Details ==
Series: Restore workarounds after engine reset and unify their handling (rev9)
URL : https://patchwork.freedesktop.org/series/53313/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5250_full -> Patchwork_11007_full
Quoting Manasi Navare (2018-12-03 22:55:16)
> On Tue, Nov 20, 2018 at 08:24:39PM +, Chris Wilson wrote:
> > Always show the FEC capability as it is initialised to 0 before error.
>
> That is a good point, do you think we should do the same for DSC DPCD and
> print
> that unconditionally?
== Series Details ==
Series: Restore workarounds after engine reset and unify their handling (rev8)
URL : https://patchwork.freedesktop.org/series/53313/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5247 -> Patchwork_11000
== Series Details ==
Series: series starting with [1/8] drm/i915/breadcrumbs: Reduce
missed-breadcrumb false positive rate (rev2)
URL : https://patchwork.freedesktop.org/series/53396/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5247 -> Patchwork_11001
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it
(rev2)
URL : https://patchwork.freedesktop.org/series/53341/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5247 -> Patchwork_11002
== Series Details ==
Series: Restore workarounds after engine reset and unify their handling (rev9)
URL : https://patchwork.freedesktop.org/series/53313/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5250 -> Patchwork_11007
== Series Details ==
Series: Restore workarounds after engine reset and unify their handling (rev9)
URL : https://patchwork.freedesktop.org/series/53313/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Record GT workarounds in a list
== Series Details ==
Series: Restore workarounds after engine reset and unify their handling (rev9)
URL : https://patchwork.freedesktop.org/series/53313/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8fdd7aefba3b drm/i915: Record GT workarounds in a list
506778d9ace9 drm/i915:
87 matches
Mail list logo
