Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 0/9] drm/i915: Further drm_get_format_info() stuff
Date: Mon, 10 Nov 2025 13:10:02 +0200	[thread overview]
Message-ID: <0fd8d5f5b4dbadcaf99b9395d248acbca35e927f@intel.com> (raw)
In-Reply-To: <20251107181126.5743-1-ville.syrjala@linux.intel.com>

On Fri, 07 Nov 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Finish eliminating the expensive extra format info lookups.
>
> And since I ended up strafing the cursor code in the end I included
> a few additional claenups there.

Some typo nitpicks in commit messages, otherwise series is

Reviewed-by: Jani Nikula <jani.nikula@intel.com>


>
> Ville Syrjälä (9):
>   drm/i915: Introduce intel_dumb_fb_max_stride()
>   drm/i915: Pass drm_format_info into plane->max_stride()
>   drm/i915: Populate fb->format accurately in BIOS FB readout
>   drm/i915: Nuke intel_plane_config.tiling
>   drm/i915/fb: Init 'ret' in each error branch in
>     intel_framebuffer_init()
>   drm/i915/wm: Use drm_get_format_info() in SKL+ cursor DDB allocation
>   drm/i915: Use mode_config->cursor_width for cursor DDB allocation
>   drm/i915/cursor: Extract intel_cursor_mode_config_init()
>   drm/i915/cursor: Initialize 845 vs 865 cursor size separately
>
>  drivers/gpu/drm/i915/display/i9xx_plane.c     | 32 ++++++++-----------
>  drivers/gpu/drm/i915/display/i9xx_plane.h     |  5 +--
>  drivers/gpu/drm/i915/display/intel_cursor.c   | 28 +++++++++++++---
>  drivers/gpu/drm/i915/display/intel_cursor.h   |  2 ++
>  drivers/gpu/drm/i915/display/intel_display.c  | 24 ++++++++++----
>  drivers/gpu/drm/i915/display/intel_display.h  |  8 +++--
>  .../drm/i915/display/intel_display_driver.c   | 13 ++------
>  .../drm/i915/display/intel_display_types.h    |  5 ++-
>  drivers/gpu/drm/i915/display/intel_fb.c       | 23 +++++++------
>  .../drm/i915/display/intel_plane_initial.c    | 11 ++++---
>  drivers/gpu/drm/i915/display/intel_sprite.c   | 10 +++---
>  .../drm/i915/display/skl_universal_plane.c    | 22 ++++++-------
>  drivers/gpu/drm/i915/display/skl_watermark.c  | 15 ++++++---
>  drivers/gpu/drm/i915/gem/i915_gem_create.c    |  4 +--
>  14 files changed, 118 insertions(+), 84 deletions(-)

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2025-11-10 11:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 18:11 [PATCH 0/9] drm/i915: Further drm_get_format_info() stuff Ville Syrjala
2025-11-07 18:11 ` [PATCH 1/9] drm/i915: Introduce intel_dumb_fb_max_stride() Ville Syrjala
2025-11-07 18:11 ` [PATCH 2/9] drm/i915: Pass drm_format_info into plane->max_stride() Ville Syrjala
2025-11-07 18:11 ` [PATCH 3/9] drm/i915: Populate fb->format accurately in BIOS FB readout Ville Syrjala
2025-11-07 18:11 ` [PATCH 4/9] drm/i915: Nuke intel_plane_config.tiling Ville Syrjala
2025-11-07 18:11 ` [PATCH 5/9] drm/i915/fb: Init 'ret' in each error branch in intel_framebuffer_init() Ville Syrjala
2025-11-10 11:07   ` Jani Nikula
2025-11-07 18:11 ` [PATCH 6/9] drm/i915/wm: Use drm_get_format_info() in SKL+ cursor DDB allocation Ville Syrjala
2025-11-10 11:08   ` Jani Nikula
2025-11-07 18:11 ` [PATCH 7/9] drm/i915: Use mode_config->cursor_width for " Ville Syrjala
2025-11-10 11:09   ` Jani Nikula
2025-11-07 18:11 ` [PATCH 8/9] drm/i915/cursor: Extract intel_cursor_mode_config_init() Ville Syrjala
2025-11-07 18:11 ` [PATCH 9/9] drm/i915/cursor: Initialize 845 vs 865 cursor size separately Ville Syrjala
2025-11-07 21:04 ` ✓ i915.CI.BAT: success for drm/i915: Further drm_get_format_info() stuff Patchwork
2025-11-08 20:43 ` ✗ i915.CI.Full: failure " Patchwork
2025-11-10 11:10 ` Jani Nikula [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0fd8d5f5b4dbadcaf99b9395d248acbca35e927f@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox