[PATCH i-g-t] tests/core_setmaster: Change break to continue in tweak_perm function

2024-07-24 Thread Bommu Krishnaiah
Existing userspace assumes there's no gaps card’s, but I see cards are not continues, after running “gta@core_hotunplug I am not seeing card0, hence test is failing. Test result before this changes: root@DUT1523LNL:/usr/local/libexec/igt-gpu-tools# root@DUT1523LNL:/usr/local/libexec/igt-gpu-tools#

RE: [PATCH 13/14] drm/i915/dp_mst: Ensure link parameters are up-to-date for a disabled link

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Intel-gfx On Behalf Of Imre > Deak > Sent: Monday, July 22, 2024 10:25 PM > To: intel-gfx@lists.freedesktop.org > Subject: [PATCH 13/14] drm/i915/dp_mst: Ensure link parameters are up-to- > date for a disabled link > > As explained in the previous patch, th

RE: [PATCH 0/2] Fix null pointer error in HDCP capability check

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Kandpal, Suraj > Sent: Monday, July 22, 2024 12:15 PM > To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org > Cc: Nautiyal, Ankit K ; Kandpal, Suraj > > Subject: [PATCH 0/2] Fix null pointer error in HDCP capability check > > During suspend

RE: [PATCH 07/14] drm/i915/dp: Add a separate function to reduce the link parameters

2024-07-24 Thread Murthy, Arun R
> -Original Message- > From: Deak, Imre > Sent: Wednesday, July 24, 2024 4:50 PM > To: Murthy, Arun R > Cc: intel-gfx@lists.freedesktop.org > Subject: Re: [PATCH 07/14] drm/i915/dp: Add a separate function to reduce the > link parameters > > On Wed, Jul 24, 2024 at 07:55:03AM +0300, Murt

RE: [PATCH 06/14] drm/i915/dp: Send only a single modeset-retry uevent for a commit

2024-07-24 Thread Murthy, Arun R
> -Original Message- > From: Deak, Imre > Sent: Wednesday, July 24, 2024 4:46 PM > To: Murthy, Arun R > Cc: intel-gfx@lists.freedesktop.org > Subject: Re: [PATCH 06/14] drm/i915/dp: Send only a single modeset-retry > uevent for a commit > > On Wed, Jul 24, 2024 at 07:29:33AM +0300, Murth

RE: [PATCH] drm/i915/display: Workaround for odd panning for planar yuv

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Kandpal, Suraj > Sent: Wednesday, July 24, 2024 10:32 PM > To: Nemesa Garg ; intel...@lists.freedesktop.org > Cc: Heikkila, Juha-pekka ; Shankar, Uma > ; Garg, Nemesa > Subject: RE: [PATCH] drm/i915/display: Workaround for odd panning for > planar yuv > >

✗ Fi.CI.BAT: failure for drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll()

2024-07-24 Thread Patchwork
== Series Details == Series: drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() URL : https://patchwork.freedesktop.org/series/136455/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15126 -> Patchwork_136455v1

[PATCH] drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll()

2024-07-24 Thread Nikita Zhandarovich
On the off chance that clock value ends up being too high (by means of skl_ddi_calculate_wrpll() having benn called with big enough value of crtc_state->port_clock * 1000), one possible consequence may be that the result will not be able to fit into signed int. Fix this, albeit unlikely, issue by

Re: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces

2024-07-24 Thread Imre Deak
On Wed, Jul 24, 2024 at 07:03:51PM +0300, Jani Nikula wrote: > [...] > Imre, I'm looking at the warnings in intel_tc.c in general, and > adlp_tc_phy_connect() in particular, and I think this is too hard to > parse: > > if (!adlp_tc_phy_take_ownership(tc, true) && > !drm_WARN_ON(&i9

Re: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces

