== Series Details ==
Series: drm/i915/display: Force full modeset for eDP
URL : https://patchwork.freedesktop.org/series/129566/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14229 -> Patchwork_129566v1
Summary
---
*
== Series Details ==
Series: Cursor Fault Fixes (rev5)
URL : https://patchwork.freedesktop.org/series/129517/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14229 -> Patchwork_129517v5
Summary
---
**SUCCESS**
No re
The series depicts a working skeleton of the fallback sequence in case
on DP link training failure.
The fallback is currently implemented for DP2.0 only, on similar basis
DP1.4 fallback will come up in the same patch series.
A hotplug event was trigerred in the existing fallback sequence. This
has
Fallback mandates on DP link training failure. This patch just covers
the DP2.0 fallback sequence.
TODO: Need to implement the DP1.4 fallback.
Signed-off-by: Arun R Murthy
---
drivers/gpu/drm/i915/display/intel_dp.c | 92 ++---
1 file changed, 82 insertions(+), 10 deletions(
On link training failure fallback sequence a hotpplu event was sent to
the user, but this is not requried as we are not changing the mode and
instead only changing the link rate and lane count. User has no
dependency with these parameters.
Signed-off-by: Arun R Murthy
---
drivers/gpu/drm/i915/di
The link rate and lane count are now part of the intel_crtc_state
structure. These two parameters are nothing to do with the crtc and are
more confined to DP.
TODO: Need to still seperate out the use of link rate and port clock
which is in intel_dp and intel_crtc_state structure.
Signed-off-by: A
On link training failure retry link training with a lesser link
rate/lane count as specified in the DP spec.
Signed-off-by: Arun R Murthy
---
drivers/gpu/drm/i915/display/intel_ddi.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_
On Tue, 06 Feb 2024, Arun R Murthy wrote:
> On link training failure fallback sequence a hotpplu event was sent to
> the user, but this is not requried as we are not changing the mode and
> instead only changing the link rate and lane count. User has no
> dependency with these parameters.
>
> Sign
On Tue, 06 Feb 2024, Stephen Rothwell wrote:
> 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
On Tue, Feb 06, 2024 at 12:47:22AM +0200, Ville Syrjälä wrote:
> 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,
> > +
== Series Details ==
Series: DP link training failure fallback
URL : https://patchwork.freedesktop.org/series/129572/
State : warning
== Summary ==
Error: dim checkpatch failed
7517157fd57d drm/i915/display/dp: Add DP fallback on LT
-:79: WARNING:UNNECESSARY_ELSE: else is not generally useful
== Series Details ==
Series: DP link training failure fallback
URL : https://patchwork.freedesktop.org/series/129572/
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: w
Hi
On Tue, 2024-02-06 at 12:28 +1100, Stephen Rothwell wrote:
> 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 comm
== Series Details ==
Series: DP link training failure fallback
URL : https://patchwork.freedesktop.org/series/129572/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14231 -> Patchwork_129572v1
Summary
---
**FAILURE**
Hi, Christian,
On Fri, 2024-01-26 at 15:09 +0100, Christian König wrote:
> Previously we would never try to move a BO into the preferred
> placements
> when it ever landed in a busy placement since those were considered
> compatible.
>
> Rework the whole handling and finally unify the idle and bu
Am 06.02.24 um 13:53 schrieb Thomas Hellström:
Hi, Christian,
On Fri, 2024-01-26 at 15:09 +0100, Christian König wrote:
Previously we would never try to move a BO into the preferred
placements
when it ever landed in a busy placement since those were considered
compatible.
Rework the whole hand
> -Original Message-
> From: Nikula, Jani
> Sent: Tuesday, February 6, 2024 5:10 PM
> To: Murthy, Arun R ; intel-gfx@lists.freedesktop.org
> Cc: Deak, Imre ; Syrjala, Ville
> ;
> Shankar, Uma ; Murthy, Arun R
>
> Subject: Re: [RFC 2/4] drm/i915/display/dp: Dont send hotplug event on LT
> -Original Message-
> From: Hogander, Jouni
> Sent: Tuesday, January 30, 2024 4:41 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Murthy, Arun R ; Hogander, Jouni
> ; Nikula, Jani
> Subject: [PATCH v3 1/4] drm/i915/alpm: Add ALPM register definitions
>
> Add ALPM register definitions f
> -Original Message-
> From: Hogander, Jouni
> Sent: Tuesday, January 30, 2024 4:41 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Murthy, Arun R ; Hogander, Jouni
>
> Subject: [PATCH v3 2/4] drm/i915/psr: Add alpm_parameters struct
>
> Add new alpm_parameters struct into intel_psr for a
> -Original Message-
> From: Hogander, Jouni
> Sent: Tuesday, January 30, 2024 4:41 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Murthy, Arun R ; Hogander, Jouni
>
> Subject: [PATCH v3 3/4] drm/i915/alpm: Calculate ALPM Entry check
>
> ALPM Entry Check represents the number of lines n
> -Original Message-
> From: Hogander, Jouni
> Sent: Tuesday, January 30, 2024 4:42 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Murthy, Arun R ; Hogander, Jouni
>
> Subject: [PATCH v3 4/4] drm/i915/alpm: Alpm aux wake configuration for lnl
>
> Lunarlake has some configurations in ALP
Accessing the display HW from the connector get_modes hooks should be
prevented during driver init/shutdown similarly to how this is done in
the encoder detect hooks and modeset as explained in the following
commits:
drm/i915: Prevent modesets during driver init/shutdown
drm/i915: Disable hotplug
Prevent accessing the HW from the SDVO/TV get_modes connector hook.
Returning 0 from the hook will make the caller -
drm_helper_probe_single_connector_modes() - keep the previously detected
mode list of the connector.
Signed-off-by: Imre Deak
---
drivers/gpu/drm/i915/display/intel_sdvo.c | 4 +++
Prevent accessing the HW from the get_modes hooks of connectors deriving
the mode list from the display's EDID. drm_edid_connector_add_modes()
will return the mode list based on the EDID which was cached during a
previous detection/get_modes call.
Closes: https://gitlab.freedesktop.org/drm/intel/-
> Subject: Re: [PATCH 2/3] drm/xe/hdcp: Enable HDCP for XE
>
>
>
> 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
On 01/02/2024 18:25, Souza, Jose wrote:
On Wed, 2024-01-24 at 08:55 +, Tvrtko Ursulin wrote:
On 24/01/2024 08:19, Joonas Lahtinen wrote:
Add reporting of the GuC submissio/VF interface version via GETPARAM
properties. Mesa intends to use this information to check for old
firmware versions
This patch series enables HDCP on XE.
Mainly includes rewriting functions that were responsible for
sending hdcp messages via gsc cs.
Signed-off-by: Suraj Kandpal
Suraj Kandpal (3):
drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file
drm/xe/hdcp: Enable HDCP for XE
drm/xe/
Move intel_hdcp_gsc_message definition into intel_hdcp_gsc_message.c
so that intel_hdcp_gsc_message can be redefined for xe as needed.
Signed-off-by: Suraj Kandpal
---
drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 6 ++
drivers/gpu/drm/i915/display/intel_hdcp_gsc.h | 7 +--
2 files cha
Enable HDCP for Xe by defining functions which take care of
interaction of HDCP as a client with the GSC CS interface.
--v2
-add kfree at appropriate place [Daniele]
-forward declare drm_i915_private [Daniele]
-remove useless define [Daniele]
-move host session logic to xe_gsc_submit.c [Daniele]
-
Add intel_hdcp_gsc_message to Makefile and add corresponding
changes to xe_hdcp_gsc.c to make it build.
Signed-off-by: Suraj Kandpal
---
drivers/gpu/drm/xe/Makefile | 1 +
drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 19 ++-
2 files changed, 19 insertions(+), 1 deleti
On 2/6/2024 8:24 AM, Kandpal, Suraj wrote:
Subject: Re: [PATCH 2/3] drm/xe/hdcp: Enable HDCP for XE
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 Kandpa
== Series Details ==
Series: drm/i915: Prevent HW access during init from connector hooks
URL : https://patchwork.freedesktop.org/series/129584/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14234 -> Patchwork_129584v1
Summ
== Series Details ==
Series: XE HDCP Enablement (rev2)
URL : https://patchwork.freedesktop.org/series/129456/
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: XE HDCP Enablement (rev2)
URL : https://patchwork.freedesktop.org/series/129456/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14234 -> Patchwork_129456v2
Summary
---
**FAILURE**
Serio
On Tue, Feb 06, 2024 at 01:39:28PM +0100, Thomas Hellström wrote:
Hi
On Tue, 2024-02-06 at 12:28 +1100, Stephen Rothwell wrote:
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 p
> -Original Message-
> From: dri-devel On Behalf Of Imre
> Deak
> Sent: Friday, January 26, 2024 6:58 PM
> To: Ville Syrjälä
> Cc: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org
> Subject: Re: [PATCH 01/19] drm/dp: Add drm_dp_max_dprx_data_rate()
>
> On Fri, Jan 26,
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 04/19] drm/i915/dp: Use drm_dp_max_dprx_data_rate()
>
> Instead of intel_dp_max_data_r
> -Original Message-
> From: dri-devel On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 05/19] drm/i915/dp: Factor out intel_dp_config_required_rate()
>
> Factor out intel_dp
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 06/19] drm/i915/dp: Export
> intel_dp_max_common_rate/lane_count()
>
> Export intel_dp
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 07/19] drm/i915/dp: Factor out intel_dp_update_sink_caps()
>
> Factor out a function u
> -Original Message-
> From: dri-devel On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 08/19] drm/i915/dp: Factor out intel_dp_read_dprx_caps()
>
> Factor out a function to
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 09/19] drm/i915/dp: Add intel_dp_max_link_data_rate()
>
> Add intel_dp_max_link_data_r
On 2/6/2024 08:33, Tvrtko Ursulin wrote:
On 01/02/2024 18:25, Souza, Jose wrote:
On Wed, 2024-01-24 at 08:55 +, Tvrtko Ursulin wrote:
On 24/01/2024 08:19, Joonas Lahtinen wrote:
Add reporting of the GuC submissio/VF interface version via GETPARAM
properties. Mesa intends to use this inform
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 13/19] drm/i915/dp: Account for tunnel BW limit in
> intel_dp_max_link_data_rate()
>
>
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 14/19] drm/i915/dp: Compute DP tunel BW during encoder state
> computation
>
> Compute
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 15/19] drm/i915/dp: Allocate/free DP tunnel BW in the encoder
> enable/disable hooks
>
> -Original Message-
> From: Intel-gfx On Behalf Of Imre
> Deak
> Sent: Tuesday, January 23, 2024 3:59 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org
> Subject: [PATCH 17/19] drm/i915/dp: Call intel_dp_sync_state() always for DDI
> DP encoders
>
> A foll
On Tue, 2024-02-06 at 12:42 -0800, John Harrison wrote:
> On 2/6/2024 08:33, Tvrtko Ursulin wrote:
> > On 01/02/2024 18:25, Souza, Jose wrote:
> > > On Wed, 2024-01-24 at 08:55 +, Tvrtko Ursulin wrote:
> > > > On 24/01/2024 08:19, Joonas Lahtinen wrote:
> > > > > Add reporting of the GuC submis
On Tue, 2024-02-06 at 16:17 +0530, Arun R Murthy wrote:
> Fallback mandates on DP link training failure. This patch just covers
> the DP2.0 fallback sequence.
>
> TODO: Need to implement the DP1.4 fallback.
>
> Signed-off-by: Arun R Murthy
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 92 ++
On Tue, Jan 23, 2024 at 12:28:42PM +0200, Imre Deak wrote:
> Add support to enable the DP tunnel BW allocation mode. Follow-up
> patches will call the required helpers added here to prepare for a
> modeset on a link with DP tunnels, the last change in the patchset
> actually enabling BWA.
>
> With
On Tue, Jan 23, 2024 at 12:28:45PM +0200, Imre Deak wrote:
> Compute the BW required through a DP tunnel on links with such tunnels
> detected and add the corresponding atomic state during a modeset.
>
> Signed-off-by: Imre Deak
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 16 ++
On Mon, Feb 05, 2024 at 08:16:35AM -0600, Lucas De Marchi wrote:
> 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
> >> d
From: Ville Syrjälä
Extract the cdclk divider calculation into a helper. We'll have
more users of this soon. We can now also get rid of the intermediate
'unsquashed_cdclk' variable.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_cdclk.c | 31 --
1 file
From: Ville Syrjälä
I missed a couple of spots when I was nuking the cd2x divider==1
assumptions from the squasher support. Remedy that.
And while I was in there I decided to pimp the docs to
describe the CDCLK update methods we support.
Ville Syrjälä (4):
drm/i915/cdclk: Extract cdclk_divide
From: Ville Syrjälä
Have cdclk_squash_waveform() return a u16 since that's
how many bits we have in the waveform. We alreday use
u16 everywhere else.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_cdclk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
From: Ville Syrjälä
Add a bit of documentation to briefly explain the methods
by which we can change the CDCLK frequency.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_cdclk.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_
From: Ville Syrjälä
cdclk_compute_crawl_and_squash_midpoint() was still assuming
that cd2x divider == 1 (ie. full divider == 2). Remove that
assumption by computing the dividers properly.
We'll also toss in a WARN in case the divider someone ends
up different between the old and new cdclk config
== Series Details ==
Series: drm/i915/cdclk: More hardcoded cd2x divider nukage
URL : https://patchwork.freedesktop.org/series/129611/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14235 -> Patchwork_129611v1
Summary
--
Hi all,
On Tue, 6 Feb 2024 12:28:22 +1100 Stephen Rothwell
wrote:
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
drivers/gpu/drm/xe/xe_bo.c:41:10: error: 'struct ttm_placement' has no member
named 'num_busy_placement'; did you mean 'num_
> -Original Message-
> From: Almahallawy, Khaled
> Sent: Wednesday, February 7, 2024 4:11 AM
> To: Murthy, Arun R ; intel-gfx@lists.freedesktop.org
> Cc: Shankar, Uma ; Nikula, Jani
> ; Deak, Imre ; Syrjala, Ville
>
> Subject: Re: [RFC 1/4] drm/i915/display/dp: Add DP fallback on LT
>
On 2/4/2024 7:54 PM, Suraj Kandpal wrote:
Create a remote HDCP capability shim function which can read the
remote monitor HDCP capability when in MST configuration.
--v2
-Add an assertion to make sure only mst encoder call this remote_cap
function [Ankit]
Signed-off-by: Suraj Kandpal
---
.
On 2/4/2024 7:55 PM, Suraj Kandpal wrote:
Currently we are only checking capability of remote device and not
immediate downstream device but during capability check we need are
concerned with only the HDCP capability of downstream device.
During i915_display_info reporting we need HDCP Capabili
On Tue, 2024-02-06 at 15:06 +, Murthy, Arun R wrote:
> > -Original Message-
> > From: Nikula, Jani
> > Sent: Tuesday, February 6, 2024 5:10 PM
> > To: Murthy, Arun R ;
> > intel-gfx@lists.freedesktop.org
> > Cc: Deak, Imre ; Syrjala, Ville <
> > ville.syrj...@intel.com>;
> > Shankar,
> -Original Message-
> From: Almahallawy, Khaled
> Sent: Wednesday, February 7, 2024 11:58 AM
> To: Murthy, Arun R ; Nikula, Jani
> ; intel-gfx@lists.freedesktop.org
> Cc: Shankar, Uma ; Deak, Imre
> ; Syrjala, Ville
> Subject: Re: [RFC 2/4] drm/i915/display/dp: Dont send hotplug event
On Tue, 2024-02-06 at 14:21 -0600, Lucas De Marchi wrote:
> On Tue, Feb 06, 2024 at 01:39:28PM +0100, Thomas Hellström wrote:
> > Hi
> >
> > On Tue, 2024-02-06 at 12:28 +1100, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > After merging the drm-misc tree, today's linux-next build (x86_64
> > >
65 matches
Mail list logo
