Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Luca Coelho <luca@coelho.fi>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Extract intel_post_plane_update_after_readout()
Date: Thu, 19 Sep 2024 14:17:48 +0300	[thread overview]
Message-ID: <ZuwIXLS25AcYaQis@intel.com> (raw)
In-Reply-To: <781573ba655d53c930b3db98319bc9831c15f2b4.camel@coelho.fi>

On Thu, Sep 19, 2024 at 10:53:15AM +0300, Luca Coelho wrote:
> On Mon, 2024-09-16 at 18:29 +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Clean up the main commit_tail() codepath a bit by pulling
> > the post plane update steps that need to performed after
> > readout into their own little function
> > (intel_post_plane_update_after_readout()).
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> 
> This looks fine, but what is the exact motivation here? Is it just to
> reduce the size of intel_atomic_commit_tail()?

That, and I guess some kind of attempt to keep the pre vs. post
update code mostly in sync (might be easier to remember to update
both sides if they are named somewhat consistently).

> 
> Regardless:
> 
> Reviewed-by: Luca Coelho <luciano.coelho@intel.com>

Ta.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-09-19 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 15:29 [PATCH 0/2] drm/i915: Some modeset refactoring Ville Syrjala
2024-09-16 15:29 ` [PATCH 1/2] drm/i915/color: Extract intel_color_modeset() Ville Syrjala
2024-09-19  7:50   ` Luca Coelho
2024-09-16 15:29 ` [PATCH 2/2] drm/i915: Extract intel_post_plane_update_after_readout() Ville Syrjala
2024-09-19  7:53   ` Luca Coelho
2024-09-19 11:17     ` Ville Syrjälä [this message]
2024-09-16 19:50 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Some modeset refactoring Patchwork
2024-09-16 20:10 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-17  9:57 ` ✗ Fi.CI.IGT: 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=ZuwIXLS25AcYaQis@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luca@coelho.fi \
    /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