2024-07-24 Thread Imre Deak
On Mon, Jul 15, 2024 at 08:35:43PM +0200, Francesco Poli wrote: > Hi all, > on a laptop where I installed Debian testing some 6 months ago, > I noticed that the logs are continuously flooded with call traces > like the attached snippet (taken from /var/log/kern.log ). > > It seems to me that it al

RE: [PATCH 3/3] drm/xe/hdcp: Check GSC structure validity

2024-07-24 Thread Bhadane, Dnyaneshwar
> -Original Message- > From: Intel-xe On Behalf Of Suraj > Kandpal > Sent: Monday, July 22, 2024 12:15 PM > To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org > Cc: Nautiyal, Ankit K ; Kandpal, Suraj > > Subject: [PATCH 3/3] drm/xe/hdcp: Check GSC structure validity >

RE: [PATCH 2/3] drm/i915/hdcp: Add encoder check in hdcp2_get_capability

2024-07-24 Thread Bhadane, Dnyaneshwar
> -Original Message- > From: Intel-gfx On Behalf Of Suraj > Kandpal > Sent: Monday, July 22, 2024 12:15 PM > To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org > Cc: Nautiyal, Ankit K ; Kandpal, Suraj > > Subject: [PATCH 2/3] drm/i915/hdcp: Add encoder check in > hdcp2

RE: [PATCH 1/3] drm/i915/hdcp: Add encoder check in intel_hdcp_get_capability

2024-07-24 Thread Bhadane, Dnyaneshwar
> -Original Message- > From: Intel-xe On Behalf Of Suraj > Kandpal > Sent: Monday, July 22, 2024 12:15 PM > To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org > Cc: Nautiyal, Ankit K ; Kandpal, Suraj > > Subject: [PATCH 1/3] drm/i915/hdcp: Add encoder check in > intel_

✗ Fi.CI.BAT: failure for drm/i915/dp: Clear VSC SDP during post ddi disable routine (rev2)

2024-07-24 Thread Patchwork
== Series Details == Series: drm/i915/dp: Clear VSC SDP during post ddi disable routine (rev2) URL : https://patchwork.freedesktop.org/series/136369/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15125 -> Patchwork_136369v2

[PATCH i-g-t] tests/xe_gt_freq: Avoid RPe usage in subtests

2024-07-24 Thread Vinay Belgaumkar
We are seeing several instances where the RPe, which can be altered by pcode dynamically, is causing subtests to fail randomly. Instead of relying on it, we can use a mid frequency value for these subtests and avoid these failures. Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2262 L

✗ Fi.CI.BAT: failure for drm/i915/dp_mst: Fix MST state after a sink reset

2024-07-24 Thread Patchwork
== Series Details == Series: drm/i915/dp_mst: Fix MST state after a sink reset URL : https://patchwork.freedesktop.org/series/136443/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15124 -> Patchwork_136443v1 Summary ---

RE: [PATCH 09/14] drm/i915/dp_mst: Reduce the link parameters in BW order after LT failures

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Deak, Imre > Sent: Wednesday, July 24, 2024 4:57 PM > To: Kandpal, Suraj > Cc: intel-gfx@lists.freedesktop.org > Subject: Re: [PATCH 09/14] drm/i915/dp_mst: Reduce the link parameters in > BW order after LT failures > > On Wed, Jul 24, 2024 at 09:43:55AM +

RE: [PATCH 14/14] drm/i915/dp_mst: Enable LT fallback between UHBR/non-UHBR link rates

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Deak, Imre > Sent: Wednesday, July 24, 2024 5:03 PM > To: Kandpal, Suraj > Cc: intel-gfx@lists.freedesktop.org > Subject: Re: [PATCH 14/14] drm/i915/dp_mst: Enable LT fallback between > UHBR/non-UHBR link rates > > On Wed, Jul 24, 2024 at 11:52:14AM +0300,

[PATCH] drm/i915/dp: Clear VSC SDP during post ddi disable routine

