Re: [PATCH 19/19] drm/i915: pass dev_priv explicitly to PORT_ALPM_LFPS_CTL

2024-04-30 Thread Rodrigo Vivi
Reviewed-by: Rodrigo Vivi On Tue, Apr 30, 2024 at 01:10:13PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the PORT_ALPM_LFPS_CTL register macro. > > Signed-off-by: Jani Nikula > --- > drivers/gpu/drm/i915/display/intel_psr.c

Re: [PATCH 18/19] drm/i915: pass dev_priv explicitly to PORT_ALPM_CTL

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:12PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the PORT_ALPM_CTL register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c | 6

Re: [PATCH 17/19] drm/i915: pass dev_priv explicitly to ALPM_CTL2

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:11PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the ALPM_CTL2 register macro. > > Signed-off-by: Jani Nikula > --- > drivers/gpu/drm/i915/display/intel_psr_regs.h | 2 +- > 1 file changed, 1 insertio

Re: [PATCH 16/19] drm/i915: pass dev_priv explicitly to ALPM_CTL

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:10PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the ALPM_CTL register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c | 4 ++--

Re: [PATCH 15/19] drm/i915: pass dev_priv explicitly to PIPE_SRCSZ_ERLY_TPT

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:09PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the PIPE_SRCSZ_ERLY_TPT register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_cursor.c

Re: [PATCH 14/19] drm/i915: pass dev_priv explicitly to PSR2_MAN_TRK_CTL

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:08PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the PSR2_MAN_TRK_CTL register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c

Re: [PATCH 13/19] drm/i915: pass dev_priv explicitly to _PSR2_SU_STATUS

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:07PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the _PSR2_SU_STATUS register macro. > > Signed-off-by: Jani Nikula why aren't we going one level up here already? > --- > drivers/gpu/drm/i915/displa

Re: [PATCH 12/19] drm/i915: pass dev_priv explicitly to EDP_PSR2_STATUS

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:06PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR2_STATUS register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c |

Re: [PATCH 11/19] drm/i915: pass dev_priv explicitly to PSR_EVENT

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:05PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the PSR_EVENT register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c | 4 +++

Re: [PATCH 10/19] drm/i915: pass dev_priv explicitly to EDP_PSR2_CTL

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:04PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR2_CTL register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c | 15

Re: [PATCH 09/19] drm/i915: pass dev_priv explicitly to EDP_PSR_DEBUG

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:03PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR_DEBUG register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c | 2

Re: [PATCH 08/19] drm/i915: pass dev_priv explicitly to EDP_PSR_PERF_CNT

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:02PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR_PERF_CNT register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c

Re: [PATCH 07/19] drm/i915: pass dev_priv explicitly to EDP_PSR_STATUS

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:01PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR_STATUS register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c |

Re: [PATCH 06/19] drm/i915: pass dev_priv explicitly to EDP_PSR_AUX_DATA

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:10:00PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR_AUX_DATA register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c

Re: [PATCH 05/19] drm/i915: pass dev_priv explicitly to EDP_PSR_AUX_CTL

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:09:59PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR_AUX_CTL register macro. > > Signed-off-by: Jani Nikula Two things crossing my mind at this point: 1. perhaps we should have grouped by imp

Re: [PATCH 04/19] drm/i915: pass dev_priv explicitly to TRANS_PSR_IIR

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:09:58PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the TRANS_PSR_IIR register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_display_irq.c

Re: [PATCH 03/19] drm/i915: pass dev_priv explicitly to TRANS_PSR_IMR

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:09:57PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the TRANS_PSR_IMR register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_display_irq.c

Re: [PATCH 02/19] drm/i915: pass dev_priv explicitly to EDP_PSR_CTL

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:09:56PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the EDP_PSR_CTL register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c | 2 +

Re: [PATCH 01/19] drm/i915: pass dev_priv explicitly to TRANS_EXITLINE

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 01:09:55PM +0300, Jani Nikula wrote: > Avoid the implicit dev_priv local variable use, and pass dev_priv > explicitly to the TRANS_EXITLINE register macro. > > Signed-off-by: Jani Nikula Reviewed-by: Rodrigo Vivi > --- > drivers/gpu/drm/i915/display/intel_psr.c |

