Re: [Intel-gfx] [PATCH] drm/i915/display: Include i915_active header in frontbuffer tracking code

On Fri, 2023-09-29 at 14:28 +0300, Jani Nikula wrote: > On Fri, 29 Sep 2023, Jouni Högander wrote: > > Intel frontbuffer tracking code is using i915_active functions -> > > include > > i915_active.h directly instead of relying getting indirectly > > included. > > > > Cc: Jani Nikula > > > >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/uapi: fix doc typos

== Series Details == Series: drm/i915/uapi: fix doc typos URL : https://patchwork.freedesktop.org/series/124498/ State : success == Summary == CI Bug Log - changes from CI_DRM_13696 -> Patchwork_124498v1 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/uapi: fix doc typos

== Series Details == Series: drm/i915/uapi: fix doc typos URL : https://patchwork.freedesktop.org/series/124498/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] [PATCH] drm/i915/uapi: fix doc typos

Correct typo of "its". Add a comma for clarity. Signed-off-by: Randy Dunlap Cc: Jani Nikula Cc: Joonas Lahtinen Cc: Rodrigo Vivi Cc: Tvrtko Ursulin Cc: intel-gfx@lists.freedesktop.org Cc: Maarten Lankhorst Cc: Maxime Ripard Cc: Thomas Zimmermann Cc: dri-de...@lists.freedesktop.org ---

[Intel-gfx] ✓ Fi.CI.BAT: success for scalable display feature configurations (rev2)

== Series Details == Series: scalable display feature configurations (rev2) URL : https://patchwork.freedesktop.org/series/124323/ State : success == Summary == CI Bug Log - changes from CI_DRM_13696 -> Patchwork_124323v2 Summary ---

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for scalable display feature configurations (rev2)

== Series Details == Series: scalable display feature configurations (rev2) URL : https://patchwork.freedesktop.org/series/124323/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] [PATCH v1 3/3] drm/i915/xe2lpd: update the scaler feature capability

Update the number of scalers per pipe based on the display capabilities reported. v1: define the field values instead of the magic number (JaniN) Bspec: 71161 Signed-off-by: Vinod Govindapillai --- drivers/gpu/drm/i915/display/intel_display_device.c | 7 +++ 1 file changed, 7 insertions(+)

[Intel-gfx] [PATCH v1 0/3] scalable display feature configurations

Get the reported device capabilities and update DSC and scaler feature support v1: use defined field values instead of magic numbers (Jani Nikula) Vinod Govindapillai (3): drm/i915/xe2lpd: display capability register definitions drm/i915/xe2lpd: update the dsc feature capability

[Intel-gfx] [PATCH v1 2/3] drm/i915/xe2lpd: update the dsc feature capability

Update the global dsc flag based on the display capabilities reported. v1: define the field values instead of the magic number (JaniN) Bspec: 71161 Signed-off-by: Vinod Govindapillai --- drivers/gpu/drm/i915/display/intel_display_device.c | 8 1 file changed, 8 insertions(+) diff

[Intel-gfx] [PATCH v1 1/3] drm/i915/xe2lpd: display capability register definitions

Register definitions to track the reported scalable display feature configurations Bspec: 71161 Signed-off-by: Vinod Govindapillai --- drivers/gpu/drm/i915/i915_reg.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h

Re: [Intel-gfx] [PATCH 5/5] drm/i915/fbc: Split plane pixel format checks per-platform

On Thu, 2023-09-14 at 14:38 +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Carve up pixel_format_is_valid() into per-platform variants to > make it easier to see what limits are actually being imposed. > > Note that the XRGB1555 can be dropped from the g4x+ variant > since the plane no

Re: [Intel-gfx] [PATCH 4/5] drm/i915/fbc: Split plane rotation checks per-platform

On Thu, 2023-09-14 at 14:38 +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Carve up rotation_is_valid() into per-platform variants to > make it easier to see what limits are actually being imposed. > > TODO: maybe go for vfuncs later > > Signed-off-by: Ville Syrjälä > --- >  

Re: [Intel-gfx] [PATCH 3/5] drm/i915/fbc: Split plane tiling checks per-platform

Hi Ville, On Thu, 2023-09-14 at 14:38 +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Carve up tiling_is_valid() into per-platform variants to > make it easier to see what limits are actually being imposed. > > TODO: maybe go for vfuncs later > > Signed-off-by: Ville Syrjälä > --- >  

Re: [Intel-gfx] [PATCH 2/5] drm/i915/fbc: Split plane stride checks per-platform

Hi Ville, On Thu, 2023-09-14 at 14:38 +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Carve up stride_is_valid() into per-platform variants to > make it easier to see what limits are actually being imposed. > > TODO: maybe go for vfuncs later > > Signed-off-by: Ville Syrjälä > --- >  

Re: [Intel-gfx] [PATCH v2 2/2] drm: Replace drm_framebuffer plane size functions with its equivalents

On 9/26/23 16:15, Carlos Eduardo Gallo Filho wrote: The functions drm_framebuffer_plane_{width,height} and fb_plane_{width,height} do exactly the same job of its equivalents drm_format_info_plane_{width,height} from drm_fourcc. The only reason to have these functions on drm_framebuffer would be

Re: [Intel-gfx] [PATCH v2 1/2] drm: Remove plane hsub/vsub alignment requirement for core helpers

Hi Carlos, On 9/26/23 16:15, Carlos Eduardo Gallo Filho wrote: The drm_format_info_plane_{height,width} functions was implemented using regular division for the plane size calculation, which cause issues [1][2] when used on contexts where the dimensions are misaligned with relation to the