2024-07-24 Thread Suraj Kandpal
Clear VSC SDP if intel_dp_set_infoframes is called from post ddi disable routine i.e with the variable of enable as false. This is to avoid an infoframes.enable mismatch issue which is caused when pipe is connected to eDp which has psr then connected to DPMST. In this case eDp's post ddi disable ro

Re: [PATCH] drm/i915/dp_mst: Fix MST state after a sink reset

2024-07-24 Thread Imre Deak
On Wed, Jul 24, 2024 at 07:21:53PM +0300, Jani Nikula wrote: > On Wed, 24 Jul 2024, Imre Deak wrote: > > In some cases the sink can reset itself after it was configured into MST > > mode, without the driver noticing the disconnected state. For instance > > the reset may happen in the middle of a m

Re: [PATCH] drm/i915/dp_mst: Fix MST state after a sink reset

2024-07-24 Thread Jani Nikula
On Wed, 24 Jul 2024, Imre Deak wrote: > In some cases the sink can reset itself after it was configured into MST > mode, without the driver noticing the disconnected state. For instance > the reset may happen in the middle of a modeset, or the (long) HPD pulse > generated may be not long enough fo

Re: [PATCH 1/7] perf/core: Add pmu get/put

2024-07-24 Thread Ian Rogers
On Mon, Jul 22, 2024 at 2:07 PM Lucas De Marchi wrote: > > If a pmu is unregistered while there's an active event, perf will still > access the pmu via event->pmu, even after the event is destroyed. This > makes it difficult for drivers like i915 that take a reference on the > device when the even

[PATCH] drm/i915/dp_mst: Fix MST state after a sink reset

2024-07-24 Thread Imre Deak
In some cases the sink can reset itself after it was configured into MST mode, without the driver noticing the disconnected state. For instance the reset may happen in the middle of a modeset, or the (long) HPD pulse generated may be not long enough for the encoder detect handler to observe the HPD

Re: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces

2024-07-24 Thread Jani Nikula
On Mon, 15 Jul 2024, Francesco Poli wrote: > Hi all, > on a laptop where I installed Debian testing some 6 months ago, > I noticed that the logs are continuously flooded with call traces > like the attached snippet (taken from /var/log/kern.log ). > > It seems to me that it also used to happen wit

Re: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces

2024-07-24 Thread Jani Nikula
On Mon, 15 Jul 2024, Francesco Poli wrote: > Hi all, > on a laptop where I installed Debian testing some 6 months ago, > I noticed that the logs are continuously flooded with call traces > like the attached snippet (taken from /var/log/kern.log ). > > It seems to me that it also used to happen wit

✗ Fi.CI.IGT: failure for drm/i915/display: Workaround for odd panning for planar yuv

2024-07-24 Thread Patchwork
== Series Details == Series: drm/i915/display: Workaround for odd panning for planar yuv URL : https://patchwork.freedesktop.org/series/136416/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15123_full -> Patchwork_136416v1_full =

Re: [PATCH 6/7] drm/i915/pmu: Lazy unregister

2024-07-24 Thread Lucas De Marchi
On Wed, Jul 24, 2024 at 02:41:05PM GMT, Peter Zijlstra wrote: On Tue, Jul 23, 2024 at 10:30:08AM -0500, Lucas De Marchi wrote: On Tue, Jul 23, 2024 at 09:03:25AM GMT, Tvrtko Ursulin wrote: > > On 22/07/2024 22:06, Lucas De Marchi wrote: > > Instead of calling perf_pmu_unregister() when unbinding

✗ Fi.CI.BAT: failure for drm/i915/gt: Stop poisoning the idle kernel context alone when waking up

2024-07-24 Thread Patchwork
== Series Details == Series: drm/i915/gt: Stop poisoning the idle kernel context alone when waking up URL : https://patchwork.freedesktop.org/series/136433/ State : failure == Summary == CI Bug Log - changes from CI_DRM_15124 -> Patchwork_136433v1 ==