✗ Fi.CI.IGT: failure for drm/i915: fix missing linux/debugfs.h includes

2024-04-30 Thread Patchwork
== Series Details == Series: drm/i915: fix missing linux/debugfs.h includes URL : https://patchwork.freedesktop.org/series/133075/ State : failure == Summary == CI Bug Log - changes from CI_DRM_14682_full -> Patchwork_133075v1_full Summary

Re: [PATCH v1 03/12] drm/i915: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
On 4/30/2024 1:29 PM, Rodrigo Vivi wrote: > On Tue, Apr 30, 2024 at 05:38:02PM +, Easwar Hariharan wrote: >> I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" >> with more appropriate terms. Inspired by and following on to Wolfram's >> series to fix drivers/i2c/[1], f

Re: [PATCH v1 03/12] drm/i915: Make I2C terminology more inclusive

2024-04-30 Thread Rodrigo Vivi
On Tue, Apr 30, 2024 at 05:38:02PM +, Easwar Hariharan wrote: > I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" > with more appropriate terms. Inspired by and following on to Wolfram's > series to fix drivers/i2c/[1], fix the terminology for users of > I2C_ALGOBIT b

[linux-next:master] BUILD REGRESSION d04466706db5e241ee026f17b5f920e50dee26b5

2024-04-30 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: d04466706db5e241ee026f17b5f920e50dee26b5 Add linux-next specific files for 20240430 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202404301738.j71xgyar-...@intel.com Unverified

[PULL] drm-intel-next

2024-04-30 Thread Rodrigo Vivi
Hi Dave and Sima, Here goes one extra, and really the last one targeting 6.10. We have decided to do this extra one so we could include the good clean-up on i915/xe's fbdev work done by Thomas Zimmermann. And it looks like he has more work on top of that, so it would be good to propagate this ini

✗ Fi.CI.BUILD: failure for Make I2C terminology more inclusive for I2C Algobit and consumers (rev2)

2024-04-30 Thread Patchwork
== Series Details == Series: Make I2C terminology more inclusive for I2C Algobit and consumers (rev2) URL : https://patchwork.freedesktop.org/series/131867/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/131867/revisions/2/mbox/ not applied Applyi

✓ Fi.CI.BAT: success for Enable display support for Battlemage (rev3)

2024-04-30 Thread Patchwork
== Series Details == Series: Enable display support for Battlemage (rev3) URL : https://patchwork.freedesktop.org/series/132429/ State : success == Summary == CI Bug Log - changes from CI_DRM_14684 -> Patchwork_132429v3 Summary --- *

✗ Fi.CI.SPARSE: warning for Enable display support for Battlemage (rev3)

2024-04-30 Thread Patchwork
== Series Details == Series: Enable display support for Battlemage (rev3) URL : https://patchwork.freedesktop.org/series/132429/ 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 Enable display support for Battlemage (rev3)

2024-04-30 Thread Patchwork
== Series Details == Series: Enable display support for Battlemage (rev3) URL : https://patchwork.freedesktop.org/series/132429/ State : warning == Summary == Error: dim checkpatch failed f1746e09cce1 drm/i915/bmg: Lane reversal requires writes to both context lanes 1f4c0c333523 drm/i915/bmg:

✓ Fi.CI.BAT: success for drm/i915/guc: avoid FIELD_PREP warning (rev2)

2024-04-30 Thread Patchwork
== Series Details == Series: drm/i915/guc: avoid FIELD_PREP warning (rev2) URL : https://patchwork.freedesktop.org/series/114145/ State : success == Summary == CI Bug Log - changes from CI_DRM_14684 -> Patchwork_114145v2 Summary ---

✗ Fi.CI.SPARSE: warning for drm/i915/guc: avoid FIELD_PREP warning (rev2)

2024-04-30 Thread Patchwork
== Series Details == Series: drm/i915/guc: avoid FIELD_PREP warning (rev2) URL : https://patchwork.freedesktop.org/series/114145/ 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/guc: avoid FIELD_PREP warning (rev2)

2024-04-30 Thread Patchwork
== Series Details == Series: drm/i915/guc: avoid FIELD_PREP warning (rev2) URL : https://patchwork.freedesktop.org/series/114145/ State : warning == Summary == Error: dim checkpatch failed 313ad2270b44 drm/i915/guc: avoid FIELD_PREP warning -:10: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum

