From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm/i915/pfit: panel fitter refactors
Date: Thu, 27 Feb 2025 20:59:05 +0200 [thread overview]
Message-ID: <87frjz2ozq.fsf@intel.com> (raw)
In-Reply-To: <Z78O5ibtHlh5Qbp4@intel.com>
On Wed, 26 Feb 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Feb 26, 2025 at 12:01:06PM +0200, Jani Nikula wrote:
>> Move pfit code to intel_pfit.c, convert to struct intel_display, split
>> out pfit registers to a separate file, etc.
>>
>> Jani Nikula (5):
>> drm/i915/pfit: rename intel_panel_fitting() to
>> intel_pfit_compute_config()
>> drm/i915/pfit: move ilk and i9xx pfit code to intel_pfit.[ch]
>> drm/i915/pfit: fix comment style for moved comments
>> drm/i915/pfit: convert moved code to struct intel_display
>> drm/i915/pfit: split out intel_pfit_regs.h
>
> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks, pushed to din.
BR,
Jani.
>
>>
>> drivers/gpu/drm/i915/display/icl_dsi.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_crt.c | 1 +
>> drivers/gpu/drm/i915/display/intel_ddi.c | 1 +
>> drivers/gpu/drm/i915/display/intel_display.c | 165 +----------------
>> drivers/gpu/drm/i915/display/intel_display.h | 2 -
>> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_dp_mst.c | 1 +
>> drivers/gpu/drm/i915/display/intel_hdmi.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_lvds.c | 3 +-
>> drivers/gpu/drm/i915/display/intel_overlay.c | 1 +
>> drivers/gpu/drm/i915/display/intel_pfit.c | 168 +++++++++++++++++-
>> drivers/gpu/drm/i915/display/intel_pfit.h | 10 +-
>> .../gpu/drm/i915/display/intel_pfit_regs.h | 79 ++++++++
>> drivers/gpu/drm/i915/display/vlv_dsi.c | 2 +-
>> drivers/gpu/drm/i915/i915_reg.h | 70 --------
>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 1 +
>> 16 files changed, 268 insertions(+), 242 deletions(-)
>> create mode 100644 drivers/gpu/drm/i915/display/intel_pfit_regs.h
>>
>> --
>> 2.39.5
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-02-27 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 10:01 [PATCH 0/5] drm/i915/pfit: panel fitter refactors Jani Nikula
2025-02-26 10:01 ` [PATCH 1/5] drm/i915/pfit: rename intel_panel_fitting() to intel_pfit_compute_config() Jani Nikula
2025-02-26 10:01 ` [PATCH 2/5] drm/i915/pfit: move ilk and i9xx pfit code to intel_pfit.[ch] Jani Nikula
2025-02-26 10:01 ` [PATCH 3/5] drm/i915/pfit: fix comment style for moved comments Jani Nikula
2025-02-26 10:01 ` [PATCH 4/5] drm/i915/pfit: convert moved code to struct intel_display Jani Nikula
2025-02-26 10:01 ` [PATCH 5/5] drm/i915/pfit: split out intel_pfit_regs.h Jani Nikula
2025-02-26 12:53 ` [PATCH 0/5] drm/i915/pfit: panel fitter refactors Ville Syrjälä
2025-02-27 18:59 ` Jani Nikula [this message]
2025-02-26 13:16 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-26 13:16 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-26 13:17 ` ✓ CI.KUnit: success " Patchwork
2025-02-26 13:34 ` ✓ CI.Build: " Patchwork
2025-02-26 13:36 ` ✓ CI.Hooks: " Patchwork
2025-02-26 13:38 ` ✗ CI.checksparse: warning " Patchwork
2025-02-26 13:55 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-26 14:55 ` ✗ Xe.CI.Full: failure " Patchwork
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=87frjz2ozq.fsf@intel.com \
--to=jani.nikula@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