Re: [PATCH] drm/i915/dp: Clear VSC SDP during post ddi disable routine

2024-07-24 Thread Jani Nikula
On Wed, 24 Jul 2024, "Nautiyal, Ankit K" wrote: > On 7/23/2024 9:58 AM, Suraj Kandpal wrote: >> Clear VSC SDP if intel_dp_set_infoframes is called from post ddi disable >> routine i.e with the variable of enable as false. This is to avoid >> an infoframes.enable mismatch issue which is caused when

✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Stop poisoning the idle kernel context alone when waking up

2024-07-24 Thread Patchwork
== Series Details == Series: drm/i915/gt: Stop poisoning the idle kernel context alone when waking up URL : https://patchwork.freedesktop.org/series/136433/ State : warning == Summary == Error: dim checkpatch failed 30c921464da6 drm/i915/gt: Stop poisoning the idle kernel context alone when w

Re: [PATCH v7 1/2] drm/buddy: Add start address support to trim function

2024-07-24 Thread Jani Nikula
On Tue, 23 Jul 2024, Arunpravin Paneer Selvam wrote: > - Add a new start parameter in trim function to specify exact > address from where to start the trimming. This would help us > in situations like if drivers would like to do address alignment > for specific requirements. > > - Add a new

✗ Fi.CI.BUILD: failure for spi: add driver for Intel discrete graphics (rev2)

2024-07-24 Thread Patchwork
== Series Details == Series: spi: add driver for Intel discrete graphics (rev2) URL : https://patchwork.freedesktop.org/series/131763/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/131763/revisions/2/mbox/ not applied Applying: spi: add driver fo

[PATCH] drm/i915/gt: Stop poisoning the idle kernel context alone when waking up

2024-07-24 Thread Krzysztof Niemiec
From: Chris Wilson The kernel context was poisoned on wakeup to simulate how the driver would cope with bad HW that caused corruption of any context that was still resident during power loss, see commit 1d0e2c9359fe ("drm/i915/gt: Always poison the kernel_context image before unparking"). However

[PATCH v2 11/12] drm/xe/spi: add on-die spi device

2024-07-24 Thread Alexander Usyskin
Enable access to internal spi on DGFX with GSC/CSC devices via a child device. The spi child device is exposed via auxiliary bus. Signed-off-by: Alexander Usyskin --- drivers/gpu/drm/xe/Makefile | 1 + drivers/gpu/drm/xe/xe_device.c | 3 ++ drivers/gpu/drm/xe/xe_device_types.h |

[PATCH v2 09/12] drm/i915/spi: add intel_spi_region map

