== Series Details ==
Series: drm/i915/display: Force full modeset for eDP
URL : https://patchwork.freedesktop.org/series/129566/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/display: Force full modeset for eDP
URL : https://patchwork.freedesktop.org/series/129566/
State : warning
== Summary ==
Error: dim checkpatch failed
d687461f727e Revert "drm/i915/display: Skip C10 state verification in case of
fastset"
8ef79285b9d3
Force full modeset for eDP when booting up. GOP programs
PLL parameters and hence, we would be able to use fastset
for eDP. However, with fastset we are not setting PLL values
from the driver and rely that GOP and driver PLL values match.
We have discovered that with some of the panels this is not
This reverts commit a1d91c6e989d0e66b89aa911f2cd459d7bdebbe5.
Signed-off-by: Mika Kahola
---
drivers/gpu/drm/i915/display/intel_cx0_phy.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_cx0_phy.c
b/drivers/gpu/drm/i915/display/intel_cx0_phy.c
index
It was discovered that we couldn't skip the fastset on state
verification and hence this workaround is proposed.
First, the patch that skips state verifcation in case of
fastset is reverted. The second patch proposes the following
workaround by forcing full modeset for eDP when booting up.
GOP
== Series Details ==
Series: Enable ccs compressed framebuffers on Xe2 (rev6)
URL : https://patchwork.freedesktop.org/series/129471/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14229 -> Patchwork_129471v6
Summary
---
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree
URL : https://patchwork.freedesktop.org/series/129561/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14229 -> Patchwork_129561v1
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree
URL : https://patchwork.freedesktop.org/series/129561/
State : warning
== Summary ==
Error: dim checkpatch failed
89f56ec93511 linux-next: build failure after merge of the drm-misc tree
-:12:
== Series Details ==
Series: Cursor Fault Fixes (rev5)
URL : https://patchwork.freedesktop.org/series/129517/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14229 -> Patchwork_129517v5
Summary
---
**FAILURE**
== Series Details ==
Series: Cursor Fault Fixes (rev5)
URL : https://patchwork.freedesktop.org/series/129517/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./arch/x86/include/asm/bitops.h:116:1: warning:
== Series Details ==
Series: Cursor Fault Fixes (rev5)
URL : https://patchwork.freedesktop.org/series/129517/
State : warning
== Summary ==
Error: dim checkpatch failed
e814f2e4a701 drm: Add drm_vblank_work_flush_all().
-:33: WARNING:WAITQUEUE_ACTIVE: waitqueue_active without comment
#33:
Hi all,
After merging the drm-misc tree, today's linux-next build (i386 defconfig)
failed like this:
In function 'i915_ttm_placement_from_obj',
inlined from 'i915_ttm_get_pages' at
drivers/gpu/drm/i915/gem/i915_gem_ttm.c:847:2:
drivers/gpu/drm/i915/gem/i915_gem_ttm.c:165:18: error:
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree
URL : https://patchwork.freedesktop.org/series/129558/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/129558/revisions/1/mbox/ not
applied
Applying:
Hi all,
After merging the drm-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:
Caused by commit
a78a8da51b36 ("drm/ttm: replace busy placement with flags v6")
interacting with commit
dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
(and maybe
Hi all,
On Tue, 6 Feb 2024 11:59:56 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
>
> drivers/gpu/drm/bridge/samsung-dsim.c
>
> between commit:
>
> ff3d5d04db07 ("drm: bridge: samsung-dsim: Don't use FORCE_STOP_STATE")
>
> from Linus'
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/bridge/samsung-dsim.c
between commit:
ff3d5d04db07 ("drm: bridge: samsung-dsim: Don't use FORCE_STOP_STATE")
from Linus' tree and commit:
b2fe2292624a ("drm: bridge: samsung-dsim: enter display
== Series Details ==
Series: drm/i915: (stolen) memory region related fixes (rev12)
URL : https://patchwork.freedesktop.org/series/127721/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14227 -> Patchwork_127721v12
Summary
On 2/2/2024 12:37 AM, Suraj Kandpal wrote:
Enable HDCP for Xe by defining functions which take care of
interaction of HDCP as a client with the GSC CS interface.
Signed-off-by: Suraj Kandpal
---
drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 188 ++-
1 file changed, 184
On Tue, Jan 23, 2024 at 12:28:42PM +0200, Imre Deak wrote:
> +static int check_inherited_tunnel_state(struct intel_atomic_state *state,
> + struct intel_dp *intel_dp,
> + const struct
> intel_digital_connector_state
== Series Details ==
Series: drm/i915: (stolen) memory region related fixes (rev12)
URL : https://patchwork.freedesktop.org/series/127721/
State : warning
== Summary ==
Error: dim checkpatch failed
f812c80bfb4f drm/i915: Use struct resource for memory region IO as well
-:388:
== Series Details ==
Series: drm/i915: (stolen) memory region related fixes (rev12)
URL : https://patchwork.freedesktop.org/series/127721/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Mon, Feb 05, 2024 at 07:15:17PM +0200, Imre Deak wrote:
> On Mon, Feb 05, 2024 at 06:13:30PM +0200, Ville Syrjälä wrote:
> > On Wed, Jan 31, 2024 at 08:49:16PM +0200, Imre Deak wrote:
> > > On Wed, Jan 31, 2024 at 06:09:04PM +0200, Ville Syrjälä wrote:
> > > > On Tue, Jan 23, 2024 at 12:28:33PM
== Series Details ==
Series: drm/i915/dsc: Fix the macro that calculates DSCC_/DSCA_ PPS reg address
(rev2)
URL : https://patchwork.freedesktop.org/series/129486/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14227 -> Patchwork_129486v2
== Series Details ==
Series: drm/i915/dsc: Fix the macro that calculates DSCC_/DSCA_ PPS reg address
(rev2)
URL : https://patchwork.freedesktop.org/series/129486/
State : warning
== Summary ==
Error: dim checkpatch failed
6a38025388cc drm/i915/dsc: Fix the macro that calculates DSCC_/DSCA_
== Series Details ==
Series: Enable ccs compressed framebuffers on Xe2 (rev5)
URL : https://patchwork.freedesktop.org/series/129471/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14227 -> Patchwork_129471v5
Summary
---
Commit bd077259d0a9 ("drm/i915/vdsc: Add function to read any PPS register")
defines
a new macro to calculate the DSC PPS register addresses with PPS number as an
input. This macro correctly calculates the addresses till PPS 11 since the
addresses increment by 4. So in that case the following
Hi Stan,
I discussed with Ville a little bit on IRC and wanted to reflect some
conversation here as review so that it could be accommodated in your
next revision for bigjoiner changes.
For bigjoiner cases to work correctly, when bigjoiner steals a CRTC
for using it as slave CRTC, the assumption
On Mon, Feb 05, 2024 at 06:11:00PM +0200, Ville Syrjälä wrote:
> On Tue, Jan 23, 2024 at 12:28:43PM +0200, Imre Deak wrote:
> > Add the atomic state during a modeset required to enable the DP tunnel
> > BW allocation mode on links where such a tunnel was detected.
> >
> > Signed-off-by: Imre Deak
Hi Jani,
Yea I think I made that change after checkpatch but didnt do commit
--amend, let me address that and send the patch for review.
Regards
Manasi
On Mon, Feb 5, 2024 at 4:03 AM Jani Nikula wrote:
>
> On Fri, 02 Feb 2024, Manasi Navare wrote:
> > Commit bd077259d0a9 ("drm/i915/vdsc: Add
> Subject: Re: [PATCH 2/2] drm/i915/lnl: Program PKGC_LATENCY register
>
> On Mon, 05 Feb 2024, Suraj Kandpal wrote:
> > Program the PKGC_LATENCY register with the highest latency from level
> > 1 and above LP registers else program with all 1's.
> > This is used to improve package C residency
On Mon, Feb 05, 2024 at 03:26:31PM +0200, Imre Deak wrote:
> The DSC HW state of DP connectors is read out during driver loading and
> system resume in intel_modeset_update_connector_atomic_state(). This
> function is called for all connectors though and so the state of DSI
> connectors will also
On Mon, Feb 05, 2024 at 06:13:30PM +0200, Ville Syrjälä wrote:
> On Wed, Jan 31, 2024 at 08:49:16PM +0200, Imre Deak wrote:
> > On Wed, Jan 31, 2024 at 06:09:04PM +0200, Ville Syrjälä wrote:
> > > On Tue, Jan 23, 2024 at 12:28:33PM +0200, Imre Deak wrote:
> > > > +static void
> -Original Message-
> From: Jani Nikula
> Sent: Monday, February 5, 2024 6:52 PM
> To: Borah, Chaitanya Kumar ; intel-
> g...@lists.freedesktop.org
> Cc: Shankar, Uma ; Borah, Chaitanya Kumar
> ; maarten.lankho...@linux.intel.com;
> ville.syrj...@linux.intel.com
> Subject: Re: [PATCH
On Wed, Jan 31, 2024 at 08:49:16PM +0200, Imre Deak wrote:
> On Wed, Jan 31, 2024 at 06:09:04PM +0200, Ville Syrjälä wrote:
> > On Tue, Jan 23, 2024 at 12:28:33PM +0200, Imre Deak wrote:
> > > +static void untrack_tunnel_ref(struct drm_dp_tunnel *tunnel,
> > > +struct
On Tue, Jan 23, 2024 at 12:28:43PM +0200, Imre Deak wrote:
> Add the atomic state during a modeset required to enable the DP tunnel
> BW allocation mode on links where such a tunnel was detected.
>
> Signed-off-by: Imre Deak
> ---
> drivers/gpu/drm/i915/display/intel_atomic.c | 8
>
On Sat, Feb 03, 2024 at 10:25:18AM -0300, Gustavo Sousa wrote:
> Quoting Ville Syrjälä (2024-02-02 16:58:37-03:00)
> >On Fri, Feb 02, 2024 at 10:12:08AM -0300, Gustavo Sousa wrote:
> >> Looks like the name and description of intel_cdclk_needs_modeset()
> >> became inacurate as of commit
== Series Details ==
Series: drm/i915/dp: Fix connector DSC HW state readout
URL : https://patchwork.freedesktop.org/series/129540/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14221 -> Patchwork_129540v1
Summary
---
Hi,
> -Original Message-
> From: Intel-xe On Behalf Of Lucas De
> Marchi
> Sent: Monday, February 5, 2024 4:17 PM
> To: Jani Nikula
> Cc: Ville Syrjala ;
> intel-gfx@lists.freedesktop.org;
> Hellstrom, Thomas ; Oded Gabbay
> ; intel...@lists.freedesktop.org; Paz Zcharya
>
> Subject:
On Mon, Feb 05, 2024 at 01:38:45PM +0200, Jani Nikula wrote:
On Sat, 03 Feb 2024, Ville Syrjala wrote:
drm/i915: Simplify intel_initial_plane_config() calling convention
drm/i915: Tweak BIOS fb reuse check
drm/i915: Try to relocate the BIOS fb to the start of ggtt
== Series Details ==
Series: Enable ccs compressed framebuffers on Xe2 (rev4)
URL : https://patchwork.freedesktop.org/series/129471/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14221 -> Patchwork_129471v4
Summary
---
On Fri, 2024-02-02 at 13:58 +, Manna, Animesh wrote:
>
>
> > -Original Message-
> > From: Hogander, Jouni
> > Sent: Friday, January 19, 2024 3:40 PM
> > To: intel-gfx@lists.freedesktop.org
> > Cc: Manna, Animesh ; Hogander, Jouni
> >
> > Subject: [PATCH v3 11/21] drm/i915/psr:
On Fri, Feb 02, 2024 at 10:48:32AM -0700, Drew Davenport wrote:
> [...]
> > diff --git a/drivers/gpu/drm/i915/display/intel_modeset_setup.c
> > b/drivers/gpu/drm/i915/display/intel_modeset_setup.c
> > index b8f43efb0ab5a..94eece7f63be3 100644
> > ---
On Thu, Feb 1, 2024 at 1:06 AM David Gow wrote:
>
> If KUnit is built as a module, and it's unloaded, the kunit_bus is not
> unregistered. This causes an error if it's then re-loaded later, as we
> try to re-register the bus.
>
> Unregister the bus and root_device on shutdown, if it looks valid.
On Mon, Jan 29, 2024 at 08:49:35AM -0600, Lucas De Marchi wrote:
> On Wed, Jan 24, 2024 at 07:27:58AM -0800, Yury Norov wrote:
> > On Wed, Jan 24, 2024 at 08:03:53AM -0600, Lucas De Marchi wrote:
> > > On Wed, Jan 24, 2024 at 09:58:26AM +0200, Jani Nikula wrote:
> > > > On Tue, 23 Jan 2024, Lucas
The DSC HW state of DP connectors is read out during driver loading and
system resume in intel_modeset_update_connector_atomic_state(). This
function is called for all connectors though and so the state of DSI
connectors will also get updated incorrectly, triggering a WARN there
wrt. the DSC
On Mon, 05 Feb 2024, Chaitanya Kumar Borah
wrote:
> This series is based on top of [1] floated by Maarten.
> To fix regressions seen in CI, following changes were made on top of the
> original series.
You've sent at least three versions of this in the past 24 hours, with
no indication of the
== Series Details ==
Series: Cursor Fault Fixes (rev4)
URL : https://patchwork.freedesktop.org/series/129517/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14220 -> Patchwork_129517v4
Summary
---
**FAILURE**
== Series Details ==
Series: Cursor Fault Fixes (rev4)
URL : https://patchwork.freedesktop.org/series/129517/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./arch/x86/include/asm/bitops.h:116:1: warning:
== Series Details ==
Series: Cursor Fault Fixes (rev4)
URL : https://patchwork.freedesktop.org/series/129517/
State : warning
== Summary ==
Error: dim checkpatch failed
933ccc26d131 drm: Add drm_vblank_work_flush_all().
-:33: WARNING:WAITQUEUE_ACTIVE: waitqueue_active without comment
#33:
On Fri, 02 Feb 2024, Manasi Navare wrote:
> Commit bd077259d0a9 ("drm/i915/vdsc: Add function to read any PPS register")
> defines
> a new macro to calculate the DSC PPS register addresses with PPS number as an
> input. This macro correctly calculates the addresses till PPS 11 since the
>
On Sat, 03 Feb 2024, Ville Syrjala wrote:
> drm/i915: Simplify intel_initial_plane_config() calling convention
> drm/i915: Tweak BIOS fb reuse check
> drm/i915: Try to relocate the BIOS fb to the start of ggtt
> drivers/gpu/drm/xe/display/xe_plane_initial.c | 67 +++--
Lucas, Thomas,
== Series Details ==
Series: Enable ccs compressed framebuffers on Xe2 (rev3)
URL : https://patchwork.freedesktop.org/series/129471/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14218 -> Patchwork_129471v3
Summary
---
On Mon, 05 Feb 2024, Suraj Kandpal wrote:
> Program the PKGC_LATENCY register with the highest latency from
> level 1 and above LP registers else program with all 1's.
> This is used to improve package C residency by sending the highest
> latency tolerance requirement (LTR) when the planes are
After we move the cursor fb unpin to a vblank work, we encounter
race conditions between the vblank work and the atomic clean up
work leading to dump stacks[1]. Let's serialize the clean up
to avoid theses races.
[1]
[ 278.748767] Workqueue: events_highpri intel_atomic_cleanup_work [i915]
The plane destroy hook can be called asynchronously even when vblank
worker responsible for unpinning the cursor fb is scheduled. Since
the vblank worker destroys the plane state, do not destroy the plane
state if it is scheduled.
Signed-off-by: Chaitanya Kumar Borah
---
Now that cursor plane fb unpinning can be deferred to vblank work
access the fb object only when vblank unpin worker is not scheduled.
Signed-off-by: Chaitanya Kumar Borah
---
drivers/gpu/drm/i915/display/intel_atomic_plane.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
From: Ville Syrjälä
The cursor hardware only does sync updates, and thus the hardware
will be scanning out from the old fb until the next start of vblank.
So in order to make the legacy cursor fastpath actually safe we
should not unpin the old fb until we're sure the hardware has
ceased
From: Maarten Lankhorst
In case of legacy cursor update, the cursor VMA needs to be unpinned
only after vblank. This exceeds the lifetime of the whole atomic commit.
Any trick I attempted to keep the atomic commit alive didn't work, as
drm_atomic_helper_setup_commit() force throttles on any old
This series is based on top of [1] floated by Maarten.
To fix regressions seen in CI, following changes were made on top of the
original series.
1. add a check in the plane state destroy hook to not move forward if the
vblank worker is scheduled.
2. add checks before accessing frame buffer
From: Maarten Lankhorst
In some cases we want to flush all vblank work, right before vblank_off
for example. Add a simple function to make this possible.
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/drm_vblank_work.c | 22 ++
include/drm/drm_vblank_work.h | 2
== Series Details ==
Series: Program Deep PKG_C_LATENCY register (rev2)
URL : https://patchwork.freedesktop.org/series/129407/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14218 -> Patchwork_129407v2
Summary
---
On 2.2.2024 22.51, Souza, Jose wrote:
On Thu, 2024-01-25 at 08:07 -0800, José Roberto de Souza wrote:
On Thu, 2024-01-25 at 17:56 +0200, Juha-Pekka Heikkila wrote:
On 25.1.2024 17.28, Souza, Jose wrote:
On Thu, 2024-01-25 at 17:25 +0200, Juha-Pekka Heikkila wrote:
AuxCCS framebuffers don't
== Series Details ==
Series: Program Deep PKG_C_LATENCY register (rev2)
URL : https://patchwork.freedesktop.org/series/129407/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/mst: enable MST mode for 128b/132b single-stream sideband
(rev2)
URL : https://patchwork.freedesktop.org/series/129468/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14218 -> Patchwork_129468v2
== Series Details ==
Series: Cursor Fault Fixes (rev3)
URL : https://patchwork.freedesktop.org/series/129517/
State : failure
== Summary ==
Error: make failed
CALLscripts/checksyscalls.sh
DESCEND objtool
INSTALL libsubcmd_headers
CC [M]
== Series Details ==
Series: drm/i915/mst: enable MST mode for 128b/132b single-stream sideband
(rev2)
URL : https://patchwork.freedesktop.org/series/129468/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/mst: enable MST mode for 128b/132b single-stream sideband
(rev2)
URL : https://patchwork.freedesktop.org/series/129468/
State : warning
== Summary ==
Error: dim checkpatch failed
c3f6f0c75507 drm/mst: read sideband messaging cap
-:124: WARNING:LONG_LINE:
Program the PKGC_LATENCY register with the highest latency from
level 1 and above LP registers else program with all 1's.
This is used to improve package C residency by sending the highest
latency tolerance requirement (LTR) when the planes are done with the
frame until the next frame programming
70 matches
Mail list logo