Re: [PATCH v3 18/19] drm/i915/display: perform transient flush

2024-04-30 Thread Lucas De Marchi
+Jani On Tue, Apr 30, 2024 at 10:28:49AM GMT, Radhakrishna Sripada wrote: From: Matthew Auld Perform manual transient cache flush prior to flip and at the end of frontbuffer_flush. This is needed to ensure display engine doesn't see garbage if the surface is L3:XD dirty. Testcase: igt@xe-pat@

Re: [PATCH v3 19/19] drm/xe/bmg: Enable the display support

2024-04-30 Thread Lucas De Marchi
On Tue, Apr 30, 2024 at 10:28:50AM GMT, Radhakrishna Sripada wrote: From: Balasubramani Vivekanandan Enable the display support for Battlemage Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Shekhar Chauhan Signed-off-by: Radhakrishna Sripada Acked-by: Lucas De Marchi to merge thi

[PATCH v1 12/12] fbdev/viafb: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 11/12] fbdev/smscufx: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 10/12] sfc: falcon: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 09/12] media: cx23885: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 04/12] media: au0828: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 08/12] media: ivtv: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 07/12] media: cx25821: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 06/12] media: cx18: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 05/12] media: cobalt: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 03/12] drm/i915: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 02/12] drm/gma500: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 01/12] drm/amdgpu, drm/radeon: Make I2C terminology more inclusive

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specific

[PATCH v1 00/12] Make I2C terminology more inclusive for I2C Algobit and consumers

2024-04-30 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of the I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the spec

[PATCH v3 14/19] Revert "drm/i915/dgfx: DGFX uses direct VBT pin mapping"

2024-04-30 Thread Radhakrishna Sripada
From: Ankit Nautiyal This reverts commit 562f33836f519a235e5c5e71bcc723ab1faccd2f. For BMG it seems that the VBT to DDI mapping does not follow DG1, and DG2, but follows ADLP mapping given in Bspec:20124. Signed-off-by: Ankit Nautiyal Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt

[PATCH v3 13/19] drm/i915/bmg: BMG should re-use MTL's south display logic

2024-04-30 Thread Radhakrishna Sripada
From: Matt Roper Battlemage's south display is the same as Meteor Lake's, including the need to invert the HPD pins, which Lunar Lake does not need. Signed-off-by: Matt Roper Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Dnyaneshwar Bhadane Signed-off-by: Radhakrishna Sripada --- d

[PATCH v3 15/19] drm/i915/xe2hpd: Set maximum DP rate to UHBR13.5

2024-04-30 Thread Radhakrishna Sripada
From: Balasubramani Vivekanandan Max supported speed by xe2hpd is UHBR13.5. Limit the max DP source rate to it. Bspec: 67066 Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Shekhar Chauhan Signed-off-by: Radhakrishna Sripada --- drivers/gpu/drm/i915/display/intel_dp.c | 3 +++ 1 file

[PATCH v3 17/19] drm/xe/device: implement transient flush

2024-04-30 Thread Radhakrishna Sripada
From: Nirmoy Das Display surfaces can be tagged as transient by mapping it using one of the various L3:XD PAT index modes on Xe2. The expectation is that KMD needs to request transient data flush at the start of flip sequence to ensure all transient data in L3 cache is flushed to memory. Add a ro

[PATCH v3 19/19] drm/xe/bmg: Enable the display support

2024-04-30 Thread Radhakrishna Sripada
From: Balasubramani Vivekanandan Enable the display support for Battlemage Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Shekhar Chauhan Signed-off-by: Radhakrishna Sripada --- drivers/gpu/drm/xe/xe_pci.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/xe/xe_pci.

[PATCH v3 12/19] drm/i915/xe2hpd: Do not program MBUS_DBOX BW credits

2024-04-30 Thread Radhakrishna Sripada
From: José Roberto de Souza No display IP beyond Xe_LPD+ has "BW credits" bits in MBUS_DBOX_CTL register. Restrict the programming only to Xe_LPD+. BSpec: 49213 CC: Matt Roper Signed-off-by: José Roberto de Souza Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt Roper Signed-off-by

[PATCH v3 11/19] drm/i915/xe2hpd: Add max memory bandwidth algorithm