2024-07-24 Thread Alexander Usyskin
From: Tomas Winkler Add the dGFX spi region map and convey it via auxiliary device to the spi child device. CC: Rodrigo Vivi CC: Lucas De Marchi Signed-off-by: Tomas Winkler Signed-off-by: Alexander Usyskin --- drivers/gpu/drm/i915/spi/intel_spi.c | 8 1 file changed, 8 insertions(

[PATCH v2 05/12] spi: intel-dg: implement mtd access handlers

2024-07-24 Thread Alexander Usyskin
From: Tomas Winkler Implement mtd read, erase, and write handlers. For erase operation address and size should be 4K aligned. For write operation address and size has to be 4bytes aligned. CC: Rodrigo Vivi CC: Lucas De Marchi Signed-off-by: Tomas Winkler Signed-off-by: Vitaly Lubart Signed-o

[PATCH v2 12/12] drm/xe/spi: add support for access mode

2024-07-24 Thread Alexander Usyskin
Check SPI access mode from GSC FW status registers and overwrite access status read from SPI descriptor, if needed. Signed-off-by: Alexander Usyskin --- drivers/gpu/drm/xe/regs/xe_gsc_regs.h | 5 drivers/gpu/drm/xe/xe_heci_gsc.c | 5 +--- drivers/gpu/drm/xe/xe_spi.c | 33 ++

[PATCH v2 08/12] drm/i915/spi: add spi device for discrete graphics

2024-07-24 Thread Alexander Usyskin
From: Tomas Winkler Enable access to internal spi on DGFX devices via a child device. The spi child device is exposed via auxiliary bus. CC: Rodrigo Vivi CC: Lucas De Marchi Signed-off-by: Tomas Winkler Signed-off-by: Alexander Usyskin --- drivers/gpu/drm/i915/Makefile| 4 ++ drive

[PATCH v2 10/12] drm/i915/spi: add support for access mode

2024-07-24 Thread Alexander Usyskin
Check SPI access mode from GSC FW status registers and overwrite access status read from SPI descriptor, if needed. Signed-off-by: Alexander Usyskin --- drivers/gpu/drm/i915/spi/intel_spi.c | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/gpu/drm/i915/spi/in

[PATCH v2 06/12] spi: intel-dg: align 64bit read and write

2024-07-24 Thread Alexander Usyskin
GSC SPI HW errors on quad access overlapping 1K border. Align 64bit read and write to avoid readq/writeq over 1K border. Signed-off-by: Alexander Usyskin --- drivers/spi/spi-intel-dg.c | 35 +++ 1 file changed, 35 insertions(+) diff --git a/drivers/spi/spi-intel-

[PATCH v2 07/12] spi: intel-dg: wake card on operations

2024-07-24 Thread Alexander Usyskin
Enable runtime PM in spi driver to notify graphics driver that whole card should be kept awake while spi operations are performed through this driver. CC: Lucas De Marchi Signed-off-by: Alexander Usyskin --- drivers/spi/spi-intel-dg.c | 44 ++ 1 file changed,

[PATCH v2 04/12] spi: intel-dg: spi register with mtd

2024-07-24 Thread Alexander Usyskin
From: Tomas Winkler Register the on-die spi device with the mtd subsystem. Refcount spi object on _get and _put mtd callbacks. CC: Rodrigo Vivi CC: Lucas De Marchi Signed-off-by: Tomas Winkler Signed-off-by: Alexander Usyskin --- drivers/spi/spi-intel-dg.c | 111

[PATCH v2 03/12] spi: intel-dg: implement spi access functions

2024-07-24 Thread Alexander Usyskin
From: Tomas Winkler Implement spi_read(), spi_erase() and spi_write() functions. CC: Lucas De Marchi CC: Rodrigo Vivi Signed-off-by: Tomas Winkler Signed-off-by: Vitaly Lubart Signed-off-by: Alexander Usyskin --- drivers/spi/spi-intel-dg.c | 199 + 1 fil

[PATCH v2 02/12] spi: intel-dg: implement region enumeration

2024-07-24 Thread Alexander Usyskin
From: Tomas Winkler In intel-dg spi, there is no access to the spi controller, the information is extracted from the descriptor region. CC: Rodrigo Vivi CC: Lucas De Marchi Signed-off-by: Tomas Winkler Signed-off-by: Alexander Usyskin --- drivers/spi/spi-intel-dg.c | 190 +++

[PATCH v2 01/12] spi: add driver for intel graphics on-die spi device

2024-07-24 Thread Alexander Usyskin
Add auxiliary driver for intel discrete graphics on-die spi device. CC: Rodrigo Vivi CC: Lucas De Marchi Signed-off-by: Tomas Winkler Signed-off-by: Alexander Usyskin --- MAINTAINERS | 7 ++ drivers/spi/Kconfig | 11 +++ drivers/spi/Makefile |

[PATCH v2 00/12] spi: add driver for Intel discrete graphics

2024-07-24 Thread Alexander Usyskin
Add driver for access to Intel discrete graphics card internal SPI device. Expose device on auxiliary bus by i915 and Xe drivers and provide spi driver to register this device with MTD framework. This is a rewrite of "drm/i915/spi: spi access for discrete graphics" series with connection to the Xe

Re: [PATCH 6/7] drm/i915/pmu: Lazy unregister

2024-07-24 Thread Peter Zijlstra
On Tue, Jul 23, 2024 at 10:30:08AM -0500, Lucas De Marchi wrote: > On Tue, Jul 23, 2024 at 09:03:25AM GMT, Tvrtko Ursulin wrote: > > > > On 22/07/2024 22:06, Lucas De Marchi wrote: > > > Instead of calling perf_pmu_unregister() when unbinding, defer that to > > > the destruction of i915 object. Si

✓ Fi.CI.BAT: success for drm/i915/display: Workaround for odd panning for planar yuv

2024-07-24 Thread Patchwork
== Series Details == Series: drm/i915/display: Workaround for odd panning for planar yuv URL : https://patchwork.freedesktop.org/series/136416/ State : success == Summary == CI Bug Log - changes from CI_DRM_15123 -> Patchwork_136416v1 Summa

Re: [PATCH 14/14] drm/i915/dp_mst: Enable LT fallback between UHBR/non-UHBR link rates

2024-07-24 Thread Imre Deak
On Wed, Jul 24, 2024 at 11:52:14AM +0300, Kandpal, Suraj wrote: > > > > -Original Message- > > From: Intel-gfx On Behalf Of Imre > > Deak > > Sent: Monday, July 22, 2024 10:25 PM > > To: intel-gfx@lists.freedesktop.org > > Subject: [PATCH 14/14] drm/i915/dp_mst: Enable LT fallback betwee

[PATCH] drm/i915/display: Workaround for odd panning for planar yuv

2024-07-24 Thread Nemesa Garg
Underrun/corruption issue is seen for NV12 format for odd panning on LNL due to hardware bug. Disable the format. HSD: 16024459452 Signed-off-by: Nemesa Garg --- drivers/gpu/drm/i915/display/intel_atomic_plane.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/gpu/drm/i915/di

Re: [PATCH 09/14] drm/i915/dp_mst: Reduce the link parameters in BW order after LT failures

2024-07-24 Thread Imre Deak
On Wed, Jul 24, 2024 at 09:43:55AM +0300, Kandpal, Suraj wrote: > > > > -Original Message- > > From: Intel-gfx On Behalf Of Imre > > Deak > > Sent: Monday, July 22, 2024 10:25 PM > > To: intel-gfx@lists.freedesktop.org > > Subject: [PATCH 09/14] drm/i915/dp_mst: Reduce the link parameter

Re: [PATCH v7 1/2] drm/buddy: Add start address support to trim function

2024-07-24 Thread Christian König
Am 24.07.24 um 11:37 schrieb Matthew Auld: On 24/07/2024 02:35, Marek Olšák wrote: The reason is that our DCC requires 768K alignment in some cases. I haven't read this patch series, but one way to do that is to align to 256K, overallocate by 512K, and then not use either 0, 256K, or 512K at t

Re: [PATCH 07/14] drm/i915/dp: Add a separate function to reduce the link parameters

2024-07-24 Thread Imre Deak
On Wed, Jul 24, 2024 at 07:55:03AM +0300, Murthy, Arun R wrote: > > -Original Message- > > From: Intel-gfx On Behalf Of Imre > > Deak > > Sent: Monday, July 22, 2024 10:25 PM > > To: intel-gfx@lists.freedesktop.org > > Subject: [PATCH 07/14] drm/i915/dp: Add a separate function to reduce t

Re: [PATCH 06/14] drm/i915/dp: Send only a single modeset-retry uevent for a commit

2024-07-24 Thread Imre Deak
On Wed, Jul 24, 2024 at 07:29:33AM +0300, Murthy, Arun R wrote: > > > -Original Message- > > From: Intel-gfx On Behalf Of Imre > > Deak > > Sent: Monday, July 22, 2024 10:25 PM > > To: intel-gfx@lists.freedesktop.org > > Subject: [PATCH 06/14] drm/i915/dp: Send only a single modeset-retry

Re: [PATCH][next] drm/i915/dp: Make read-only array bw_gbps static const

2024-07-24 Thread Jani Nikula
On Mon, 22 Jul 2024, Colin Ian King wrote: > Don't populate the read-only array bw_gbps on the stack at run time, > instead make it static const. > > Signed-off-by: Colin Ian King Pushed to drm-intel-next, thanks for the patch. BR, Jani. > --- > drivers/gpu/drm/i915/display/intel_dp.c | 2 +-

Re: [PATCH v7 1/2] drm/buddy: Add start address support to trim function

2024-07-24 Thread Matthew Auld
On 23/07/2024 14:25, Arunpravin Paneer Selvam wrote: - Add a new start parameter in trim function to specify exact address from where to start the trimming. This would help us in situations like if drivers would like to do address alignment for specific requirements. - Add a new flag DR

Re: [PATCH v7 1/2] drm/buddy: Add start address support to trim function

2024-07-24 Thread Matthew Auld
On 24/07/2024 02:35, Marek Olšák wrote: The reason is that our DCC requires 768K alignment in some cases. I haven't read this patch series, but one way to do that is to align to 256K, overallocate by 512K, and then not use either 0, 256K, or 512K at the beginning to get to 768K alignment. Ah,

RE: [PATCH 14/14] drm/i915/dp_mst: Enable LT fallback between UHBR/non-UHBR link rates

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Intel-gfx On Behalf Of Imre > Deak > Sent: Monday, July 22, 2024 10:25 PM > To: intel-gfx@lists.freedesktop.org > Subject: [PATCH 14/14] drm/i915/dp_mst: Enable LT fallback between > UHBR/non-UHBR link rates > > Enable switching between UHBR and non-UHBR li

RE: [PATCH 12/14] drm/i915/dp_mst: Reprobe the MST topology after a link parameter change

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Intel-gfx On Behalf Of Imre > Deak > Sent: Monday, July 22, 2024 10:25 PM > To: intel-gfx@lists.freedesktop.org > Subject: [PATCH 12/14] drm/i915/dp_mst: Reprobe the MST topology after a > link parameter change > > The MST link BW reported by branch devices

Re: [PATCH v1] drm/i915/hwmon: expose fan speed

2024-07-24 Thread Nilawar, Badal
On 12-07-2024 17:53, Raag Jadav wrote: Add hwmon support for fan1_input attribute, which will expose fan speed in RPM. With this in place we can monitor fan speed using lm-sensors tool. $ sensors i915-pci-0300 Adapter: PCI adapter in0: 653.00 mV fan1:3833 RPM power1:

RE: [PATCH 11/14] drm/i915/dp_mst: Queue modeset-retry after a failed payload BW allocation

2024-07-24 Thread Kandpal, Suraj
> -Original Message- > From: Intel-gfx On Behalf Of Imre > Deak > Sent: Monday, July 22, 2024 10:25 PM > To: intel-gfx@lists.freedesktop.org > Subject: [PATCH 11/14] drm/i915/dp_mst: Queue modeset-retry after a > failed payload BW allocation > > If the MST payload allocation failed, en

Re: [PATCH 6/7] drm/i915/pmu: Lazy unregister

2024-07-24 Thread Tvrtko Ursulin
On 23/07/2024 16:30, Lucas De Marchi wrote: On Tue, Jul 23, 2024 at 09:03:25AM GMT, Tvrtko Ursulin wrote: On 22/07/2024 22:06, Lucas De Marchi wrote: Instead of calling perf_pmu_unregister() when unbinding, defer that to the destruction of i915 object. Since perf itself holds a reference in