Chris Wilson writes:
> Allow some users the discretion to not immediately return on a normal
> signal. Hopefully, they will opt to use TASK_KILLABLE instead.
>
> Signed-off-by: Chris Wilson
> ---
> drivers/gpu/drm/i915/i915_active.c | 6 --
> drivers/gpu/drm/i915/i915_active.h
== Series Details ==
Series: drm/i915/huc: Fix HuC register used in debugfs
URL : https://patchwork.freedesktop.org/series/75231/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8214 -> Patchwork_17128
Summary
---
**FA
== Series Details ==
Series: drm/i915/selftests: Check timeout before flush and cond checks (rev2)
URL : https://patchwork.freedesktop.org/series/75126/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
97b0985bc49a drm/i915/selftests: Check timeout before flush and cond checks
-:1
On Mon, Mar 30, 2020 at 03:23:51PM +0300, Stanislav Lisovskiy wrote:
> In Gen11+ whenever we might exceed DBuf bandwidth we might need to
> recalculate CDCLK which DBuf bandwidth is scaled with.
> Total Dbuf bw used might change based on particular plane needs.
>
> Signed-off-by: Stanislav Lisovsk
On Fri, 2020-03-27 at 14:56 +0200, Ville Syrjälä wrote:
> On Fri, Mar 27, 2020 at 07:27:56AM +, Mun, Gwan-gyeong wrote:
> > On Fri, 2020-03-20 at 13:57 +0200, Laurent Pinchart wrote:
> > > Hi Jani,
> > >
> > > On Fri, Mar 20, 2020 at 01:32:17PM +0200, Jani Nikula wrote:
> > > > On Fri, 20 Mar
Dump out the HDMI Dynamic Range and Mastering (DRM) infoframe in the
normal crtc state dump.
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/display/intel_display.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_display
In order to use a common VSC SDP Colorimetry calculating code on PSR,
it adds a compute routine for PSR VSC SDP.
As PSR routine can not use infoframes.vsc of crtc state, it also adds new
writing of DP SDPs (Secondary Data Packet) for PSR.
PSR routine has its own scenario and timings of writing a VS
In order to readout DP SDPs (Secondary Data Packet: DP HDR Metadata
Infoframe SDP, DP VSC SDP), it refactors handling DP SDPs codes.
It adds new compute routines for DP HDR Metadata Infoframe SDP
and DP VSC SDP.
And new writing routines of DP SDPs (Secondary Data Packet) that uses
computed configs
Compared to implementation of DP and HDMI's encoder->infoframes_enabled,
the lspcon's implementation returns its active state. (we expect enabled
infoframe states of HW.) It leads to pipe state mismatch error
when ddi_get_config is called.
Because the current implementation of lspcon is not ready
When receiving video it is very useful to be able to log DP VSC SDP.
This greatly simplifies debugging.
v2: Minor style fix
v3: Move logging functions to drm core [Jani N]
v5: Rebased
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/drm_dp_helper.c | 174
In order to use a common VSC SDP Colorimetry calculating code on PSR,
it uses a new psr vsc sdp compute routine.
Because PSR routine has its own scenario and timings of writing a VSC SDP,
the current PSR routine needs to have its own drm_dp_vsc_sdp structure
member variable on struct i915_psr.
In
Added state readout for DP HDR Metadata Infoframe SDP.
v9: Rebased
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/display/intel_ddi.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c
b/drivers/gpu/drm/i915/d
It adds code to read the DP SDPs from the video DIP and unpack them into
the crtc state.
It adds routines that read out DP VSC SDP and DP HDR Metadata Infoframe SDP
In order to unpack DP VSC SDP, it adds intel_dp_vsc_sdp_unpack() function.
It follows DP 1.4a spec. [Table 2-116: VSC SDP Header Byte
In order to use computed config for DP SDPs (DP VSC SDP and DP HDR Metadata
Infoframe SDP), it replaces intel_dp_vsc_enable() function and
intel_dp_hdr_metadata_enable() function to intel_dp_set_infoframes()
function.
And it removes unused functions.
Before:
intel_dp_vsc_enable() and intel_dp_hdr
Added state readout for DP VSC SDP and enabled state validation
for DP VSC SDP.
v2: Minor style fix
v3: Replace a structure name to drm_dp_vsc_sdp from intel_dp_vsc_sdp
v4: Use struct drm_device logging macros
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/dis
Dump out the DP VSC SDP in the normal crtc state dump
v3: Replace a structure name to drm_dp_vsc_sdp from intel_dp_vsc_sdp
Use drm core's DP VSC SDP logging function
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/display/intel_display.c | 13 +
Dump out the DP HDR Metadata Infoframe SDP in the normal crtc state dump.
HDMI Dynamic Range and Mastering (DRM) infoframe and DP HDR Metadata
Infoframe SDP use the same member variable in infoframes of crtc state.
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i91
Call intel_dp_set_infoframes(false) function on intel_ddi_post_disable_dp()
to make sure not to send VSC SDP and HDR Metadata Infoframe SDP.
v5: Polish commit message [Uma]
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/display/intel_ddi.c | 2 ++
1 file chang
Call intel_dp_set_infoframes() function on pipe updates to make sure
that we send VSC SDP and HDR Metadata Infoframe SDP (when applicable)
on fastsets.
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/display/intel_ddi.c | 1 +
1 file changed, 1 insertion(+)
dif
It adds an unpack only function for DRM infoframe for dynamic range and
mastering infoframe readout.
It unpacks the information data block contained in the binary buffer into
a structured frame of the HDMI Dynamic Range and Mastering (DRM)
information frame.
In contrast to hdmi_drm_infoframe_unpac
Content Protection property should be updated as per the kernel
internal state. Let's say if Content protection is disabled
by userspace, CP property should be set to UNDESIRED so that
reauthentication will not happen until userspace request it again,
but when kernel disables the HDCP due to any DD
Quoting Dixit, Ashutosh (2020-03-30 16:55:32)
> On Mon, 30 Mar 2020 03:09:20 -0700, Chris Wilson wrote:
> >
> > Quoting Lionel Landwerlin (2020-03-30 10:14:11)
> > > Reading or writing those fields should only happen under
> > > stream->oa_buffer.ptr_lock.
> >
> > Writing, yes. Reading as a pair, s
== Series Details ==
Series: drm/i915: HDCP: fix Ri prime check done during link check (rev2)
URL : https://patchwork.freedesktop.org/series/74152/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e4fabe623ddb drm/i915: HDCP: fix Ri prime check done during link check
-:22: CHECK:P
== Series Details ==
Series: drm/i915/selftests: Check timeout before flush and cond checks (rev2)
URL : https://patchwork.freedesktop.org/series/75126/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8214 -> Patchwork_17129
== Series Details ==
Series: drm/i915: HDCP: fix Ri prime check done during link check (rev2)
URL : https://patchwork.freedesktop.org/series/74152/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8214 -> Patchwork_17130
Summa
On Mon, Mar 30, 2020 at 03:23:53PM +0300, Stanislav Lisovskiy wrote:
> According to BSpec max BW per slice is calculated using formula
> Max BW = CDCLK * 64. Currently when calculating min CDCLK we
> account only per plane requirements, however in order to avoid
> FIFO underruns we need to estimate
Quoting Mika Kuoppala (2020-03-30 17:07:34)
> Chris Wilson writes:
>
> > Allow some users the discretion to not immediately return on a normal
> > signal. Hopefully, they will opt to use TASK_KILLABLE instead.
> >
> > Signed-off-by: Chris Wilson
> > ---
> > drivers/gpu/drm/i915/i915_active.c
On Mon, Mar 30, 2020 at 07:18:57PM +0300, Ville Syrjälä wrote:
> On Mon, Mar 30, 2020 at 03:23:51PM +0300, Stanislav Lisovskiy wrote:
> > In Gen11+ whenever we might exceed DBuf bandwidth we might need to
> > recalculate CDCLK which DBuf bandwidth is scaled with.
> > Total Dbuf bw used might change
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev3)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
Applying: drm/i915: Decouple cdclk calculation from modeset checks
Applying: drm/i915: Force recalculate min_cdclk if planes co
On Mon, 2020-03-30 at 18:22 +0300, Imre Deak wrote:
> The DDI IO power well must not be enabled for a TypeC port in TBT
> mode,
> ensure this during driver loading/system resume.
>
> This gets rid of error messages like
> [drm] *ERROR* power well DDI E TC2 IO state mismatch (refcount
> 1/enabled 0
On Mon, Mar 30, 2020 at 08:07:31PM +0300, Ville Syrjälä wrote:
> On Mon, Mar 30, 2020 at 03:23:53PM +0300, Stanislav Lisovskiy wrote:
> > According to BSpec max BW per slice is calculated using formula
> > Max BW = CDCLK * 64. Currently when calculating min CDCLK we
> > account only per plane requi
== Series Details ==
Series: drm/i915/execlists: Explicitly reset both reg and context runtime (rev2)
URL : https://patchwork.freedesktop.org/series/75127/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8216 -> Patchwork_17132
===
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 (
Add documentation for newly introduced KMS plane and CRTC scaling
filter properties.
changes since v1:
* None
changes since RFC:
* Add separate documentation for plane and CRTC.
Signed-off-by: Pankaj Bharadiya
---
Documentation/gpu/drm-kms.rst | 12
1 file changed, 12 insertions(+)
Introduce per-plane and per-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_create_scaling_filter() and for a
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
Introduce scaler registers and bit fields needed to configure the
scaling filter in prgrammed mode and configure scaling filter
coefficients.
changes since v2:
* Change macro names to CNL_* and use +(set)*8 instead of adding
another trip through _PICK_EVEN (Ville).
changes since v1:
* None
chan
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 v2:
* Use updated functions
* Add ps_ctrl var to contain the full PS_CTRL register value
Chris Wilson writes:
> Use a separate array allocation for the execbuf vma, so that we can
> track their lifetime independently from the copy of the user arguments.
> With luck, this has a secondary benefit of splitting the malloc size to
> within reason and avoid vmalloc. The downside is that we
== Series Details ==
Series: drm/i915/gem: Split eb_vma into its own allocation
URL : https://patchwork.freedesktop.org/series/75241/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8216 -> Patchwork_17133
Summary
---
On Mon, 2020-03-30 at 12:54 +0300, Imre Deak wrote:
> On TypeC ports if a sink deasserts/reasserts its HPD signal,
> generating
> a hotplug interrupt without the sink getting unplugged/replugged from
> the connector, there can be an up to 3 seconds delay until the AUX
> channel gets functional. To
On Mon, 2020-03-30 at 17:50 +0300, Ville Syrjälä wrote:
> On Fri, Mar 27, 2020 at 02:34:11PM -0700, José Roberto de Souza
> wrote:
> > DDI ports have its encoders initialized with INTEL_OUTPUT_DDI type
> > and
> > later eDP ports that have the type changed to INTEL_OUTPUT_EDP.
> > But for all other
With below commit, we have new struct drm_device based WARN* macros,
which include device specific information in the backtrace.
commit dc1a73e50f9c63d4dd928df538082200467dc4b1
Author: Pankaj Bharadiya
Date: Wed Jan 15 09:14:45 2020 +0530
drm/print: introduce new struct drm_device based WA
Hi Pankaj.
On Tue, Mar 31, 2020 at 12:45:24AM +0530, Pankaj Bharadiya wrote:
> With below commit, we have new struct drm_device based WARN* macros,
> which include device specific information in the backtrace.
>
> commit dc1a73e50f9c63d4dd928df538082200467dc4b1
> Author: Pankaj Bharadiya
> Date:
> -Original Message-
> From: Sam Ravnborg
> Sent: 31 March 2020 00:57
> To: Laxminarayan Bharadiya, Pankaj
>
> Cc: jani.nik...@linux.intel.com; dan...@ffwll.ch; intel-
> g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; Maarten Lankhorst
> ; Maxime Ripard ;
> Thomas Zimmerma
On Monday, March 30, 2020 8:38 PM, Pankaj Bharadiya
wrote:
> diff --git a/Documentation/gpu/drm-kms.rst b/Documentation/gpu/drm-kms.rst
> index 906771e03103..b0335e9d887c 100644
> --- a/Documentation/gpu/drm-kms.rst
> +++ b/Documentation/gpu/drm-kms.rst
> @@ -509,6 +509,18 @@ Variable Refresh Pr
Hi,
On Monday, March 30, 2020 8:38 PM, Pankaj Bharadiya
wrote:
> Userspace patch series link: https://github.com/lrusak/xbmc/pull/24
This pull request is against a fork, not the official Kodi repository.
Are there any plans to upstream the change so that users can benefit
from it? Is there a r
With below commit, we have new struct drm_device based WARN* macros,
which include device specific information in the backtrace.
commit dc1a73e50f9c63d4dd928df538082200467dc4b1
Author: Pankaj Bharadiya
Date: Wed Jan 15 09:14:45 2020 +0530
drm/print: introduce new struct drm_device based WA
== Series Details ==
Series: drm/i915: check to see if the FPU is available before using it
URL : https://patchwork.freedesktop.org/series/75249/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
90ca26365082 drm/i915: check to see if the FPU is available before using it
-:34: CHEC
Chris Wilson writes:
> Upon a GPU reset, we copy the default context image over top of the
> guilty image. This will rollback the CTX_TIMESTAMP register to before
> our value of ce->runtime.last. Reset both back to 0 so that we do not
> encounter an underflow on the next schedule out after resume
== Series Details ==
Series: drm/i915: check to see if the FPU is available before using it
URL : https://patchwork.freedesktop.org/series/75249/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8217 -> Patchwork_17134
Summary
On Sat, 2020-03-28 at 11:57 +0200, Imre Deak wrote:
> Hi José,
>
> On Tue, Mar 24, 2020 at 01:14:24PM -0700, José Roberto de Souza
> wrote:
> > TC ports can enter in TCCOLD to save power and is required to
> > request
> > to PCODE to exit this state before use or read to TC registers.
> >
> > For
On Mon, Mar 30, 2020 at 12:15:07PM -0700, Guru Das Srinagesh wrote:
> On Sat, Mar 21, 2020 at 02:47:03PM +0300, Dan Carpenter wrote:
> > This is a giant CC list.
>
> Yes, this is because I received feedback [1] on an earlier patchset
> directing me to add the reviewers of patches to the cover lett
On Sat, 2020-03-28 at 12:26 +0200, Imre Deak wrote:
> On Tue, Mar 24, 2020 at 01:14:29PM -0700, José Roberto de Souza
> wrote:
> > As now the cost to lock and use a TC port is higher due the
> > implementation of the TCCOLD sequences it is worty to hold a
> > reference
> > of the TC port to avoid a
== Series Details ==
Series: series starting with [01/22] Revert "drm/i915/gem: Drop relocation
slowpath"
URL : https://patchwork.freedesktop.org/series/75251/
State : failure
== Summary ==
Applying: Revert "drm/i915/gem: Drop relocation slowpath"
Applying: perf/core: Only copy-to-user after
DDI ports have its encoders initialized with INTEL_OUTPUT_DDI type and
later eDP ports that have the type changed to INTEL_OUTPUT_EDP.
But for all other DDI ports it can drive HDMI or DP depending on what
user connects to the ports.
ehl_get_combo_buf_trans() and tgl_get_combo_buf_trans() was check
Specification was updated with vswing tables for different
configurations.
Also reordering icl_mg_phy_ddi_buf_trans struct to match table order.
BSpec: 21735
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_ddi.c | 93 +++-
1 file changed, 73 insert
EHL has now only one table for all DP rates.
BSpec: 21257
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_ddi.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c
b/drivers/gpu/drm/i915/display/intel_
On Sat, Mar 21, 2020 at 02:47:03PM +0300, Dan Carpenter wrote:
> This is a giant CC list.
Yes, this is because I received feedback [1] on an earlier patchset
directing me to add the reviewers of patches to the cover letter as
well so that they get some context for the patch.
> There was one versi
On Mon, Mar 30, 2020 at 09:26:36PM +0100, Daniel Thompson wrote:
> On Mon, Mar 30, 2020 at 12:15:07PM -0700, Guru Das Srinagesh wrote:
> > On Sat, Mar 21, 2020 at 02:47:03PM +0300, Dan Carpenter wrote:
> > > This is a giant CC list.
> >
> > Yes, this is because I received feedback [1] on an earlie
On Mon, Mar 30, 2020 at 10:51:28AM +0200, Greg KH wrote:
> On Sun, Mar 29, 2020 at 08:30:55PM -0700, Sultan Alsawaf wrote:
> > From: Sultan Alsawaf
> >
> > Hi,
> >
> > This patchset contains fixes for two pesky i915 bugs that exist in 5.4.
>
> Any reason you didn't also cc: the developers invol
CC'ing relevant folks. My apologies.
Sultan
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
From: Sultan Alsawaf
Hi,
This patchset contains fixes for two pesky i915 bugs that exist in 5.4.
The first bug, fixed by
"drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very
high power consumption by i915 hardware due to an old commit that broke the RC6
power state f
From: Chris Wilson
commit 311770173fac27845a3a83e2c16100a54d308f72 upstream.
The major drawback of commit 7e34f4e4aad3 ("drm/i915/gen8+: Add RC6 CTX
corruption WA") is that it disables RC6 while Skylake (and friends) is
active, and we do not consider the GPU idle until all outstanding
requests h
Now that we can peek at GEM->engines[] and obtain a reference to them
using RCU, do so for instances where we can safely iterate the
potentially old copy of the engines. For setting, we can do this when we
know the engine properties are copied over before swapping, so we know
the new engines alread
== Series Details ==
Series: drm/i915: do AUD_FREQ_CNTRL state save on all gen9+ platforms (rev2)
URL : https://patchwork.freedesktop.org/series/74664/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8218 -> Patchwork_17136
S
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c:205: warning: Excess function
parameter 'supported' description in 'intel_uc_fw_init_early'
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c:205: warning: Excess function
parameter 'platform' description in 'intel_uc_fw_init_early'
drivers/gpu/drm/i915/gt/uc/intel
Typo found in word transparent.
Correct the word transparant, replacing the last letter -a- with -e-
(transpar-a-nt to transpar-e-nt).
Signed-off-by: Melissa Wen
---
tests/kms_plane_alpha_blend.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tests/kms_plane_alp
Generalize description of fd since it is not restricted to i915 driver fd
Signed-off-by: Melissa Wen
---
lib/igt_fb.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/igt_fb.c b/lib/igt_fb.c
index 0c4fdc5d..0fb8db12 100644
--- a/lib/igt_fb.c
+++ b/lib/igt_fb.c
@
== Series Details ==
Series: tests/kms_plane_alpha_blend: Correct typo in the name and comments of a
subtest
URL : https://patchwork.freedesktop.org/series/75273/
State : failure
== Summary ==
ERROR! This series introduces new undocumented tests:
kms_plane_alpha_blend@pipe-A-alpha-transparen
== Series Details ==
Series: tests/kms_plane_alpha_blend: Correct typo in the name and comments of a
subtest
URL : https://patchwork.freedesktop.org/series/75273/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> IGTPW_4376
== Series Details ==
Series: lib/igt_fb: change comments with fd description
URL : https://patchwork.freedesktop.org/series/75274/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> IGTPW_4377
Summary
---
**SUCCES
== Series Details ==
Series: drm/i915/icl+: Don't enable DDI IO power on a TypeC port in TBT mode
URL : https://patchwork.freedesktop.org/series/75253/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17137
S
== Series Details ==
Series: In order to readout DP SDPs, refactors the handling of DP SDPs (rev9)
URL : https://patchwork.freedesktop.org/series/72853/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
38f26ed437b1 video/hdmi: Add Unpack only function for DRM infoframe
e58de153b99
Some flips could be missed when FBC + PSR link off is enabled.
Spec states that SKL, BXT, KBL and CNL needs it but probably all
other GEN9 platforms also needs it. As the power drawback would be
mininal even if not needed.
BSpec: 21664
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i9
Render modifications could not trigger PSR exit this WA fixes it.
BSpec: 21664
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/i915_reg.h | 1 +
drivers/gpu/drm/i915/intel_pm.c | 8
2 files changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gp
It was missing GLK and causing some CRC mismatches.
BSpec: 21664
Cc: Ville Syrjälä
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_fbc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c
b/drivers/gpu/
== Series Details ==
Series: In order to readout DP SDPs, refactors the handling of DP SDPs (rev9)
URL : https://patchwork.freedesktop.org/series/72853/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17138
process_csb: :00:02.0 bcs0: cs-irq head=4, tail=5
process_csb: :00:02.0 bcs0: csb[5]: status=0x8002:0x6020
trace_ports: :00:02.0 bcs0: preempted { ff84:45154! prio 2 }
trace_ports: :00:02.0 bcs0: promote { ff84:45155* prio 2 }
trace_ports: :00:02.0 bcs0: submit
process_csb: :00:02.0 bcs0: cs-irq head=4, tail=5
process_csb: :00:02.0 bcs0: csb[5]: status=0x8002:0x6020
trace_ports: :00:02.0 bcs0: preempted { ff84:45154! prio 2 }
trace_ports: :00:02.0 bcs0: promote { ff84:45155* prio 2 }
trace_ports: :00:02.0 bcs0: submit
== Series Details ==
Series: Introduce drm scaling filter property (rev4)
URL : https://patchwork.freedesktop.org/series/73883/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
96f667695dae drm: Introduce plane and CRTC scaling filter properties
8b03194b0630 drm/drm-kms.rst: Add p
== Series Details ==
Series: drm/i915/hdcp: Update CP as per the kernel internal state (rev3)
URL : https://patchwork.freedesktop.org/series/72251/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17139
Summa
On Mon, Mar 30, 2020 at 09:31:44AM +0530, Manna, Animesh wrote:
>
> On 28-03-2020 00:15, Manasi Navare wrote:
> >On Tue, Mar 24, 2020 at 10:41:11AM +0530, Animesh Manna wrote:
> >>DP_COMP_CTL and DP_COMP_PAT register used to program DP
> >>compliance pattern.
> >>
> >>v1: Initial patch.
> >>v2: us
@Jani @Ville, this is the one we had discussed on IRC, could you
take a look at this patch?
Manasi
On Tue, Mar 24, 2020 at 06:22:01PM -0700, Manasi Navare wrote:
> From: Aditya Swarup
>
> This function sets the VRR property for connector based
> on the platform support, EDID monitor range and D
== Series Details ==
Series: Introduce drm scaling filter property (rev4)
URL : https://patchwork.freedesktop.org/series/73883/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17140
Summary
---
**SUCC
If we receive the error interrupt before the CS interrupt, we may find
ourselves without an active request to reset, skipping the GPU reset.
All because the attempt to reset was too early.
GEM_BUG_ON(EXECLIST_STATUS_HI() != upper_32_bits(ce->lrc_desc)) ?
Signed-off-by: Chris Wilson
---
drivers/
== Series Details ==
Series: drm/todo: Add todo to make i915 WARN* calls drm device specific (rev2)
URL : https://patchwork.freedesktop.org/series/75265/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e3dc4dcfa7f1 drm/todo: Add todo to make i915 WARN* calls drm device specific
-
== Series Details ==
Series: drm/todo: Add todo to make i915 WARN* calls drm device specific (rev2)
URL : https://patchwork.freedesktop.org/series/75265/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17141
== Series Details ==
Series: series starting with [v2,1/3] drm/i915/dp: Return the right vswing
tables
URL : https://patchwork.freedesktop.org/series/75268/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17142
=
On Mon, 30 Mar 2020 09:38:23 -0700, Chris Wilson wrote:
>
> Quoting Dixit, Ashutosh (2020-03-30 16:55:32)
> > On Mon, 30 Mar 2020 03:09:20 -0700, Chris Wilson wrote:
> > >
> > > Quoting Lionel Landwerlin (2020-03-30 10:14:11)
> > > > Reading or writing those fields should only happen under
> > > >
== Series Details ==
Series: drm/i915/gem: Utilize rcu iteration of context engines
URL : https://patchwork.freedesktop.org/series/75270/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17143
Summary
---
== Series Details ==
Series: drm/i915/uc: Cleanup kerneldoc warnings
URL : https://patchwork.freedesktop.org/series/75271/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17144
Summary
---
**FAILURE**
== Series Details ==
Series: series starting with [1/2] drm/i915: Add a retry counter for hotplug
detect retries
URL : https://patchwork.freedesktop.org/series/75224/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8213_full -> Patchwork_17125_full
=
== Series Details ==
Series: series starting with [1/3] drm/i915/psr: Implement WA 1110
URL : https://patchwork.freedesktop.org/series/75277/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17145
Summary
---
== Series Details ==
Series: drm/i915/execlists: Double check breadcrumb before crying foul (rev2)
URL : https://patchwork.freedesktop.org/series/75278/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
22f7a545c2a2 drm/i915/execlists: Double check breadcrumb before crying foul
-:1
== Series Details ==
Series: drm/i915/execlists: Double check breadcrumb before crying foul (rev2)
URL : https://patchwork.freedesktop.org/series/75278/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17146
== Series Details ==
Series: drm/i915/huc: Add more errors for I915_PARAM_HUC_STATUS
URL : https://patchwork.freedesktop.org/series/75230/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8213_full -> Patchwork_17127_full
Summ
== Series Details ==
Series: drm/i915/execlists: Peek at the next submission for error interrupts
URL : https://patchwork.freedesktop.org/series/75279/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8219 -> Patchwork_17147
S
== Series Details ==
Series: drm/i915: HDCP: fix Ri prime check done during link check (rev2)
URL : https://patchwork.freedesktop.org/series/74152/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8214_full -> Patchwork_17130_full
=
It is wrong to block the user thread in the next poll when OA data is
already available which could not fit in the user buffer provided in
the previous read. In several cases the exact user buffer size is not
known. Blocking user space in poll can lead to data loss when the
buffer size used is smal
101 - 200 of 204 matches
Mail list logo
