Hi Animesh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Animesh-Manna/drm-panelreplay-dpcd-register-definition-for-panelreplay/20230824-14
base:
== Series Details ==
Series: drm/i915/tc: some clean-ups in max lane count handling code (rev4)
URL : https://patchwork.freedesktop.org/series/120980/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13566_full -> Patchwork_120980v4_full
> -Original Message-
> From: Rodrigo Vivi
> Sent: Friday, August 25, 2023 10:24 AM
> To: Sripada, Radhakrishna
> Cc: Jani Nikula ;
> intel-gfx@lists.freedesktop.org;
> Raj, Ashok
> Subject: Re: [Intel-gfx] [topic/core-for-ci v2] iommu/vt-d: Check domain flags
> before setting snp
== Series Details ==
Series: drm/i915/gt: Remove interruptible flag from wait_for_space
URL : https://patchwork.freedesktop.org/series/122936/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13568 -> Patchwork_122936v1
== Series Details ==
Series: drm/i915/gt: Remove interruptible flag from wait_for_space
URL : https://patchwork.freedesktop.org/series/122936/
State : warning
== Summary ==
Error: dim sparse failed
/home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No
such file or
On Fri, Aug 25, 2023 at 02:55:33PM -0700, Matt Roper wrote:
On Thu, Aug 24, 2023 at 09:25:54PM -0700, Lucas De Marchi wrote:
On Wed, Aug 23, 2023 at 01:49:21PM -0700, Matt Roper wrote:
> On Wed, Aug 23, 2023 at 10:07:29AM -0700, Lucas De Marchi wrote:
> > LNL's south display uses the same table
When performing the i915_request_wait in wait_for_space, which itself is
called by intel_ring_begin, we do not need to apply the
I915_TASK_INTERRUPTIBLE flag. So, remove it.
Signed-off-by: Jonathan Cavitt
CC: Chris Wilson
CC: Andi Shyti
Jonathan Cavitt (1):
drm/i915/gt: Remove
When performing the i915_request_wait in wait_for_space, which itself is
called by intel_ring_begin, we do not need to apply the
I915_TASK_INTERRUPTIBLE flag. So, remove it.
Signed-off-by: Jonathan Cavitt
---
drivers/gpu/drm/i915/gt/intel_ring.c | 4 +---
1 file changed, 1 insertion(+), 3
On Thu, Aug 24, 2023 at 09:25:54PM -0700, Lucas De Marchi wrote:
> On Wed, Aug 23, 2023 at 01:49:21PM -0700, Matt Roper wrote:
> > On Wed, Aug 23, 2023 at 10:07:29AM -0700, Lucas De Marchi wrote:
> > > LNL's south display uses the same table as MTP. Check for LNL's fake PCH
> > > to make it
> -Original Message-
> From: De Marchi, Lucas
> Sent: Wednesday, August 23, 2023 10:07 AM
> To: intel...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
> Cc: Roper, Matthew D ; Srivatsa, Anusha
> ; De Marchi, Lucas
> Subject: [PATCH 22/42] drm/i915/xe2lpd: Add DC state support
> -Original Message-
> From: Intel-gfx On Behalf Of Lucas
> De
> Marchi
> Sent: Wednesday, August 23, 2023 10:07 AM
> To: intel...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
> Cc: De Marchi, Lucas ; Roper, Matthew D
>
> Subject: [Intel-gfx] [PATCH 19/42] drm/i915/xe2lpd:
just a follow up note-to-self:
On Tue, 2023-08-15 at 12:08 -0700, Teres Alexis, Alan Previn wrote:
> On Tue, 2023-08-15 at 09:56 -0400, Vivi, Rodrigo wrote:
> > On Mon, Aug 14, 2023 at 06:12:09PM -0700, Alan Previn wrote:
> > >
[snip]
in guc_submission_send_busy_loop, we are incrementing the
== Series Details ==
Series: drm/i915/gsc: define gsc fw (rev3)
URL : https://patchwork.freedesktop.org/series/119310/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13568 -> Patchwork_119310v3
Summary
---
Thanks again Rodrigo for reviewing and apologies for my tardy replies.
We are stil testing on shipping platforms and these latest patches seemed
to have reduced the frequency and solved the "system hangs" while suspending
but its still causing issues so we continue to debug. (issue is that
its
On 8/25/2023 10:20 AM, Rodrigo Vivi wrote:
On Fri, Aug 25, 2023 at 09:27:53AM -0700, Daniele Ceraolo Spurio wrote:
Add FW definition and the matching override modparam.
The GSC FW has both a release version, based on platform and a rolling
counter, and a compatibility version, which is the
== Series Details ==
Series: drm/i915/gsc: define gsc fw (rev3)
URL : https://patchwork.freedesktop.org/series/119310/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
== Series Details ==
Series: series starting with [1/2] drm/i915/display: Allow VRR parameters
mismatch in case of dual refresh rate fastset
URL : https://patchwork.freedesktop.org/series/122926/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13568 -> Patchwork_122926v1
== Series Details ==
Series: series starting with [1/2] drm/i915/display: Allow VRR parameters
mismatch in case of dual refresh rate fastset
URL : https://patchwork.freedesktop.org/series/122926/
State : warning
== Summary ==
Error: dim sparse failed
/home/kbuild2/linux/maintainer-tools/dim:
== Series Details ==
Series: series starting with [1/2] drm/i915/display: Allow VRR parameters
mismatch in case of dual refresh rate fastset
URL : https://patchwork.freedesktop.org/series/122926/
State : warning
== Summary ==
Error: dim checkpatch failed
1dedbe087f62 drm/i915/display: Allow
On Fri, Aug 25, 2023 at 02:15:27PM +, Sripada, Radhakrishna wrote:
> I was trying this as a solution for the Pipe fault errors. However, I still
> see
> The pipe fault errors which do not occur all the time.
We should avoid overloading CI with tests. But if needed because we cannot
reproduce
On Fri, Aug 25, 2023 at 09:27:53AM -0700, Daniele Ceraolo Spurio wrote:
> Add FW definition and the matching override modparam.
>
> The GSC FW has both a release version, based on platform and a rolling
> counter, and a compatibility version, which is the one tracking
> interface changes. Since
== Series Details ==
Series: drm/i915/sdvo: DDC rework and fixes (rev2)
URL : https://patchwork.freedesktop.org/series/120253/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13568 -> Patchwork_120253v2
Summary
---
On 2023-07-24 17:14, Michał Winiarski wrote:
IDR is deprecated, and since XArray manages its own state with internal
locking, it simplifies the locking on DRM side.
Additionally, don't use the IRQ-safe variant, since operating on drm
minor is not done in IRQ context.
Signed-off-by: Michał
== Series Details ==
Series: drm, cec and edid updates (rev2)
URL : https://patchwork.freedesktop.org/series/122841/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13568 -> Patchwork_122841v2
Summary
---
**SUCCESS**
Add FW definition and the matching override modparam.
The GSC FW has both a release version, based on platform and a rolling
counter, and a compatibility version, which is the one tracking
interface changes. Since what we care about is the interface, we use
the compatibility version in the binary
== Series Details ==
Series: drm, cec and edid updates (rev2)
URL : https://patchwork.freedesktop.org/series/122841/
State : warning
== Summary ==
Error: dim sparse failed
/home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No
such file or directory
In Seamless refresh rate switching when we throttle refresh rate
VRR parameters get updated.
Update these in fastset in update_crtc() hook before enabling VRR
so that the VRR range now reflects the throttled refresh rate
correctly.
This has been tested for Dual refresh rate + VRR use cases
In case of a panel that supports DRRS and seamless_m_n, dual refresh rate
allows to seamlessly switch to a downclock mode to save power.
This is expected to happen seamlessly without a full modeset as in this
case we allow the mismatch in mode's crtc clock.
With VRR fastset patch series
I was trying this as a solution for the Pipe fault errors. However, I still see
The pipe fault errors which do not occur all the time.
Will update the explanation in my follow up patches.
Thanks,
Radhakrishna Sripada
> -Original Message-
> From: Jani Nikula
> Sent: Thursday, August 24,
From: Ville Syrjälä
We already have encoder->port so get rid of the duplicate
sdvo->port.
Reviewed-by: Jani Nikula
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_sdvo.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git
From: Ville Syrjälä
Call drm_encoder_init() earlier so that we don't have to keep passing
the i915/dev_priv around separately.
v2: Reorder drm_encoder_cleanup() in the error path (Jani)
Reviewed-by: Jani Nikula
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_sdvo.c | 37
From: Ville Syrjälä
To reduce the guesswork a bit let's print out the SDVO
device i2c bus and slave address during init.
Reviewed-by: Jani Nikula
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_sdvo.c | 4
1 file changed, 4 insertions(+)
diff --git
From: Ville Syrjälä
Each SDVO device can have up to three sets of DDC pins.
Currently we just register a single i2c_adapter for the
entire SDVO device and semi-randomly pick the "correct"
set of DDC pins during intel_sdvo_tmds_sink_detect().
This doesn't make any real sense especially if we have
From: Ville Syrjälä
We should switch over to the standard "ddc" per-connector
symlink instead of rolling our own thing. The i2c specific
symlink is also in the way of reworking the SDVO DDC handling
(which is a mess atm) so get rid of it.
Reviewed-by: Jani Nikula
Signed-off-by: Ville Syrjälä
From: Ville Syrjälä
Instead of operating on the output the user specified (via the
connector) the current code tends to operate on whichever outputs
it has detected as attached. That is not how the kms uapi is supposed
to work. So simply get rid of attached_outputs and instead directly
operate
From: Ville Syrjälä
I have plans to switch the whole driver over to using
drm_connector_init_with_ddc(), and thus populate the
sysfs "ddc" consistently. The biggest hurdle is the
SDVO DDC handling, so start by cleaning that up.
I also found some other issues with the SDVO code so
some
Connectors have source physical address available in display
info. There's no need to parse the EDID again for this. Add
drm_dp_cec_attach() to do this.
Seems like the set_edid/unset_edid naming is a bit specific now that
there's no need to pass the EDID at all, so aim for attach/detach going
== Series Details ==
Series: iommu/vt-d: Check domain flags before setting snp bit in page-control
(rev2)
URL : https://patchwork.freedesktop.org/series/121893/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13562_full -> Patchwork_121893v2_full
== Series Details ==
Series: drm/i915/tc: some clean-ups in max lane count handling code (rev4)
URL : https://patchwork.freedesktop.org/series/120980/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13566 -> Patchwork_120980v4
== Series Details ==
Series: drm/i915/tc: some clean-ups in max lane count handling code (rev4)
URL : https://patchwork.freedesktop.org/series/120980/
State : warning
== Summary ==
Error: dim sparse failed
/home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No
such file
== Series Details ==
Series: drm/i915/tc: some clean-ups in max lane count handling code (rev4)
URL : https://patchwork.freedesktop.org/series/120980/
State : warning
== Summary ==
Error: dim checkpatch failed
/home/kbuild2/linux/maintainer-tools/dim: line 50: /home/kbuild2/.dimrc: No
such
Hi Jani,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm/drm-next next-20230825]
[cannot apply to drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
linus/master v6.5-rc7]
[If your patch is applied
Hi Jani,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm/drm-next next-20230825]
[cannot apply to drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
linus/master v6.5-rc7]
[If your patch is applied
== Series Details ==
Series: drm, cec and edid updates
URL : https://patchwork.freedesktop.org/series/122841/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13562_full -> Patchwork_122841v1_full
Summary
---
> -Original Message-
> From: Jani Nikula
> Sent: Thursday, August 24, 2023 5:05 PM
> To: Manna, Animesh ; intel-
> g...@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH v4 4/6] drm/i915/panelreplay: Initializaton
> and
> compute config for panel replay
>
> On Thu, 24 Aug 2023,
This function doesn't really return the pin assignment mask, but the
max lane count derived from that. So rename the function to
mtl_tc_port_get_max_lane_count() to better reflect what it really does.
Reviewed-by: Lucas De Marchi
Reviewed-by: Suraj Kandpal
Signed-off-by: Luca Coelho
---
It is irrelevant for the caller that the max lane count is being
derived from a FIA register, so having "fia" in the function name is
irrelevant. Rename the function accordingly.
Reviewed-by: Lucas De Marchi
Reviewed-by: Suraj Kandpal
Signed-off-by: Luca Coelho
---
This makes the code a bit more symmetric and readable, especially when
we start adding more display version-specific alternatives.
Reviewed-by: Suraj Kandpal
Signed-off-by: Luca Coelho
---
drivers/gpu/drm/i915/display/intel_tc.c | 32 +++--
1 file changed, 19 insertions(+),
This function is only used locally, so make it static and remove the
definition from the header file.
Reviewed-by: Suraj Kandpal
Signed-off-by: Luca Coelho
---
drivers/gpu/drm/i915/display/intel_tc.c | 2 +-
drivers/gpu/drm/i915/display/intel_tc.h | 1 -
2 files changed, 1 insertion(+), 2
Hi,
Here are four patches with some clean-ups in the code that handles the
max lane count of Type-C connections.
This is done mostly in preparation for a new way to read the pin
assignments and lane count in future devices.
In v2:
* Fix some rebasing damage.
In v3:
* Fixed "assigment"
> -Original Message-
> From: Jani Nikula
> Sent: Thursday, August 24, 2023 4:59 PM
> To: Manna, Animesh ; intel-
> g...@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH v4 1/6] drm/panelreplay: dpcd register
> definition for panelreplay
>
> On Thu, 24 Aug 2023, Animesh Manna
> -Original Message-
> From: Hogander, Jouni
> Sent: Thursday, August 24, 2023 4:55 PM
> To: Manna, Animesh ; intel-
> g...@lists.freedesktop.org
> Cc: Murthy, Arun R
> Subject: Re: [PATCH v4 6/6] drm/i915/panelreplay: enable/disable panel
> replay
>
> On Thu, 2023-08-24 at 09:39
> -Original Message-
> From: Hogander, Jouni
> Sent: Thursday, August 24, 2023 4:50 PM
> To: Manna, Animesh ; intel-
> g...@lists.freedesktop.org
> Cc: Murthy, Arun R
> Subject: Re: [PATCH v4 2/6] drm/i915/panelreplay: Added
> HAS_PANEL_REPLAY() macro
>
> On Thu, 2023-08-24 at 09:39
> -Original Message-
> From: De Marchi, Lucas
> Sent: Wednesday, August 23, 2023 8:08 PM
> To: intel...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
> Cc: Lisovskiy, Stanislav ; Kahola, Mika
> ; De Marchi, Lucas
>
> Subject: [PATCH 41/42] drm/i915/xe2lpd: Update mbus on post
> -Original Message-
> From: De Marchi, Lucas
> Sent: Wednesday, August 23, 2023 8:08 PM
> To: intel...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
> Cc: Lisovskiy, Stanislav ; Kahola, Mika
> ; De Marchi, Lucas
>
> Subject: [PATCH 37/42] drm/i915/xe2lpd: Write DBuf after
On Thu, 24 Aug 2023, Radhakrishna Sripada
wrote:
> From: Ashok Raj
>
The *why* goes here, along with a link to a gitlab issue.
Please don't expect topic/core-for-ci to have lower standards than any
other branches. That's not the case. On the contrary, you'll need the
*additional*
On Tue, 22 Aug 2023, Vinod Govindapillai wrote:
> SDP split config for DP-MST
>
> v1: Fix wrong port comparison (Jani Nikula)
>
> Vinod Govindapillai (2):
> drm/i915/display: update intel_dp_has_audio to support MST
> drm/i915/display: configure SDP split for DP-MST
Pushed to din, thanks for
On Wed, 23 Aug 2023, "Hogander, Jouni" wrote:
> On Fri, 2023-08-18 at 14:27 +0300, Jani Nikula wrote:
>> unbind_fence_ops can be const and placed in rodata.
>>
>> Signed-off-by: Jani Nikula
>
> Reviewed-by: Jouni Högander
Thanks, pushed to din.
BR,
Jani.
>
>> ---
>>
58 matches
Mail list logo
