This reverts commit 560af5dc839eef08a273908f390cfefefb82aa04.
Signed-off-by: Luca Coelho
---
lib/Kconfig.debug | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index f3d723705879..de4ffe09323b 100644
--- a/lib/Kconfig.debug
+
This series implements Wa_14022698537 for DG2 along with its prerequisites
in i915. Detailed description in commit message.
v1: https://patchwork.freedesktop.org/series/139628/
v2: Introduce DG2_WA subplatform for workaround (Jani)
Fix Wa_ID and include it in subject (Badal)
Rephrase comm
Thanks for review!
> > --- a/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > @@ -793,7 +793,7 @@ int intel_dp_tunnel_mgr_init(struct intel_display
> > *display)
> > drm_connector_list_iter_end(&connector_list_iter);
> >
> > tun
Thanks for review!
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > b/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > index 94198bc04939..6c960416f776 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> >
Refactor DG2 PCI IDs into D, E and M ranges which will be useful for
segment specific features.
v3: Rework subplatform naming (Jani)
Signed-off-by: Raag Jadav
Acked-by: Jani Nikula
Reviewed-by: Riana Tauro
Reviewed-by: Andi Shyti
---
include/drm/intel/pciids.h | 55 ++
== Series Details ==
Series: Implement Wa_14022698537 (rev3)
URL : https://patchwork.freedesktop.org/series/139883/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: Implement Wa_14022698537 (rev3)
URL : https://patchwork.freedesktop.org/series/139883/
State : warning
== Summary ==
Error: dim checkpatch failed
ba38e573b559 drm/intel/pciids: Refactor DG2 PCI IDs into segment ranges
-:28: ERROR:COMPLEX_MACRO: Macros with complex
Add g4x_dp_compute_config() instead of using intel_dp_compute_config()
directly, in order to slightly reduce the clutter in the latter wrt
->has_pch_encoder.
Cc: Ville Syrjala
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/g4x_dp.c | 14 +-
drivers/gpu/drm/i915/displa
It does not look like anything in intel_dp_compute_config() after the
g4x_dp_set_clock() call depends on the changes it makes, namely setting
dpll and clock_set in crtc_state. Move the call one level higher to
g4x_dp_compute_config() to reduce the clutter in
intel_dp_compute_config().
Cc: Ville Sy
== Series Details ==
Series: Implement Wa_14022698537 (rev3)
URL : https://patchwork.freedesktop.org/series/139883/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15819 -> Patchwork_139883v3
Summary
---
**SUCCESS**
On Wed, Dec 11, 2024 at 09:56:50AM +, Krzysztof Karas wrote:
> drm_dp_tunnel_mgr_create() may return NULL on failure, which will not
> be caught via IS_ERR(), so replace it with IS_ERR_OR_NULL() macro.
>
> Signed-off-by: Krzysztof Karas
> ---
> drivers/gpu/drm/i915/display/intel_dp_tunnel.c
== Series Details ==
Series: Revert "lockdep: Enable PROVE_RAW_LOCK_NESTING with PROVE_LOCKING."
(rev2)
URL : https://patchwork.freedesktop.org/series/142298/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15819 -> Patchwork_142298v2
===
On Wed, Dec 11, 2024 at 02:54:31PM +0200, Jani Nikula wrote:
> It does not look like anything in intel_dp_compute_config() after the
> g4x_dp_set_clock() call depends on the changes it makes, namely setting
> dpll and clock_set in crtc_state.
Hmm, yeah I was a bit worried about DRRS and such, but
== Series Details ==
Series: series starting with [1/2] drm/i915/dp: add g4x_dp_compute_config()
URL : https://patchwork.freedesktop.org/series/142411/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15819 -> Patchwork_142411v1
===
== Series Details ==
Series: Implement Wa_14022698537 (rev3)
URL : https://patchwork.freedesktop.org/series/139883/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15819_full -> Patchwork_139883v3_full
Summary
---
**FA
Uprev IGT to the latest version and update expectation files.
Signed-off-by: Vignesh Raman
---
v1:
- Pipeline link -
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1327810
Will update the flake bug report link after v1 is reviewed.
---
drivers/gpu/drm/ci/gitlab-ci.yml
On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
> +/**
> + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode
> + * @aux: DisplayPort AUX channel
> + * @enable: Enable or disable transparent mode
> + *
> + * Returns 0 on success or a negative error code on failure.
There's a lot of duplication between mst_stream_compute_config_limits()
and intel_dp_compute_config_limits(). Adjust the latter to suit the
needs of the former, and use the same function for both. This reduces
duplication and highlights the differences for SST and MST and UHBR.
Remove the kernel-d
Instead of returning a generic NULL on error from drm_dp_tunnel_mgr_create(),
use error pointers with informative codes. This will also trigger IS_ERR() in
current caller (intel_dp_tunnerl_mgr_init()) instead of bypassing it via NULL
pointer.
v2: use error codes inside drm_dp_tunnel_mgr_create() i
On Wed, Dec 11, 2024 at 03:04:15PM +0200, Abel Vesa wrote:
> +static void msm_dp_display_lttpr_init(struct msm_dp_display_private *dp)
> +{
> + int lttpr_count;
> +
> + if (drm_dp_read_lttpr_common_caps(dp->aux, dp->panel->dpcd,
> + dp->lttpr_caps))
>
Hi Krzysztof,
On Wed, Dec 11, 2024 at 02:52:20PM +, Krzysztof Karas wrote:
> Instead of returning a generic NULL on error from drm_dp_tunnel_mgr_create(),
> use error pointers with informative codes. This will also trigger IS_ERR() in
> current caller (intel_dp_tunnerl_mgr_init()) instead of b
On Wed, Dec 11, 2024 at 04:18:06PM +0100, Andi Shyti wrote:
> Hi Krzysztof,
>
> On Wed, Dec 11, 2024 at 02:52:20PM +, Krzysztof Karas wrote:
> > Instead of returning a generic NULL on error from
> > drm_dp_tunnel_mgr_create(),
> > use error pointers with informative codes. This will also trig
== Series Details ==
Series: drm/ci: uprev IGT (rev2)
URL : https://patchwork.freedesktop.org/series/135749/
State : warning
== Summary ==
Error: dim checkpatch failed
954d51ca75ac drm/ci: uprev IGT
-:858: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does
MAINTAINERS need updat
== Series Details ==
Series: series starting with [1/2] drm/i915/dp: add g4x_dp_compute_config()
URL : https://patchwork.freedesktop.org/series/142411/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15819_full -> Patchwork_142411v1_full
=
== Series Details ==
Series: drm/display: use ERR_PTR on DP tunnel manager creation fail
URL : https://patchwork.freedesktop.org/series/142423/
State : warning
== Summary ==
Error: dim checkpatch failed
aa96e1997901 drm/display: use ERR_PTR on DP tunnel manager creation fail
-:6: WARNING:COMMI
== Series Details ==
Series: drm/i915/mst: use intel_dp_compute_config_limits() for DP MST
URL : https://patchwork.freedesktop.org/series/142422/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15821 -> Patchwork_142422v1
Sum
== Series Details ==
Series: drm/ci: uprev IGT (rev2)
URL : https://patchwork.freedesktop.org/series/135749/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15821 -> Patchwork_135749v2
Summary
---
**SUCCESS**
No reg
Hi Vignesh,
thanks for the patch.
On Wed, 11 Dec 2024 11:28:05 -0300 Vignesh Raman wrote ---
> Uprev IGT to the latest version and update expectation files.
>
> Signed-off-by: Vignesh Raman vignesh.ra...@collabora.com>
> ---
>
> v1:
> - Pipeline link -
> https://gitlab.
== Series Details ==
Series: drm/display: use ERR_PTR on DP tunnel manager creation fail
URL : https://patchwork.freedesktop.org/series/142423/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15821 -> Patchwork_142423v1
Summa
On Wed, Dec 11, 2024 at 02:16:35PM +0200, Luca Coelho wrote:
This reverts commit 560af5dc839eef08a273908f390cfefefb82aa04.
Signed-off-by: Luca Coelho
I added some more context to the commit message and
pushed to topic/core-for-CI with Rodrigo's ack:
81827bbe1d8b ("Revert "lockdep: Enable
On Wed, Dec 04, 2024 at 01:17:17PM +0200, Raag Jadav wrote:
> + misc maintainers
>
> On Tue, Dec 03, 2024 at 11:18:00AM +0100, Christian König wrote:
> > Am 03.12.24 um 06:00 schrieb Raag Jadav:
> > > On Mon, Dec 02, 2024 at 10:07:59AM +0200, Raag Jadav wrote:
> > > > On Fri, Nov 29, 2024 at 10:40
On Wed, Dec 11, 2024 at 03:42:27PM +0100, Johan Hovold wrote:
> On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
>
> > +/**
> > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode
> > + * @aux: DisplayPort AUX channel
> > + * @enable: Enable or disable transparent
On Wed, Dec 11, 2024 at 07:58:05PM +0530, Vignesh Raman wrote:
> Uprev IGT to the latest version and update expectation files.
>
> Signed-off-by: Vignesh Raman
> ---
>
> v1:
> - Pipeline link -
> https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1327810
> Will update the flake
== Series Details ==
Series: drm/display: use ERR_PTR on DP tunnel manager creation fail
URL : https://patchwork.freedesktop.org/series/142423/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15821_full -> Patchwork_142423v1_full
=
Hey Jani,
I believe at least for the platforms xe cares about (gen12+), display is
sufficiently separated that everything can be performed in a single init
call before we enable interrupts.
Because of the strict separation between xe and display, it should be
fine to keep the ordering as-is
On Wed, Dec 11, 2024 at 03:42:27PM +0100, Johan Hovold wrote:
> On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
>
> > +/**
> > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode
> > + * @aux: DisplayPort AUX channel
> > + * @enable: Enable or disable transparent
== Series Details ==
Series: drm/xe/display: Program double buffered LUT registers
URL : https://patchwork.freedesktop.org/series/142437/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15825 -> Patchwork_142437v1
Summary
---
Hi Dave and Sima,
Here goes our first drm-intel-next round targeting 6.14.
One drm/print change coming from here. The rest is mostly
display changes and one GSC FW update for ARL platforms.
Thanks,
Rodrigo.
drm-intel-next-2024-12-11:
Core Changes:
- drm/print: add drm_print_hex_dump()
Driver
On Wed, 11 Dec 2024, Ville Syrjälä wrote:
> On Wed, Dec 11, 2024 at 02:54:31PM +0200, Jani Nikula wrote:
>> It does not look like anything in intel_dp_compute_config() after the
>> g4x_dp_set_clock() call depends on the changes it makes, namely setting
>> dpll and clock_set in crtc_state.
>
> Hmm,
Introduce DG2_D subplatform for the devices that span across multiple
DG2 subplatforms but are within same segment and will be useful for
segment specific features.
v3: Rework subplatform naming (Jani)
Split subplatform check into separate case (Jani)
Signed-off-by: Raag Jadav
Acked-by: Jani
== Series Details ==
Series: drm/i915/display: use IS_ERR_OR_NULL macro on DP tunnel mgr creation
failure
URL : https://patchwork.freedesktop.org/series/142404/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15819 -> Patchwork_142404v1
=
Having similar naming convention in intel-family.h and intel_device_info.h
results in redefinition of a few platforms. Define CPU IDs in its own file
to avoid this.
v3: Move file out of gt directory, add kernel doc (Riana)
Rephrase file description (Jani)
Signed-off-by: Raag Jadav
Acked-by:
== Series Details ==
Series: drm/ci: uprev IGT (rev2)
URL : https://patchwork.freedesktop.org/series/135749/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15821_full -> Patchwork_135749v2_full
Summary
---
**FAILURE**
== Series Details ==
Series: drm/i915/mst: use intel_dp_compute_config_limits() for DP MST
URL : https://patchwork.freedesktop.org/series/142422/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15821_full -> Patchwork_142422v1_full
===
G8 power state entry is disabled due to a limitation on DG2, so we
enable it from driver with Wa_14022698537. For now we enable it for
all DG2 devices with the exception of a few, for which, we enable
only when paired with whitelisted CPU models. This works with native
ASPM and reduces idle power c
Hi Dave, Sima,
A handful of fixes for the weekly release candidate cycle:
One fix for a performance regression in DSB register programming and also
in the same area a partial fix for the legacy LUT and DSB interaction.
Then there is a fix for a null pointer dereference in the GuC error state
ca
>From PTL, LUT registers are made double buffered. This helps us
to program them in the active region without any concern of tearing.
This particulary helps in case of displays with high refresh rates
where vblank periods are shorter.
This patch tries to incorporates LUT programming to the noarm c
On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote:
> According to the DisplayPort standard, LTTPRs have two operating
> modes:
> - non-transparent - it replies to DPCD LTTPR field specific AUX
>requests, while passes through all other AUX requests
> - transparent - it passes through a
Hi Krzysztof,
On Wed, Dec 11, 2024 at 02:52:20PM +, Krzysztof Karas wrote:
> Instead of returning a generic NULL on error from drm_dp_tunnel_mgr_create(),
> use error pointers with informative codes. This will also trigger IS_ERR() in
> current caller (intel_dp_tunnerl_mgr_init()) instead of b
After an error during adding an MST connector the MST port and the
intel_connector object could be leaked, fix this up.
Reviewed-by: Rodrigo Vivi
Signed-off-by: Imre Deak
---
drivers/gpu/drm/i915/display/intel_dp_mst.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
dif
All the drivers should be converted now to use
drm_connector_dynamic_init() for MST connectors, hence
drm_connector_dynamic_register()->drm_connector_add() can WARN now if
this was not the case (for instance if a driver inited an MST connector
with one of the drm_connector_init*() functions incorre
Follow the canonical way in intel_dp_mst.c, referencing a connector only
via a struct intel_connector pointer and naming this pointer 'connector'
instead of 'intel_connector', the only exception being the casting of
a drm_connector function parameter pointer to intel_connector, calling
the drm_conn
After a connector is added to the drm_mode_config::connector_list, it's
visible to any in-kernel users looking up connectors via the above list.
Make sure that the connector is properly initialized before such
look-ups, by initializing the connector with
drm_connector_dynamic_register() - which doe
Add kunit tests for
drm_connector_dynamic_init()/drm_connector_dynamic_register() added in
this patchset.
Suggested-by: Maxime Ripard
Signed-off-by: Imre Deak
---
drivers/gpu/drm/tests/drm_connector_test.c | 463 +
1 file changed, 463 insertions(+)
diff --git a/drivers/gpu/
Drivers should register/unregister only dynamic (MST) connectors
manually using drm_connector_dynamic_register()/unregister().
Static connectors are registered/unregistered by the DRM core
automatically. Some drivers still call drm_connector_register()/
unregister() for static connectors, both of w
This is v3 of [1], with the following changes:
- Instead of the drm_connector_init_core()/drm_connector_add() add
a drm_connector_dynamic_init()/drm_connector_dynamic_register()
interface. Adding the connector to the connector list is now part of
the registration step done by the latter func
Atm when the connector is added to the drm_mode_config::connector_list,
the connector may not be fully initialized yet. This is not a problem
for static connectors initialized/added during driver loading, for which
the driver ensures that look-ups via the above list are not possible
until all the c
MST connectors should be initialized/registered by calling
drm_connector_dynamic_init()/drm_connector_dynamic_register(). The
previous patch adding these functions explains the issue with the
current drm_connector_init*()/drm_connector_register() interface for
MST connectors.
Based on the above ad
After a connector is added to the drm_mode_config::connector_list, it's
visible to any in-kernel users looking up connectors via the above list.
Make sure that the connector is properly initialized before such
look-ups, by initializing the connector with
drm_connector_dynamic_register() - which doe
The connectors enumerated by the GETRESOURCES ioctl may not be fully
initialized yet wrt. to the state set up during connector registration
(for instance the connector's debugfs/sysfs interfaces may not exist
yet). This can happen in two ways:
1. Connectors initialized and added to the
drm_mode
After a connector is added to the drm_mode_config::connector_list, it's
visible to any in-kernel users looking up connectors via the above list.
Make sure that the connector is properly initialized before such
look-ups, by initializing the connector with
drm_connector_dynamic_register() - which doe
On Wed, Dec 11, 2024 at 07:21:54AM +0200, Raag Jadav wrote:
> On Tue, Dec 10, 2024 at 01:52:21PM +0100, Andi Shyti wrote:
> > Hi Raag,
> >
> > > +/* Wa_14022698537:dg2 */
> > > +static void i915_enable_g8(struct drm_i915_private *i915)
> > > +{
> > > + if (IS_DG2(i915)) {
> > > + if (IS_DG
Hi Krzysztof,
On Wed, Dec 11, 2024 at 09:56:50AM +, Krzysztof Karas wrote:
> drm_dp_tunnel_mgr_create() may return NULL on failure, which will not
> be caught via IS_ERR(), so replace it with IS_ERR_OR_NULL() macro.
>
> Signed-off-by: Krzysztof Karas
Fixes: 91888b5b1ad2 ("drm/i915/dp: Add s
On 11.12.2024 10:56, Krzysztof Karas wrote:
> drm_dp_tunnel_mgr_create() may return NULL on failure, which will not
> be caught via IS_ERR(), so replace it with IS_ERR_OR_NULL() macro.
>
> Signed-off-by: Krzysztof Karas
> ---
> drivers/gpu/drm/i915/display/intel_dp_tunnel.c | 2 +-
> 1 file c
> -Original Message-
> From: Ville Syrjälä
> Sent: Saturday, November 23, 2024 1:32 AM
> To: Garg, Nemesa
> Cc: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org
> Subject: Re: [PATCH 3/6] drm/i915/display: Replace adjusted mode with pipe
> mode
>
> On Wed, Nov 20, 2024 a
On Tue, 10 Dec 2024, "Golani, Mitulkumar Ajitkumar"
wrote:
>> -Original Message-
>> From: Intel-gfx On Behalf Of Jani
>> Nikula
>> Sent: 05 December 2024 15:01
>> To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org
>> Cc: Nikula, Jani
>> Subject: [PATCH] drm/i915/display
On Wed, Dec 11, 2024 at 11:08:16AM +0200, Abel Vesa wrote:
> On 24-10-31 18:54:25, Dmitry Baryshkov wrote:
> > On Thu, Oct 31, 2024 at 05:12:48PM +0200, Abel Vesa wrote:
> > > Link Training Tunable PHY Repeaters (LTTPRs) are defined in DisplayPort
> > > 1.4a specification. As the name suggests, the
Adding Kartihik
> Subject: Re: [PATCH 06/10] mtd: intel-dg: wake card on operations
>
> Hi Alexander,
>
> Please reduce the context when answering, otherwise it's hard to find
> all places where you commented.
>
> >> > > > That's the part that I'm not sure if I agree. if I remember from some
>
drm_dp_tunnel_mgr_create() may return NULL on failure, which will not
be caught via IS_ERR(), so replace it with IS_ERR_OR_NULL() macro.
Signed-off-by: Krzysztof Karas
---
drivers/gpu/drm/i915/display/intel_dp_tunnel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/g
Hi Dave and Sima,
Here goes our first Xe PR towards 6.14.
It's important to highlight that in couple backmerges we had to
manually solve some silent conflicts:
1. Namespace conflict issue caused by
commit cdd30ebb1b9f ("module: Convert symbol namespace to string literal")
and commit 0c45e76fcc62
Coming in again with the good patches I see :D
Apologies for not seeing these patches before, I really need to figure out a
way to keep up with dri-devel outside of patches that are CC'd to me :S (if
you ever need me to review something, you're more then welcome to poke me via
IRC btw)
For patche
== Series Details ==
Series: drm/connector: Expose only a properly inited connector
URL : https://patchwork.freedesktop.org/series/142445/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15827 -> Patchwork_142445v1
Summary
--
Hi Raag,
> Raag Jadav (4):
> drm/intel/pciids: Refactor DG2 PCI IDs into segment ranges
> drm/i915/dg2: Introduce DG2_D subplatform
> drm/i915: Introduce intel_cpu_info.c for CPU IDs
> drm/i915/dg2: Implement Wa_14022698537
merged to drm-intel-next.
Thanks,
Andi
== Series Details ==
Series: drm/connector: Expose only a properly inited connector
URL : https://patchwork.freedesktop.org/series/142445/
State : warning
== Summary ==
Error: dim checkpatch failed
f8b5a1808248 drm/connector: Add a way to init/add a connector in separate steps
42da5fe8446c drm
== Series Details ==
Series: drm/connector: Expose only a properly inited connector
URL : https://patchwork.freedesktop.org/series/142445/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Hi Dmitry,
On 12/12/24 03:09, Dmitry Baryshkov wrote:
On Wed, Dec 11, 2024 at 07:58:05PM +0530, Vignesh Raman wrote:
Uprev IGT to the latest version and update expectation files.
Signed-off-by: Vignesh Raman
---
v1:
- Pipeline link -
https://gitlab.freedesktop.org/vigneshraman/linux/-/pi
On 11/14/2024 3:48 PM, Nemesa Garg wrote:
As only second scaler can be used for sharpness check if it
is available and also check if panel fitting is also not enabled,
then set the sharpness. Panel fitting will have the preference
over sharpness property.
v2: Add the panel fitting check before
On 11/14/2024 3:48 PM, Nemesa Garg wrote:
Add new registers and related bits. Compute the strength
value and tap value based on display mode.
v2: Replace i915/dev_priv with display[Jani]
v3: Create separate file for defining register[Jani]
Add display->drm in debug prints[Jani]
v4: Rebase
Hi Helen,
On 11/12/24 21:57, Helen Mae Koike Fornazier wrote:
Hi Vignesh,
thanks for the patch.
On Wed, 11 Dec 2024 11:28:05 -0300 Vignesh Raman wrote ---
> Uprev IGT to the latest version and update expectation files.
>
> Signed-off-by: Vignesh Raman vignesh.ra...@collabora.com
On Thu, Dec 12, 2024 at 12:40:07AM +0100, Andi Shyti wrote:
> Hi Raag,
>
> > Raag Jadav (4):
> > drm/intel/pciids: Refactor DG2 PCI IDs into segment ranges
> > drm/i915/dg2: Introduce DG2_D subplatform
> > drm/i915: Introduce intel_cpu_info.c for CPU IDs
> > drm/i915/dg2: Implement Wa_1402
On 12/3/2024 14:00, Lucas De Marchi wrote:
Similar to commit 65c4c9447bfc ("usb: typec: ucsi: Fix a missing bits to
bytes conversion in ucsi_init()"), there was a missing conversion from
bits to bytes. Here the outcome is worse though: since the value is
lower than UCSI_MAX_DATA_LENGTH, instead o
On 11/14/2024 3:48 PM, Nemesa Garg wrote:
The sharpness property requires the use of one of the scaler
so need to set the sharpness scaler coefficient values.
These values are based on experiments and vary for different
tap value/win size. These values are normalized by taking the
sum of all va
> -Original Message-
> From: Intel-xe On Behalf Of Arun R
> Murthy
> Sent: Monday, November 11, 2024 2:56 PM
> To: intel...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
> Cc: Murthy, Arun R
> Subject: [PATCHv4] drm/i915/dp: Guarantee a minimum HBlank time
>
> Mandate a minim
83 matches
Mail list logo
