From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 8/9] drm/i915/wm: Include ddb_y in skl_print_wm_changes() on pre-icl
Date: Thu, 19 Mar 2026 16:03:52 +0200 [thread overview]
Message-ID: <abwCSM3RhBrv_rKF@intel.com> (raw)
In-Reply-To: <b7e66b0a5203d6d96f8415f3effc5c5ba7544c2e@intel.com>
On Thu, Mar 19, 2026 at 03:44:29PM +0200, Jani Nikula wrote:
> On Thu, 19 Mar 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Pre-icl doesn't use a separate hardware plane for Y scanout,
> > and instead it's all handled magially by the hardware. We
>
> *magically
>
> > do still need to allocate DDB space for the Y color plane
> > though (PLANE_NV12_BUF_CFG). Include that information in the
> > debugs so that we know where it ended up.
> >
> > On icl+ the equivalent information is dumped as the hardware
> > Y plane's normal ddb allocation.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/display/skl_watermark.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/skl_watermark.c b/drivers/gpu/drm/i915/display/skl_watermark.c
> > index 8687026935e9..345767349988 100644
> > --- a/drivers/gpu/drm/i915/display/skl_watermark.c
> > +++ b/drivers/gpu/drm/i915/display/skl_watermark.c
> > @@ -2735,10 +2735,17 @@ skl_print_wm_changes(struct intel_atomic_state *state)
> > old = &old_crtc_state->wm.skl.plane_ddb[plane_id];
> > new = &new_crtc_state->wm.skl.plane_ddb[plane_id];
> >
> > - if (skl_ddb_entry_equal(old, new))
> > + if (!skl_ddb_entry_equal(old, new))
> > + skl_print_plane_ddb_changes(plane, old, new, " ddb");
>
> Superfluous whitespace in " ddb"?
It's there to align the columns in the "ddb" and "ddb_y" prints.
Perhaps I should use the printk field width for that instead...
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
>
> > +
> > + if (DISPLAY_VER(display) >= 11)
> > continue;
> >
> > - skl_print_plane_ddb_changes(plane, old, new, "ddb");
> > + old = &old_crtc_state->wm.skl.plane_ddb_y[plane_id];
> > + new = &new_crtc_state->wm.skl.plane_ddb_y[plane_id];
> > +
> > + if (!skl_ddb_entry_equal(old, new))
> > + skl_print_plane_ddb_changes(plane, old, new, "ddb_y");
> > }
> >
> > for_each_intel_plane_on_crtc(display->drm, crtc, plane) {
>
> --
> Jani Nikula, Intel
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-03-19 14:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 11:40 [PATCH 0/9] drm/i915/wm: Clean up pre-icl NV12 watermarks Ville Syrjala
2026-03-19 11:40 ` [PATCH 1/9] drm/i915/wm: Nuke is_planar from skl+ wm structures Ville Syrjala
2026-03-19 12:27 ` Jani Nikula
2026-03-19 11:40 ` [PATCH 2/9] drm/i915/wm: Reorder the arguments to skl_allocate_plane_ddb() Ville Syrjala
2026-03-19 12:28 ` Jani Nikula
2026-03-19 11:40 ` [PATCH 3/9] drm/i915/wm: s/skl_check_nv12_wm_level()/skl_check_wm_level_nv12()/ Ville Syrjala
2026-03-19 13:07 ` Jani Nikula
2026-03-19 11:40 ` [PATCH 4/9] drm/i915/wm: Extract skl_allocate_plane_ddb_nv12() Ville Syrjala
2026-03-19 13:21 ` Jani Nikula
2026-03-19 11:40 ` [PATCH 5/9] drm/i915/wm: Nuke wm->uv_wm[] Ville Syrjala
2026-03-19 14:06 ` Jani Nikula
2026-03-19 11:40 ` [PATCH 6/9] drm/i915/wm: s/skl_print_plane_changes()/skl_print_plane_wm_changes()/ Ville Syrjala
2026-03-19 13:36 ` Jani Nikula
2026-03-19 11:40 ` [PATCH 7/9] drm/i915/wm: Extract skl_print_plane_ddb_changes() Ville Syrjala
2026-03-19 13:38 ` Jani Nikula
2026-03-19 11:40 ` [PATCH 8/9] drm/i915/wm: Include ddb_y in skl_print_wm_changes() on pre-icl Ville Syrjala
2026-03-19 13:44 ` Jani Nikula
2026-03-19 14:03 ` Ville Syrjälä [this message]
2026-03-19 11:40 ` [PATCH 9/9] drm/i915/wm: Include .min_ddb_alloc_uv in the wm dumps Ville Syrjala
2026-03-19 14:01 ` Jani Nikula
2026-03-19 13:17 ` ✓ i915.CI.BAT: success for drm/i915/wm: Clean up pre-icl NV12 watermarks Patchwork
2026-03-20 3:58 ` ✓ i915.CI.Full: " 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=abwCSM3RhBrv_rKF@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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