2024-04-30 Thread Radhakrishna Sripada
From: Matt Roper Unlike DG2, Xe2_HPD does support multiple GV points with different maximum memory bandwidths, but uses a much simpler algorithm than igpu platforms use. Bspec: 64631 CC: Jani Nikula Signed-off-by: Matt Roper Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Radhakrishna

[PATCH v3 08/19] drm/i915/xe2hpd: update pll values in sync with Bspec

2024-04-30 Thread Radhakrishna Sripada
From: Ravi Kumar Vodapalli DP/eDP and HDMI pll values are updated for Xe2_HPD platform v2: Removed the unsupported mtl_c20_dp_uhbr20 from xehpd_c20_dp_tables Bspec: 74165 Signed-off-by: Ravi Kumar Vodapalli Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt Roper Signed-off-by: Radh

[PATCH v3 09/19] drm/i915/xe2hpd: Add display info

2024-04-30 Thread Radhakrishna Sripada
From: Lucas De Marchi Add initial display info for xe2hpd. It is similar to xelpdp, but with no PORT_B. v2: Inherit from XE_LPDP_FEATURES instead of XE_LPD_FEATURES Bspec: 67066 CC: Matt Roper Signed-off-by: Lucas De Marchi Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt Roper S

[PATCH v3 07/19] drm/i915/xe2hpd: Add support for eDP PLL configuration

2024-04-30 Thread Radhakrishna Sripada
From: Balasubramani Vivekanandan Tables for eDP PHY PLL configuration for different link rates added for Xe2_HPD. Previous platforms were using C10 PHY for eDP port whereas Xe2_HPD has C20 PHY. v2: Updated with a more appropriate Bspec number. Bspec: 74165 CC: Clint Taylor Signed-off-by: Balas

[PATCH v3 16/19] drm/xe/gt_print: add xe_gt_err_once()

2024-04-30 Thread Radhakrishna Sripada
From: Matthew Auld Needed in an upcoming patch, where we want GT level print, but only which to trigger once to avoid flooding dmesg. Signed-off-by: Matthew Auld Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Nirmoy Das Signed-off-by: Radhakrishna Sripada --- drivers/gpu/drm/xe/xe_g

[PATCH v3 18/19] drm/i915/display: perform transient flush

2024-04-30 Thread Radhakrishna Sripada
From: Matthew Auld Perform manual transient cache flush prior to flip and at the end of frontbuffer_flush. This is needed to ensure display engine doesn't see garbage if the surface is L3:XD dirty. Testcase: igt@xe-pat@display-vs-wb-transient Signed-off-by: Matthew Auld Signed-off-by: Balasubra

[PATCH v3 05/19] drm/i915/xe2hpd: Properly disable power in port A

2024-04-30 Thread Radhakrishna Sripada
From: José Roberto de Souza Xe2_HPD has a different value to power down port A. BSpec: 65450 Signed-off-by: José Roberto de Souza Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt Roper Signed-off-by: Radhakrishna Sripada --- drivers/gpu/drm/i915/display/intel_cx0_phy.c | 17 +

[PATCH v3 00/19] Enable display support for Battlemage

2024-04-30 Thread Radhakrishna Sripada
Adds display support for Battlemage. v4: * Dropped patch "drm/i915/xe2hpd: Skip CCS modifiers" as there is already a patch merged taking care of this fix. * Dropped patch "drm/i915/display: Enable RM timeout detection" as it is not really a BMG enablement patch. Will be posted as a separat

[PATCH v3 10/19] drm/i915/xe2hpd: Configure CHICKEN_MISC_2 before enabling planes

2024-04-30 Thread Radhakrishna Sripada
From: Anusha Srivatsa Add step 9 from initialize display sequence. v2: Commit subject improved Bpsec: 49189 Signed-off-by: Anusha Srivatsa Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt Roper Signed-off-by: Radhakrishna Sripada --- drivers/gpu/drm/i915/display/intel_display_po

[PATCH v3 06/19] drm/i915/xe2hpd: Add new C20 PHY SRAM address

