RE: [PATCH 1/2] drm/i915/display: After joiner compute pfit_dst

2024-12-19 Thread Garg, Nemesa
> -Original Message- > From: Ville Syrjälä > Sent: Thursday, December 19, 2024 9:32 PM > To: Garg, Nemesa > Cc: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org > Subject: Re: [PATCH 1/2] drm/i915/display: After joiner compute pfit_dst > > On Thu, Dec 12, 2024 at 08:03:2

✗ Fi.CI.BUILD: failure for Revert "drm/i915/hdcp: Don't enable HDCP1.4 directly from check_link"

2024-12-19 Thread Patchwork
== Series Details == Series: Revert "drm/i915/hdcp: Don't enable HDCP1.4 directly from check_link" URL : https://patchwork.freedesktop.org/series/142871/ State : failure == Summary == Error: make failed CALLscripts/checksyscalls.sh DESCEND objtool INSTALL libsubcmd_headers CC [M]

[PATCH] Revert "drm/i915/hdcp: Don't enable HDCP1.4 directly from check_link"

2024-12-19 Thread Suraj Kandpal
This reverts commit 483f7d94a0453564ad9295288c0242136c5f36a0. This needs to be reverted since HDCP even after updating the connector state HDCP property we don't reenable HDCP until the next commit in which the CP Property is set causing compliance to fail. Signed-off-by: Suraj Kandpal --- drive

linux-next: build warnings after merge of the drm-misc tree

2024-12-19 Thread Stephen Rothwell
Hi all, After merging the drm-misc tree, today's linux-next build (htmldocs) produced these warnings: drivers/gpu/drm/xlnx/zynqmp_dpsub.h:86: warning: Function parameter or struct member 'audio' not described in 'zynqmp_dpsub' drivers/gpu/drm/xlnx/zynqmp_dpsub.c:1: warning: no structured comment

Re: [PATCH] drm/i915/dg1: Fix power gate sequence.

