From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Nemesa Garg <nemesa.garg@intel.com>
Subject: Re: [PATCH v1 0/9] drm/i915/scaler: allocation cleanup
Date: Wed, 10 Jun 2026 15:44:44 +0300 [thread overview]
Message-ID: <ailcPBpmqJ0wa7--@intel.com> (raw)
In-Reply-To: <20260609231217.208357-1-michal.grzelak@intel.com>
On Wed, Jun 10, 2026 at 01:12:08AM +0200, Michał Grzelak wrote:
> Apparently during review of commit 17d70a0760f2 ("drm/i915/casf: Extract
> scaler_has_casf()") I missed that argument plane_state isn't used
> anymore. While at it couple other fixes included.
>
> This series will almost surely need a better splitting than currently
> is, but I hope now it is slightly easier to review.
>
> BR,
> Michał
>
>
> Michał Grzelak (9):
> drm/i915/scaler: remove unused plane_state argument
> drm/i915/scaler: s/i/scaler_id/
Those seem fine.
> drm/i915/scaler: de-Morgan-ize !scaler_has_casf()
> drm/i915/scaler: move independent CASF check
> drm/i915/scaler: check CASF before allocation's loop
> drm/i915/scaler: inline CASF scaler allocation
> drm/i915/scaler: linearize scaler allocation
> drm/i915/scaler: move CASF alloc check into
> intel_atomic_setup_scaler()
> drm/i915/scaler: move CASF alloc check into setup_crtc_scaler()
This looks like it's replacing a simple "does this scale have CASF?"
check with some kind of more complicated special casing of the CASF
scaler elsewhere. I don't like it.
>
> drivers/gpu/drm/i915/display/skl_scaler.c | 43 ++++++++++++-----------
> 1 file changed, 22 insertions(+), 21 deletions(-)
>
> --
> 2.45.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-06-10 12:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 23:12 [PATCH v1 0/9] drm/i915/scaler: allocation cleanup Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 1/9] drm/i915/scaler: remove unused plane_state argument Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 2/9] drm/i915/scaler: s/i/scaler_id/ Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 3/9] drm/i915/scaler: de-Morgan-ize !scaler_has_casf() Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 4/9] drm/i915/scaler: move independent CASF check Michał Grzelak
2026-06-10 14:20 ` Jani Nikula
2026-06-09 23:12 ` [PATCH v1 5/9] drm/i915/scaler: check CASF before allocation's loop Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 6/9] drm/i915/scaler: inline CASF scaler allocation Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 7/9] drm/i915/scaler: linearize " Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 8/9] drm/i915/scaler: move CASF alloc check into intel_atomic_setup_scaler() Michał Grzelak
2026-06-09 23:12 ` [PATCH v1 9/9] drm/i915/scaler: move CASF alloc check into setup_crtc_scaler() Michał Grzelak
2026-06-10 5:29 ` Garg, Nemesa
2026-06-09 23:20 ` ✓ CI.KUnit: success for drm/i915/scaler: allocation cleanup Patchwork
2026-06-10 0:00 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-10 12:44 ` Ville Syrjälä [this message]
2026-06-10 22:59 ` [PATCH v1 0/9] " Michał Grzelak
2026-06-10 14:45 ` ✓ Xe.CI.FULL: success for " 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=ailcPBpmqJ0wa7--@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.grzelak@intel.com \
--cc=nemesa.garg@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