2024-04-30 Thread Radhakrishna Sripada
From: Balasubramani Vivekanandan Xe2_HPD has different offsets for C20 PHY SRAM configuration context location. Use the display version to select the right address. Note that Xe2_LPD uses the same C20 SRAM offsets used by Xe_LPDP (i.e. MTL's display). According to the BSpec, currently, only Xe2_

[PATCH v3 02/19] drm/i915/bmg: Define IS_BATTLEMAGE macro

2024-04-30 Thread Radhakrishna Sripada
From: Balasubramani Vivekanandan Display code uses IS_BATTLEMAGE macro but the platform support doesn't exist in i915. So fake IS_BATTLEMAGE macro defined to enable building i915 code. We should make sure the macro parameter is used in the always-false expression so that we don't run into "unuse

[PATCH v3 01/19] drm/i915/bmg: Lane reversal requires writes to both context lanes

2024-04-30 Thread Radhakrishna Sripada
From: Clint Taylor Write both CX0 Lanes for Context Toggle for all except TC pin assignment D. v2: Update title(RK) Bspec: 64539 CC: Jani Nikula Signed-off-by: Clint Taylor Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt Roper Signed-off-by: Radhakrishna Sripada --- drivers/gpu

[PATCH v3 03/19] drm/i915/xe2hpd: Initial cdclk table

2024-04-30 Thread Radhakrishna Sripada
From: Clint Taylor Add Xe2_HPD specific CDCLK table and use MTL Funcs. Bspec: 65243 CC: Lucas De Marchi Signed-off-by: Clint Taylor Signed-off-by: Balasubramani Vivekanandan Reviewed-by: Matt Roper Signed-off-by: Radhakrishna Sripada --- drivers/gpu/drm/i915/display/intel_cdclk.c | 11

[PATCH v3 04/19] drm/i915/bmg: Extend DG2 tc check to future

2024-04-30 Thread Radhakrishna Sripada
Discrete cards use the Port numbers TC1-4 for the offsets. The regular flow for type-c subsystem port initialization can be skipped. This check is present in DG2. Extend this to future discrete products. Signed-off-by: Radhakrishna Sripada Signed-off-by: Balasubramani Vivekanandan Reviewed-by: M

[PATCH] drm/i915/guc: avoid FIELD_PREP warning

2024-04-30 Thread Julia Filipchuk
From: Arnd Bergmann With gcc-7 and earlier, there are lots of warnings like In file included from :0:0: In function '__guc_context_policy_add_priority.isra.66', inlined from '__guc_context_set_prio.isra.67' at drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:3292:3, inlined from 'guc_c

✓ Fi.CI.BAT: success for drm/i915: fix missing linux/debugfs.h includes

2024-04-30 Thread Patchwork
== Series Details == Series: drm/i915: fix missing linux/debugfs.h includes URL : https://patchwork.freedesktop.org/series/133075/ State : success == Summary == CI Bug Log - changes from CI_DRM_14682 -> Patchwork_133075v1 Summary ---

Re: [PATCH] drm/i915: fix missing linux/debugfs.h includes

2024-04-30 Thread Danilo Krummrich
On 4/30/24 16:53, Jani Nikula wrote: On Tue, 30 Apr 2024, Danilo Krummrich wrote: After dropping linux/debugfs.h include from drm/drm_print.h the following files in i915 miss the linux/debugfs.h include: i915_debugfs.c, i915_debugfs_params.c and i915_gpu_error.c. Add the include to fix the cor

✗ Fi.CI.CHECKPATCH: warning for drm/i915: fix missing linux/debugfs.h includes

2024-04-30 Thread Patchwork
== Series Details == Series: drm/i915: fix missing linux/debugfs.h includes URL : https://patchwork.freedesktop.org/series/133075/ State : warning == Summary == Error: dim checkpatch failed 20b2bfeb6ee9 drm/i915: fix missing linux/debugfs.h includes -:12: WARNING:BAD_REPORTED_BY_LINK: Reported

[PATCH v8 20/35] dyndbg-doc: add classmap info to howto

2024-04-30 Thread Jim Cromie
Describe the 3 API macros providing dynamic_debug's classmaps DYNDBG_CLASSMAP_DEFINE - create, exports a module's classmap DYNDBG_CLASSMAP_USE- refer to exported map DYNDBG_CLASSMAP_PARAM - bind control param to the classmap DYNDBG_CLASSMAP_PARAM_REF + use module's storage - __drm_debug cc:

[PATCH v8 21/35] dyndbg: treat comma as a token separator

2024-04-30 Thread Jim Cromie
Treat comma as a token terminator, just like a space. This allows a user to avoid quoting hassles when spaces are otherwise needed: :#> modprobe drm dyndbg=class,DRM_UT_CORE,+p\;class,DRM_UT_KMS,+p or as a boot arg: drm.dyndbg=class,DRM_UT_CORE,+p # todo: support multi-query here Given the

[PATCH v8 18/35] selftests-dyndbg: exit 127 if no facility

2024-04-30 Thread Jim Cromie
Test if /proc/dynamic_debug/control exists, exit 127 otherwise. This distinguishes an untestable config from both pass & fail. The 127 choice is pretty arbitrary, but imitating bisect. That control file's presense guarantees that dynamic-debugging is configured (unless /proc is off, unusually), wi

[PATCH v8 04/35] dyndbg: reword "class unknown, " to "class:_UNKNOWN_"

2024-04-30 Thread Jim Cromie
When a dyndbg classname is unknown to a kernel module (as before previous patch), the callsite is un-addressable via >control queries. The control-file displays this condition as "class unknown," currently. That spelling is sub-optimal, so change it to "class:_UNKNOWN_" to loudly announce the err

[PATCH v8 06/35] dyndbg: replace classmap list with a vector

2024-04-30 Thread Jim Cromie
Classmaps are stored in an elf section/array, but are individually list-linked onto dyndbg's per-module ddebug_table for operation. This is unnecessary; even when ddebug_attach_classmap() is handling the builtin section (with classmaps for multiple builtin modules), its contents are ordered, so a

[PATCH v8 33/35] drm-drivers: DRM_CLASSMAP_USE in 2nd batch of drivers, helpers

2024-04-30 Thread Jim Cromie
Add a DRM_CLASSMAP_USE declaration to 2nd batch of helpers and *_drv.c files. For drivers, add the decl just above the module's PARAMs, since it identifies the "inherited" drm.debug param. Note: with CONFIG_DRM_USE_DYNAMIC_DEBUG=y, a module not also declaring DRM_CLASSMAP_USE will have its class'

[PATCH v8 15/35] dyndbg-API: remove DD_CLASS_TYPE_(DISJOINT|LEVEL)_NAMES and code

2024-04-30 Thread Jim Cromie
Remove the NAMED class types; these 2 classmap types accept class names at the PARAM interface, for example: echo +DRM_UT_CORE,-DRM_UT_KMS > /sys/module/drm/parameters/debug_names The code works, but its only used by test-dynamic-debug, and wasn't asked for by anyone else, so reduce test-surfac

[PATCH v8 25/35] docs/dyndbg: explain new delimiters: comma, percent

2024-04-30 Thread Jim Cromie
Add mention of comma and percent delimiters into the respective paragraphs describing their equivalents: space and newline. Signed-off-by: Jim Cromie --- .../admin-guide/dynamic-debug-howto.rst| 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/Documen

[PATCH v8 34/35] drm: restore CONFIG_DRM_USE_DYNAMIC_DEBUG un-BROKEN

2024-04-30 Thread Jim Cromie
Time for some quality CI Signed-off-by: Jim Cromie --- drivers/gpu/drm/Kconfig | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig index 5a0c476361c3..b2ea73ae48f0 100644 --- a/drivers/gpu/drm/Kconfig +++ b/drivers/gpu/drm/Kconf

[PATCH v8 03/35] test-dyndbg: fixup CLASSMAP usage error

2024-04-30 Thread Jim Cromie
A more careful reading of logging output from test_dynamic_debug.ko reveals: lib/test_dynamic_debug.c:103 [test_dynamic_debug]do_cats =pmf "doing categories\n" lib/test_dynamic_debug.c:105 [test_dynamic_debug]do_cats =p "LOW msg\n" class:MID lib/test_dynamic_debug.c:106 [test_dynamic_debug]do_ca

[PATCH v8 21/35] dyndbg: treat comma as a token separator

2024-04-30 Thread Jim Cromie
Treat comma as a token terminator, just like a space. This allows a user to avoid quoting hassles when spaces are otherwise needed: :#> modprobe drm dyndbg=class,DRM_UT_CORE,+p\;class,DRM_UT_KMS,+p or as a boot arg: drm.dyndbg=class,DRM_UT_CORE,+p # todo: support multi-query here Given the

[PATCH v8 28/35] dyndbg-doc: explain flags parse 1st

2024-04-30 Thread Jim Cromie
When writing queries to >control, flags are parsed 1st, since they are the only required field. So if the flags draw an error, then keyword errors aren't reported. This can be mildly confusing/annoying, so explain it instead. This note could be moved up to just after the grammar id's the flags,

[PATCH v8 29/35] dyndbg: add __counted_by annotations

2024-04-30 Thread Jim Cromie
Tell the compiler about our vectors (array,length), in 2 places: h: struct _ddebug_info, which keeps refs to the __dyndbg_* ELF/DATA sections, these are all vectors with a length. c: struct ddebug_table, which has sub-refs into _ddebug_info.* Signed-off-by: Jim Cromie --- include/linux/dynamic

[PATCH v8 30/35] drm+drivers: adapt to use DYNDBG_CLASSMAP_{DEFINE, USE}

2024-04-30 Thread Jim Cromie
Follow dynamic_debug API change from DECLARE_DYNDBG_CLASSMAP to DYNDBG_CLASSMAP_{DEFINE,USE}. Prior to this, we used DECLARE_DYNDBG_CLASSMAP, which was preserved to decouple DRM conversion. I'm unsure of the full functionality in-between, a round of lkp-testing will help. Fixes: f158936b60a7 ("d

[PATCH v8 14/35] dyndbg: reduce verbose=3 messages in ddebug_add_module

2024-04-30 Thread Jim Cromie
When modprobing a module, dyndbg currently logs/says "add-module", and then "skipping" if the module has no prdbgs. Instead just check 1st and return quietly. no functional change Signed-off-by: Jim Cromie --- lib/dynamic_debug.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) di