2024-12-19 Thread Ghimiray, Himal Prasad
On 20-12-2024 02:30, Rodrigo Vivi wrote: sub-pipe PG is not present on DG1. Setting these bits can disable other power gates and cause GPU hangs on video playbacks. VLK: 16314, 4304 Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13381 Fixes: 85a12d7eb8fe ("drm/i915/tgl: Fix

[PATCH i-g-t v2 4/4] tools/gputop: Add GT freq and c6 stats

2024-12-19 Thread Vinay Belgaumkar
Add GT C6 and Frequency support. These will use the PMU interface and are displayed per GT/device in the header. GT: 0, c6: 94.54% req_freq: 750.63 MHz act_freq:0.00 MHz GT: 1, c6: 2.75% req_freq: 1200.71 MHz act_freq: 1112.66 MHz v2: Split patch into logical units and other review commen

[PATCH i-g-t v2 3/4] lib/igt_perf: Add utils to extract PMU event info

2024-12-19 Thread Vinay Belgaumkar
Functions to parse config ID and GT bit shift for PMU events. Cc: Kamil Konieczny Cc: Rodrigo Vivi Signed-off-by: Vinay Belgaumkar --- lib/igt_perf.c | 68 ++ lib/igt_perf.h | 2 ++ 2 files changed, 70 insertions(+) diff --git a/lib/igt_perf.c

[PATCH i-g-t v2 2/4] lib/igt_drm_clients: Add pdev and driver info

2024-12-19 Thread Vinay Belgaumkar
This will be used for gathering PMU event information. Cc: Rodrigo Vivi Cc: Lucas De Marchi Cc: Kamil Konieczny Signed-off-by: Vinay Belgaumkar This will be used for gathering PMU event information. Signed-off-by: Vinay Belgaumkar /igt_debugfs.c.orig --- lib/igt_drm_clients.c | 6 ++ l

[PATCH i-g-t v2 1/4] tools/gputop: Define data structs for PMU stats

2024-12-19 Thread Vinay Belgaumkar
Prep work for adding PMU support in gputop. Cc: Rodrigo Vivi Cc: Lucas De Marchi Cc: Kamil Konieczny Signed-off-by: Vinay Belgaumkar --- tools/gputop.c | 28 1 file changed, 28 insertions(+) diff --git a/tools/gputop.c b/tools/gputop.c index 43b01f566..4e3663417

[PATCH i-g-t v2 0/4] tools/gputop: Add PMU stats

2024-12-19 Thread Vinay Belgaumkar
Use the PMU support being added in https://patchwork.freedesktop.org/series/139121/ to add freq/c6 stats. Cc: Rodrigo Vivi Cc: Lucas De Marchi Cc: Kamil Konieczny Signed-off-by: Vinay Belgaumkar Vinay Belgaumkar (4): tools/gputop: Define data structs for PMU stats lib/igt_drm_clients: Add

Re: [PATCH i-g-t] tools/gputop: Add GT freq and c6 stats

2024-12-19 Thread Belgaumkar, Vinay
On 12/18/2024 11:27 AM, Kamil Konieczny wrote: Hi Vinay, On 2024-12-15 at 16:32:38 -0800, Vinay Belgaumkar wrote: Add GT C6 and Frequency support. These will use the PMU interface and are displayed per GT/device in the header. GT: 0, c6: 94.54% req_freq: 750.63 MHz act_freq:0.00 MHz GT:

✓ i915.CI.BAT: success for drm/i915/dmc_wl: Support extra values for dmc_wl_enable for debugging

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/dmc_wl: Support extra values for dmc_wl_enable for debugging URL : https://patchwork.freedesktop.org/series/142855/ State : success == Summary == CI Bug Log - changes from CI_DRM_15873 -> Patchwork_142855v1 =

✓ i915.CI.BAT: success for drm/i915/display: Reduce global state funcs boilerplate

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/display: Reduce global state funcs boilerplate URL : https://patchwork.freedesktop.org/series/142853/ State : success == Summary == CI Bug Log - changes from CI_DRM_15873 -> Patchwork_142853v1 Summary -

RE: [PATCH 3/3] drm/i915/display: Use INTEL_GLOBAL_STATE_DEFAULTS

2024-12-19 Thread Cavitt, Jonathan
-Original Message- From: Intel-gfx On Behalf Of Gustavo Sousa Sent: Thursday, December 19, 2024 1:49 PM To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org Cc: Ville Syrjälä ; Nikula, Jani Subject: [PATCH 3/3] drm/i915/display: Use INTEL_GLOBAL_STATE_DEFAULTS > > Reduce

RE: [PATCH 2/3] drm/i915/display: Add infra to reduce global state funcs boilerplate

2024-12-19 Thread Cavitt, Jonathan
-Original Message- From: Intel-gfx On Behalf Of Gustavo Sousa Sent: Thursday, December 19, 2024 1:49 PM To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org Cc: Ville Syrjälä ; Nikula, Jani Subject: [PATCH 2/3] drm/i915/display: Add infra to reduce global state funcs boi

RE: [PATCH 1/3] drm/i915/display: Do not assume zero offset when duplicating global state

2024-12-19 Thread Cavitt, Jonathan
-Original Message- From: Intel-xe On Behalf Of Gustavo Sousa Sent: Thursday, December 19, 2024 1:49 PM To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org Cc: Ville Syrjälä ; Nikula, Jani Subject: [PATCH 1/3] drm/i915/display: Do not assume zero offset when duplicating

[PATCH 4/4] drm/i915/dmc_wl: Allow enable_dmc_wl=3 to mean "always locked"

2024-12-19 Thread Gustavo Sousa
When debugging issues that might be related to the DMC wakelock code, it might be useful to compare runs with the lock acquired while DC states are enabled vs the regular case. If issues disappear with the former, it might be a symptom of something wrong in our code. Support having this "always loc

✗ Fi.CI.SPARSE: warning for drm/i915/display: Reduce global state funcs boilerplate

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/display: Reduce global state funcs boilerplate URL : https://patchwork.freedesktop.org/series/142853/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Reduce global state funcs boilerplate

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/display: Reduce global state funcs boilerplate URL : https://patchwork.freedesktop.org/series/142853/ State : warning == Summary == Error: dim checkpatch failed ec99e692f6f4 drm/i915/display: Do not assume zero offset when duplicating global state b3d1fee

✓ i915.CI.BAT: success for drm/i915/dp: 128b/132b uncompressed SST (rev2)

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/dp: 128b/132b uncompressed SST (rev2) URL : https://patchwork.freedesktop.org/series/142547/ State : success == Summary == CI Bug Log - changes from CI_DRM_15873 -> Patchwork_142547v2 Summary ---

[PATCH 1/4] drm/i915/dmc_wl: Use enum values for enable_dmc_wl

2024-12-19 Thread Gustavo Sousa
Currently, after sanitization, enable_dmc_wl will behave like a boolean parameter (enabled vs disabled). However, in upcoming changes, we will allow more values for debugging purposes. For that, let's make the sanitized value an enumeration. Signed-off-by: Gustavo Sousa --- drivers/gpu/drm/i915/

[PATCH 2/4] drm/i915/dmc_wl: Show description string for enable_dmc_wl

2024-12-19 Thread Gustavo Sousa
We already provide the value resulting from sanitization of enable_dmc_wl in dmesg, however the reader will need to either have the meanings memorized or look them up in the parameter's documentation. Let's make things easier by providing a short human-readable name for the parameter in dmesg. Sig

[PATCH 3/4] drm/i915/dmc_wl: Allow enable_dmc_wl=2 to mean "match any register"

2024-12-19 Thread Gustavo Sousa
When debugging issues that might be related to the DMC wakelock code, it is sometimes useful to compare runs when we match any register offset vs the regular case. If issues disappear when we take the wakelock for any register, it might indicate that we are missing some offset to be tracked. Suppor

[PATCH 0/4] drm/i915/dmc_wl: Support extra values for dmc_wl_enable for debugging

2024-12-19 Thread Gustavo Sousa
This series adds support for two new values for dmc_wl_enable for debugging purposes: * 2 to mean "match any register", which makes the wakelock to be taken for every display MMIO transaction; * 3 to mean "always locked", which causes the lock to be taken as soon as the DMC wakelock me

✓ i915.CI.BAT: success for drm/i915/dg1: Fix power gate sequence. (rev3)

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/dg1: Fix power gate sequence. (rev3) URL : https://patchwork.freedesktop.org/series/85082/ State : success == Summary == CI Bug Log - changes from CI_DRM_15873 -> Patchwork_85082v3 Summary --- **

✗ Fi.CI.SPARSE: warning for drm/i915/dp: 128b/132b uncompressed SST (rev2)

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/dp: 128b/132b uncompressed SST (rev2) URL : https://patchwork.freedesktop.org/series/142547/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp: 128b/132b uncompressed SST (rev2)

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/dp: 128b/132b uncompressed SST (rev2) URL : https://patchwork.freedesktop.org/series/142547/ State : warning == Summary == Error: dim checkpatch failed 90b7afc2e7f6 drm/mst: remove mgr parameter and debug logging from drm_dp_get_vc_payload_bw() ed57d41e01

Re: [PATCH] drm/i915/dg1: Fix power gate sequence.

2024-12-19 Thread Belgaumkar, Vinay
On 12/19/2024 1:00 PM, Rodrigo Vivi wrote: sub-pipe PG is not present on DG1. Setting these bits can disable other power gates and cause GPU hangs on video playbacks. LGTM, Reviewed-by: Vinay Belgaumkar VLK: 16314, 4304 Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/133

[PATCH 0/3] drm/i915/display: Reduce global state funcs boilerplate

2024-12-19 Thread Gustavo Sousa
If we look at how the members of struct intel_global_state_funcs, we see a common pattern repeating itself. We can reduce such boilerplate by moving the common implementation to the generic global state code. This series proposes that. Gustavo Sousa (3): drm/i915/display: Do not assume zero offs

[PATCH 2/3] drm/i915/display: Add infra to reduce global state funcs boilerplate

2024-12-19 Thread Gustavo Sousa
If we look at how the members of struct intel_global_state_funcs, we see a common pattern repeating itself. Let's add the necessary infra-structure to allow reducing the boilerplate. We do that by adding common generic implementations for each member and adding a macro INTEL_GLOBAL_STATE_DEFAULTS()

[PATCH 3/3] drm/i915/display: Use INTEL_GLOBAL_STATE_DEFAULTS

2024-12-19 Thread Gustavo Sousa
Reduce global state boilerplate by using INTEL_GLOBAL_STATE_DEFAULTS(). The only case that requires customization is for the duplication of CDCLK state, which is resolved by wrapping the generic implementation. Signed-off-by: Gustavo Sousa --- drivers/gpu/drm/i915/display/intel_bw.c | 21 +

[PATCH 1/3] drm/i915/display: Do not assume zero offset when duplicating global state

2024-12-19 Thread Gustavo Sousa
The current intel_*_duplicate_state() functions assume the offset for the base member of their state structures is zero when calling kmemdup(). While that is true today, such assumption should not be made and proper offset must be applied when calling kmemdup(), otherwise we will be duplicating the

[PATCH v2 10/16] drm/i915/ddi: write payload for 128b/132b SST

2024-12-19 Thread Jani Nikula
Write the payload allocation table for 128b/132b SST. Use VCPID 1 and start from slot 0, with dp_m_n.tu slots. This is preparation for enabling 128b/132b SST. This path is not reachable yet. Indeed, we don't yet compute TU for 128b/132b SST. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/d

[PATCH v2 08/16] drm/i915/ddi: enable 128b/132b TRANS_DDI_FUNC_CTL mode for UHBR SST

2024-12-19 Thread Jani Nikula
128b/132b SST needs 128b/132b mode enabled in the TRANS_DDI_FUNC_CTL register. This is preparation for enabling 128b/132b SST. This path is not reachable yet. v2: Use the MST path instead of SST to also set transport select (Imre) Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/int

[PATCH v2 05/16] drm/i915/mst: remove crtc_state->pbn

2024-12-19 Thread Jani Nikula
The crtc_state->pbn member is only used as a temporary variable within mst_stream_find_vcpi_slots_for_bpp(). Remove it as unnecessary. Suggested-by: Imre Deak Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_display_types.h | 2 -- drivers/gpu/drm/i915/display/intel_dp_mst.c

[PATCH v2 12/16] drm/i915/ddi: enable ACT handling for 128b/132b SST

2024-12-19 Thread Jani Nikula
Add ACT handling for 128b/132b SST. This is preparation for enabling 128b/132b SST. This path is not reachable yet. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_ddi.c | 13 + 1 file changed, 13 insertions(+) diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c

[PATCH v2 16/16] drm/i915/dp: compute config for 128b/132b SST w/o DSC

2024-12-19 Thread Jani Nikula
Enable basic 128b/132b SST functionality without compression. Reuse intel_dp_mtp_tu_compute_config() to figure out the TU after we've determined we need to use an UHBR rate. It's slightly complicated as the M/N computation is done in different places in MST and SST paths, so we need to avoid trash

[PATCH v2 13/16] drm/i915/ddi: start distinguishing 128b/132b SST and MST at state readout

2024-12-19 Thread Jani Nikula
We'll want to distinguish 128b/132b SST and MST modes at state readout. There's a catch, though. From the hardware perspective, 128b/132b SST and MST programming are pretty much the same. And we can't really ask the sink at this point. If we have more than one transcoder in 128b/132b mode associat

[PATCH v2 15/16] drm/i915/ddi: disable trancoder port select for 128b/132b SST

2024-12-19 Thread Jani Nikula
128b/1232b SST will have mst_master_transcoder set and matching cpu_transcoder. Ensure disable also for 128b/132b SST. Co-developed-by: Imre Deak Signed-off-by: Imre Deak Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_ddi.c | 4 +++- 1 file changed, 3 insertions(+), 1 deleti

[PATCH v2 14/16] drm/i915/ddi: handle 128b/132b SST in intel_ddi_read_func_ctl()

2024-12-19 Thread Jani Nikula
We'll only ever get here in MST mode from MST stream encoders; the primary encoder's ->get_config() won't be called when we've detected it's MST. v2: Read mst_master_transcoder in 128b/132b SST path (Imre) Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_ddi.c | 19

[PATCH v2 11/16] drm/i915/ddi: initialize 128b/132b SST DP2 VFREQ registers

2024-12-19 Thread Jani Nikula
Write the DP2 specific VFREQ registers. This is preparation for enabling 128b/132b SST. This path is not reachable yet. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_ddi.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/gpu/drm/i915/display/intel_dd

[PATCH v2 09/16] drm/i915/ddi: 128b/132b SST also needs DP_TP_CTL_MODE_MST

2024-12-19 Thread Jani Nikula
It's not very clearly specified, and the hardware bit is ill-named, but 128b/132b SST also needs the MST mode set in the DP_TP_CTL register. This is preparation for enabling 128b/132b SST. This path is not reachable yet. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_ddi.c |

[PATCH v2 06/16] drm/i915/mst: split out a helper for figuring out the TU

2024-12-19 Thread Jani Nikula
Extract intel_dp_mtp_tu_compute_config() for figuring out the TU. Move the link configuration and mst state access to the callers. This will be easier to adapt to 128b/132b SST. v2: Don't add SST stuff here yet Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_dp_mst.c | 53

[PATCH v2 07/16] drm/i915/mst: adapt intel_dp_mtp_tu_compute_config() for 128b/132b SST

2024-12-19 Thread Jani Nikula
Handle 128b/132b SST in intel_dp_mtp_tu_compute_config(). The remote bandwidth overhead and time slot allocation are only relevant for MST; SST only needs the local bandwidth and a check that 64 slots isn't exceeded. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_dp_mst.c | 10

[PATCH v2 04/16] drm/i915/mst: change return value of mst_stream_find_vcpi_slots_for_bpp()

2024-12-19 Thread Jani Nikula
The callers of mst_stream_find_vcpi_slots_for_bpp() don't need the returned slots for anything. On the contrary, they need to jump through hoops to just distinguish between success and failure. Just return 0 instead of slots from mst_stream_find_vcpi_slots_for_bpp() for success, and simplify the ca

[PATCH v2 00/16] drm/i915/dp: 128b/132b uncompressed SST

2024-12-19 Thread Jani Nikula
This is v2 of [1], enabling uncompressed 128b/132b UHBR SST. The first one was accidentally "RFC v0", and there have been a few iterations sent to CI trybot since, with various version numbers, so I expect everyone to get royally confused about the versioning here. Sorry. Anyway, unlike with [1],

[PATCH v2 03/16] drm/i915/mst: drop connector parameter from intel_dp_mst_compute_m_n()

2024-12-19 Thread Jani Nikula
intel_dp_mst_compute_m_n() doesn't need the connector. Remove the parameter. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_dp_mst.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/displa

[PATCH v2 02/16] drm/i915/mst: drop connector parameter from intel_dp_mst_bw_overhead()

2024-12-19 Thread Jani Nikula
intel_dp_mst_bw_overhead() doesn't need the connector. Remove the parameter. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/display/intel_dp_mst.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/dis

[PATCH v2 01/16] drm/mst: remove mgr parameter and debug logging from drm_dp_get_vc_payload_bw()

2024-12-19 Thread Jani Nikula
The struct drm_dp_mst_topology_mgr *mgr parameter is only used for debug logging in case the passed in link rate or lane count are zero. There's no further error checking as such, and the function returns 0. There should be no case where the parameters are zero. The returned value is generally use

RE: [PATCH] drm/i915/display: Don't program DBUF_CTL tracker state service

2024-12-19 Thread Cavitt, Jonathan
-Original Message- > From: Roper, Matthew D > Sent: Thursday, December 19, 2024 12:50 PM > To: Cavitt, Jonathan > Cc: Vodapalli, Ravi Kumar ; > intel-gfx@lists.freedesktop.org; Vivekanandan, Balasubramani > ; De Marchi, Lucas > ; Sousa, Gustavo ; Taylor, > Clinton A ; Atwood, Matthew

[PATCH] drm/i915/dg1: Fix power gate sequence.

2024-12-19 Thread Rodrigo Vivi
sub-pipe PG is not present on DG1. Setting these bits can disable other power gates and cause GPU hangs on video playbacks. VLK: 16314, 4304 Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13381 Fixes: 85a12d7eb8fe ("drm/i915/tgl: Fix Media power gate sequence.") Cc: Vinay Belgaum

Re: [PATCH] drm/i915/display: Don't program DBUF_CTL tracker state service

2024-12-19 Thread Matt Roper
On Thu, Dec 19, 2024 at 11:39:07AM -0800, Cavitt, Jonathan wrote: > -Original Message- > From: Intel-gfx On Behalf Of Ravi > Kumar Vodapalli > Sent: Thursday, December 19, 2024 9:37 AM > To: intel-gfx@lists.freedesktop.org > Cc: Vivekanandan, Balasubramani ; > Roper, Matthew D ; De March

RE: [PATCH] drm/i915/display: Don't program DBUF_CTL tracker state service

2024-12-19 Thread Gustavo Sousa
Quoting Cavitt, Jonathan (2024-12-19 16:39:07-03:00) >-Original Message- >From: Intel-gfx On Behalf Of Ravi >Kumar Vodapalli >Sent: Thursday, December 19, 2024 9:37 AM >To: intel-gfx@lists.freedesktop.org >Cc: Vivekanandan, Balasubramani ; Roper, >Matthew D ; De Marchi, Lucas >; Sousa,

RE: [PATCH] drm/i915/display: Don't program DBUF_CTL tracker state service

2024-12-19 Thread Cavitt, Jonathan
-Original Message- From: Intel-gfx On Behalf Of Ravi Kumar Vodapalli Sent: Thursday, December 19, 2024 9:37 AM To: intel-gfx@lists.freedesktop.org Cc: Vivekanandan, Balasubramani ; Roper, Matthew D ; De Marchi, Lucas ; Sousa, Gustavo ; Taylor, Clinton A ; Atwood, Matthew S ; Bhadane,

Re: [PATCH] drm/i915/gt: Log reason for setting TAINT_WARN at reset

2024-12-19 Thread Andi Shyti
Hi Sebastian, On Thu, Dec 19, 2024 at 03:31:52PM +, Sebastian Brzezinka wrote: > TAINT_WARN is used to notify CI about non-recoverable failures, which > require device to be restarted. In some cases, there is no sufficient > information about the reason for the restart. The test runner is just

✓ i915.CI.BAT: success for drm/i915/display: Don't program DBUF_CTL tracker state service (rev2)

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/display: Don't program DBUF_CTL tracker state service (rev2) URL : https://patchwork.freedesktop.org/series/142744/ State : success == Summary == CI Bug Log - changes from CI_DRM_15873 -> Patchwork_142744v2 =

[PULL] drm-misc-fixes

2024-12-19 Thread Maarten Lankhorst
Hi Dave, Simona, (Second?) last pull request for the year. Happy holidays! Cheers, ~Maarten drm-misc-fixes-2024-12-19: drm-misc-fixes for v6.13-rc4: - udma-buf fixes related to sealing. - dma-buf build warning fix when debugfs is not enabled. - Assorted drm/panel fixes. - Correct error return i

[PATCH] drm/i915/display: Don't program DBUF_CTL tracker state service

2024-12-19 Thread Ravi Kumar Vodapalli
While display initialization along with MBUS credits programming DBUF_CTL register is also programmed, as a part of it the tracker state service field is also set to 0x8 value when default value is other than 0x8 which are for platforms past display version 13. For remaining platforms the default v

RE: [PATCH] drm/i915/display: Don't program DBUF_CTL tracker state service

2024-12-19 Thread Vodapalli, Ravi Kumar
-Original Message- From: Bhadane, Dnyaneshwar Sent: Thursday, December 19, 2024 12:55 PM To: Vodapalli, Ravi Kumar ; intel-gfx@lists.freedesktop.org Cc: Vivekanandan, Balasubramani ; Roper, Matthew D ; De Marchi, Lucas ; Sousa, Gustavo ; Taylor, Clinton A ; Atwood, Matthew S ; Kalv

✗ i915.CI.BAT: failure for annotate i915_gem_object_trylock() as __must_check

2024-12-19 Thread Patchwork
== Series Details == Series: annotate i915_gem_object_trylock() as __must_check URL : https://patchwork.freedesktop.org/series/142836/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15873 -> Patchwork_142836v1 Summary --

✗ Fi.CI.SPARSE: warning for annotate i915_gem_object_trylock() as __must_check

2024-12-19 Thread Patchwork
== Series Details == Series: annotate i915_gem_object_trylock() as __must_check URL : https://patchwork.freedesktop.org/series/142836/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

✗ Fi.CI.CHECKPATCH: warning for annotate i915_gem_object_trylock() as __must_check

2024-12-19 Thread Patchwork
== Series Details == Series: annotate i915_gem_object_trylock() as __must_check URL : https://patchwork.freedesktop.org/series/142836/ State : warning == Summary == Error: dim checkpatch failed d9ac0678af4a drm/i915/selftests: check the return value of i915_gem_object_trylock() 72b7193baf3f d

✗ Fi.CI.BUILD: failure for Remove get_task_comm() and print task comm directly

2024-12-19 Thread Patchwork
== Series Details == Series: Remove get_task_comm() and print task comm directly URL : https://patchwork.freedesktop.org/series/142837/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/142837/revisions/1/mbox/ not applied Applying: kernel: Remove ge

[PATCH 2/2] drm/i915: mark i915_gem_object_trylock() as __must_check

2024-12-19 Thread Rolf Eike Beer
When you don't look at the return code you can't know if you actually got the lock. Signed-off-by: Rolf Eike Beer --- drivers/gpu/drm/i915/gem/i915_gem_object.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/gem/i915_gem_object.h b/drivers/gpu/drm/i

[PATCH v2 2/5] arch: Remove get_task_comm() and print task comm directly

2024-12-19 Thread Yafang Shao
Since task->comm is guaranteed to be NUL-terminated, we can print it directly without the need to copy it into a separate buffer. This simplifies the code and avoids unnecessary operations. Signed-off-by: Yafang Shao Cc: Vineet Gupta Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Borislav Petkov Cc:

[PATCH v2 3/5] net: Remove get_task_comm() and print task comm directly

2024-12-19 Thread Yafang Shao
Since task->comm is guaranteed to be NUL-terminated, we can print it directly without the need to copy it into a separate buffer. This simplifies the code and avoids unnecessary operations. Signed-off-by: Yafang Shao Cc: Johannes Berg --- net/wireless/wext-core.c | 4 +--- 1 file changed, 1 ins

[PATCH v2 4/5] security: Remove get_task_comm() and print task comm directly

2024-12-19 Thread Yafang Shao
Since task->comm is guaranteed to be NUL-terminated, we can print it directly without the need to copy it into a separate buffer. This simplifies the code and avoids unnecessary operations. Signed-off-by: Yafang Shao Reviewed-by: Paul Moore Acked-by: Kees Cook Cc: James Morris Cc: "Serge E. Ha

[PATCH v2 1/5] kernel: Remove get_task_comm() and print task comm directly

2024-12-19 Thread Yafang Shao
Since task->comm is guaranteed to be NUL-terminated, we can print it directly without the need to copy it into a separate buffer. This simplifies the code and avoids unnecessary operations. Signed-off-by: Yafang Shao Cc: Serge Hallyn Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Peter Zijlstra Cc:

[PATCH 1/2] drm/i915/selftests: check the return value of i915_gem_object_trylock()

2024-12-19 Thread Rolf Eike Beer
A trylock can fail, in which case operating on the object is unsafe and unconditionally unlocking is wrong. Signed-off-by: Rolf Eike Beer --- drivers/gpu/drm/i915/gt/selftest_migrate.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gt/selftest_migrat

[PATCH v2 5/5] drivers: Remove get_task_comm() and print task comm directly

2024-12-19 Thread Yafang Shao
Since task->comm is guaranteed to be NUL-terminated, we can print it directly without the need to copy it into a separate buffer. This simplifies the code and avoids unnecessary operations. Signed-off-by: Yafang Shao Reviewed-by: Jiri Slaby (For tty) Reviewed-by: Lyude Paul (For nouveau) Cc: Od

[PATCH 0/2] annotate i915_gem_object_trylock() as __must_check

2024-12-19 Thread Rolf Eike Beer
A while ago I did an attempt to convert some *_trylock*() functions to __must_check annotation. I have refreshed that and the only new compile error I found was in i915/gt/selftest_migrate.c. Here is what I have come up with as a solution for this. I have not observed any actual error about thi

[PATCH v2 0/5] Remove get_task_comm() and print task comm directly

2024-12-19 Thread Yafang Shao
Since task->comm is guaranteed to be NUL-terminated, we can print it directly without the need to copy it into a separate buffer. This simplifies the code and avoids unnecessary operations. v1->v2: - Don't add "%pTN" (Petr, Kalle, Borislav, Andy, Linus) v1: https://lore.kernel.org/all/20241213054

Re: [PATCH 1/2] drm/i915/display: After joiner compute pfit_dst

2024-12-19 Thread Ville Syrjälä
On Thu, Dec 12, 2024 at 08:03:28PM +0530, Nemesa Garg wrote: > In panel fitter/pipe scaler scenario the pch_pfit configuration > currently takes place before accounting for pipe_src width for > joiner. This causes issue when pch_pfit and joiner get enabled > together.So once pipe src is computed ad

RE: [PATCH 2/2] drm/i915/display: Initialize pipe_src in compute stage

2024-12-19 Thread Garg, Nemesa
> -Original Message- > From: Cavitt, Jonathan > Sent: Thursday, December 12, 2024 9:25 PM > To: Garg, Nemesa ; intel-gfx@lists.freedesktop.org; > intel...@lists.freedesktop.org > Cc: Garg, Nemesa ; Cavitt, Jonathan > > Subject: RE: [PATCH 2/2] drm/i915/display: Initialize pipe_src in c

RE: [PATCH 1/2] drm/i915/display: After joiner compute pfit_dst

2024-12-19 Thread Garg, Nemesa
> -Original Message- > From: Cavitt, Jonathan > Sent: Thursday, December 12, 2024 9:24 PM > To: Garg, Nemesa ; intel-gfx@lists.freedesktop.org; > intel...@lists.freedesktop.org > Cc: Garg, Nemesa ; Cavitt, Jonathan > > Subject: RE: [PATCH 1/2] drm/i915/display: After joiner compute pfit

✓ i915.CI.BAT: success for drm/i915/scaler: Scaler cleanups and tracepoints

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/scaler: Scaler cleanups and tracepoints URL : https://patchwork.freedesktop.org/series/142828/ State : success == Summary == CI Bug Log - changes from CI_DRM_15871 -> Patchwork_142828v1 Summary ---

✗ Fi.CI.CHECKPATCH: warning for drm/i915/scaler: Scaler cleanups and tracepoints

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/scaler: Scaler cleanups and tracepoints URL : https://patchwork.freedesktop.org/series/142828/ State : warning == Summary == Error: dim checkpatch failed 5e3d242efe8e drm/i915/scaler: Extract skl_scaler_min_src_size() 32e8df2e586f drm/i915/scaler: Extract

Re: [PATCH v2] drm/i915/display: UHBR rates for Thunderbolt

2024-12-19 Thread Imre Deak
On Thu, Dec 19, 2024 at 01:35:11PM +0200, Jani Nikula wrote: > On Thu, 19 Dec 2024, "Kahola, Mika" wrote: > > Thanks for the review! Patch is now merged with the change of naming > > to XE3_*. This is used elsewhere in the driver so maybe it's ok to use > > here as well. > > Nag, I don't really l

[PATCH 8/8] drm/i915/scaler: Add scaler tracepoints

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä Add some tracpoints around skl+ scaler programming to help with debugging. Signed-off-by: Ville Syrjälä --- .../drm/i915/display/intel_display_trace.h| 99 +++ drivers/gpu/drm/i915/display/skl_scaler.c | 8 ++ 2 files changed, 107 insertions(+) dif

[PATCH 7/8] drm/i915/scaler: s/excdeed/exceed/

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä Fix typo s/excdeed/exceed/ Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/skl_scaler.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/display/skl_scaler.c b/drivers/gpu/drm/i915/display/skl_scaler.c index f6d76ef1a85

[PATCH 6/8] drm/i915/scaler: Pimp scaler debugs

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä Include the standard "[CRTC:...]" information in the scaler debugs to make life easier. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/skl_scaler.c | 25 +++ 1 file changed, 16 insertions(+), 9 deletions(-) diff --git a/drivers/gpu/drm/i9

[PATCH 5/8] drm/i915/scaler: Nuke redundant code

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä The tgl+ and mtl+ numbers in skl_scaler_max_dst_size() are identical. Combine them to a single piece of code. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/skl_scaler.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/gpu/drm/i

[PATCH 4/8] drm/i915/scaler: Extract skl_scaler_max_dst_size()

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä The SKL_MAX_DST_* defines just make things hard to read. Get rid of them and introduce an easy to read function in their place. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/skl_scaler.c | 44 +++ 1 file changed, 21 insertions(+), 23 dele

[PATCH 2/8] drm/i915/scaler: Extract skl_scaler_max_src_size()

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä The SKL_MAX_SRC_* defines just make things hard to read. Get rid of them and introduce an easy to read function in their place. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/skl_scaler.c | 37 +-- 1 file changed, 21 insertions(+), 16 dele

[PATCH 3/8] drm/i915/scaler: Extract skl_scaler_min_dst_size()

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä The SKL_MIN_DST_* defines just make things hard to read. Get rid of them and introduce an easy to read function in their place. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/skl_scaler.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff

[PATCH 1/8] drm/i915/scaler: Extract skl_scaler_min_src_size()

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä The SKL_MIN_*SRC_* defines just make things hard to read. Get rid of them and introduce an easy to read function in their place. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/skl_scaler.c | 25 --- 1 file changed, 13 insertions(+), 12 del

[PATCH 0/8] drm/i915/scaler: Scaler cleanups and tracepoints

2024-12-19 Thread Ville Syrjala
From: Ville Syrjälä Do a bunch of cleanup in the scaler code, and add rudimentary scaler tracpoints to aid debugging. Ville Syrjälä (8): drm/i915/scaler: Extract skl_scaler_min_src_size() drm/i915/scaler: Extract skl_scaler_max_src_size() drm/i915/scaler: Extract skl_scaler_min_dst_size()

[PULL] drm-misc-next

2024-12-19 Thread Maxime Ripard
Hi Dave, Sima, Here's this week drm-misc-next PR. Maxime drm-misc-next-2024-12-19: drm-misc-next for 6.14: UAPI Changes: Cross-subsystem Changes: Core Changes: - connector: Add a mutex to protect ELD access, Add a helper to create a connector in two steps Driver Changes: - amdxdna: A

RE: [PATCH v2] drm/i915/display: UHBR rates for Thunderbolt

2024-12-19 Thread Jani Nikula
On Thu, 19 Dec 2024, "Kahola, Mika" wrote: > Thanks for the review! Patch is now merged with the change of naming > to XE3_*. This is used elsewhere in the driver so maybe it's ok to use > here as well. Nag, I don't really like modifying patches while applying. Personally, I try to avoid it altog

RE: [PATCH v2] drm/i915/display: UHBR rates for Thunderbolt

2024-12-19 Thread Kahola, Mika
> -Original Message- > From: Deak, Imre > Sent: Wednesday, 18 December 2024 16.57 > To: Kahola, Mika > Cc: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org > Subject: Re: [PATCH v2] drm/i915/display: UHBR rates for Thunderbolt > > On Tue, Dec 17, 2024 at 04:34:40PM +0200,

Re: [PATCH v7] drm/i915/selftests: Implement frequency logging for energy reading validation

2024-12-19 Thread Andi Shyti
Hi Sk, On Fri, Nov 29, 2024 at 09:17:16PM +0530, Sk Anirban wrote: > Add RC6 & RC0 frequency printing to ensure accurate energy > readings aimed at addressing GPU energy leaks and power > measurement failures. > Also update sleep time for RC6 mode to match RC0. > > v2: > - Improved commit messa

RE: [PATCH v3 03/10] mtd: intel-dg: implement access functions

2024-12-19 Thread Usyskin, Alexander
> > + > > +static ssize_t idg_nvm_rewrite_partial(struct intel_dg_nvm *nvm, loff_t to, > > + loff_t offset, size_t len, const u32 > *newdata) > > +{ > > + u32 data = idg_nvm_read32(nvm, to); > > + > > + if (idg_nvm_error(nvm)) > > + return -EIO; > > +

Re: [PATCH v7] drm/i915/selftests: Implement frequency logging for energy reading validation

2024-12-19 Thread Andi Shyti
Hi Sk, On Fri, Nov 29, 2024 at 09:17:16PM +0530, Sk Anirban wrote: > Add RC6 & RC0 frequency printing to ensure accurate energy > readings aimed at addressing GPU energy leaks and power > measurement failures. > Also update sleep time for RC6 mode to match RC0. > > v2: > - Improved commit messa

Re: [PATCH v2 1/1] drm/i915/gt: Increase a time to retry RING_HEAD reset

2024-12-19 Thread Andi Shyti
Hi Nitin, On Tue, Dec 17, 2024 at 12:05:32PM +0530, Nitin Gote wrote: > Issue seen again where engine resets fails because the engine resumes from > an incorrect RING_HEAD. HEAD is still not 0 even after writing into it. > This seems to be timing issue and we experimented different values from 5ms

Re: [PATCH] drm/i915/gt: Add logging before setting TAINT_WARN

2024-12-19 Thread Andi Shyti
Hi Sebastian, On Wed, Dec 18, 2024 at 07:55:30PM +, Sebastian Brzezinka wrote: > Adding TAINT_WARN is expected when GPU cannot be restarted, informing > about it will make it easier to find the source of the failure. > > Right now TAINT_WARN will cause CI machine to restart, leaving only err

✗ i915.CI.BAT: failure for drm/i915/gvt: store virtual_dp_monitor_edid in rodata (rev2)

2024-12-19 Thread Patchwork
== Series Details == Series: drm/i915/gvt: store virtual_dp_monitor_edid in rodata (rev2) URL : https://patchwork.freedesktop.org/series/142793/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15868 -> Patchwork_142793v2 Summ