[PATCH v8 32/35] drm: use correct ccflags-y spelling

2024-04-30 Thread Jim Cromie
Incorrectly spelled CFLAGS- failed to add -DDYNAMIC_DEBUG_MODULE, which broke builds with: CONFIG_DRM_USE_DYNAMIC_DEBUG=y CONFIG_DYNAMIC_DEBUG_CORE=y CONFIG_DYNAMIC_DEBUG=n Also add subdir-ccflags so that all drivers pick up the addition. Fixes: 84ec67288c10 ("drm_print: wrap drm_*_dbg in dyndbg

[PATCH v8 19/35] dyndbg-API: promote DYNDBG_CLASSMAP_PARAM to API

2024-04-30 Thread Jim Cromie
move the DYNDBG_CLASSMAP_PARAM macro from test-dynamic-debug.c into the header, and refine it, by distinguishing the 2 use cases: 1.DYNDBG_CLASSMAP_PARAM_REF for DRM, to pass in extern __drm_debug by name. dyndbg keeps bits in it, so drm can still use it as before 2.DYNDBG_CLASSMAP_PARAM

[PATCH v8 31/35] drm-dyndbg: adapt to use DYNDBG_CLASSMAP_PARAM

2024-04-30 Thread Jim Cromie
use new export --- drivers/gpu/drm/drm_print.c | 8 ++-- include/drm/drm_print.h | 6 -- 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/drm_print.c b/drivers/gpu/drm/drm_print.c index 4a5f2317229b..efdf82f8cbbb 100644 --- a/drivers/gpu/drm/drm_print.c ++

[PATCH v8 23/35] dyndbg: split multi-query strings with %

2024-04-30 Thread Jim Cromie
Multi-query strings have long allowed: modprobe drm dyndbg="class DRM_UT_CORE +p; class DRM_UT_KMS +p" modprobe drm dyndbg=< [ 203.902703] dyndbg: query parse failed [ 203.902871] dyndbg: processed 2 queries, with 0 matches, 2 errs bash: echo: write error: Invalid argument The '%' splits th

[PATCH v8 35/35] drm-print: workaround compiler meh

2024-04-30 Thread Jim Cromie
For some reason I cannot grok, I get an unused variable 'category' warning/error, though the usage follows immediately. This drops the local var and directly derefs in the macro-call, which somehow avoids the warning. commit 9fd6f61a297e ("drm/print: add drm_dbg_printer() for drm device specific

[PATCH v8 12/35] dyndbg: tighten ddebug_class_name() 1st arg type

2024-04-30 Thread Jim Cromie
Change function's 1st arg-type, and deref in the caller. The fn doesn't need any other fields in the struct. no functional change. Signed-off-by: Jim Cromie --- lib/dynamic_debug.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/lib/dynamic_debug.c b/lib/dynamic_d

[PATCH v8 26/35] selftests-dyndbg: add test_mod_submod

2024-04-30 Thread Jim Cromie
This new test-fn runs 3 module/submodule modprobe scenarios, variously using both the generic dyndbg= modprobe arg, and the test-module's classmap-params to manipulate the test-mod*'s pr_debugs. In all cases, the current flag-settings are counted and tested vs expectations. The 3rd scenario recapi

[PATCH v8 08/35] dyndbg: split param_set_dyndbg_classes to _module & wrapper fns

2024-04-30 Thread Jim Cromie
Split api-fn: param_set_dyndbg_classes(), adding modname param and passing NULL in from api-fn. The new arg allows caller to specify that only one module is affected by a prdbgs update. This selectivity will be used later to narrow the scope of changes made. no functional change. Signed-off-by:

[PATCH v8 01/35] dyndbg: fix old BUG_ON in >control parser

2024-04-30 Thread Jim Cromie
Fix a BUG_ON from 2009. Even if it looks "unreachable" (I didn't really look), lets make sure by removing it, doing pr_err and return -EINVAL instead. cc: sta...@vger.kernel.org Signed-off-by: Jim Cromie --- lib/dynamic_debug.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --

[PATCH v8 20/35] dyndbg-doc: add classmap info to howto

2024-04-30 Thread Jim Cromie
Describe the 3 API macros providing dynamic_debug's classmaps DYNDBG_CLASSMAP_DEFINE - create, exports a module's classmap DYNDBG_CLASSMAP_USE- refer to exported map DYNDBG_CLASSMAP_PARAM - bind control param to the classmap DYNDBG_CLASSMAP_PARAM_REF + use module's storage - __drm_debug cc:

[PATCH v8 16/35] dyndbg-API: fix DECLARE_DYNDBG_CLASSMAP

2024-04-30 Thread Jim Cromie
DECLARE_DYNDBG_CLASSMAP() has a design error; its usage fails a basic K&R rule: "define once, refer many times". It is used across DRM core & drivers, each use re-defines the classmap understood by that module; and all must match for the modules to respond together when DRM.debug categories are en

[PATCH v8 27/35] selftests-dyndbg: test dyndbg-to-tracefs

2024-04-30 Thread Jim Cromie
Add a series of trace-tests: test_actual_trace() etc, to validate that the dyndbg-to-tracefs feature (using +T flag) works as intended. The 1st test uses the global tracebuf, the rest use/excercise private tracebufs. These tests are currently optional, via "TRACE" arg1, because the feature code i

[PATCH v8 00/35] fix CONFIG_DRM_USE_DYNAMIC_DEBUG=y regression

2024-04-30 Thread Jim Cromie
hi Greg, Jason, DRM-folk, This patchset fixes the CONFIG_DRM_USE_DYNAMIC_DEBUG=y regression, Fixes: bb2ff6c27bc9 ("drm: Disable dynamic debug as broken") this is v8. Its also here: https://github.com/jimc/linux/tree/dd-classmap-fix-8a v7 had at least 2 problems: https://lore.kernel.org/lkml/20

[PATCH v8 11/35] dyndbg: silence debugs with no-change updates

2024-04-30 Thread Jim Cromie
In ddebug_apply_class_bitmap(), check for actual changes to the bits before announcing them, to declutter logs. no functional change. Signed-off-by: Jim Cromie --- lib/dynamic_debug.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/lib/dynamic_debug.c b/lib/dyna

[PATCH v8 10/35] dyndbg: reduce verbose/debug clutter

2024-04-30 Thread Jim Cromie
currently, for verbose=3, these are logged (blank lines for clarity): dyndbg: query 0: "class DRM_UT_CORE +p" mod:* dyndbg: split into words: "class" "DRM_UT_CORE" "+p" dyndbg: op='+' dyndbg: flags=0x1 dyndbg: *flagsp=0x1 *maskp=0x dyndbg: parsed: func="" file="" module="" format="

  1   2   >