From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/4] drm/i915: Clean up crtc state flag checks
Date: Thu, 20 Oct 2022 17:17:28 +0300 [thread overview]
Message-ID: <Y1FYeDF7XEcYXTUe@intel.com> (raw)
In-Reply-To: <877d0uhalo.fsf@intel.com>
On Thu, Oct 20, 2022 at 04:45:55PM +0300, Jani Nikula wrote:
> On Thu, 20 Oct 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Some cleanups for checking whether the crtc was flagged for
> > modesets/fastsets/color update.
>
> I wish we could avoid piling more static inlines in
> intel_display_types.h, but the clarity added here is great.
I mainly put them there since the first one was already there.
Dunno if the function call overhead would really be measurable,
even though we do use these a lot. Should measure it on some
real slouch of a machine I guess.
>
> On the series,
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Thanks.
>
> >
> > Ville Syrjälä (4):
> > drm/i915: Introduce intel_crtc_needs_fastset()
> > drm/i915: Remove some local 'mode_changed' bools
> > drm/i915: Don't flag both full modeset and fastset at the same time
> > drm/i915: Introduce intel_crtc_needs_color_update()
> >
> > drivers/gpu/drm/i915/display/hsw_ips.c | 8 ++--
> > drivers/gpu/drm/i915/display/intel_crtc.c | 3 +-
> > drivers/gpu/drm/i915/display/intel_cursor.c | 6 ++-
> > drivers/gpu/drm/i915/display/intel_display.c | 46 +++++++++----------
> > .../drm/i915/display/intel_display_types.h | 14 ++++++
> > .../drm/i915/display/intel_modeset_verify.c | 3 +-
> > 6 files changed, 46 insertions(+), 34 deletions(-)
>
> --
> Jani Nikula, Intel Open Source Graphics Center
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-10-20 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 12:04 [Intel-gfx] [PATCH 0/4] drm/i915: Clean up crtc state flag checks Ville Syrjala
2022-10-20 12:04 ` [Intel-gfx] [PATCH 1/4] drm/i915: Introduce intel_crtc_needs_fastset() Ville Syrjala
2022-10-20 12:04 ` [Intel-gfx] [PATCH 2/4] drm/i915: Remove some local 'mode_changed' bools Ville Syrjala
2022-10-20 12:04 ` [Intel-gfx] [PATCH 3/4] drm/i915: Don't flag both full modeset and fastset at the same time Ville Syrjala
2022-10-20 12:04 ` [Intel-gfx] [PATCH 4/4] drm/i915: Introduce intel_crtc_needs_color_update() Ville Syrjala
2022-10-20 13:45 ` [Intel-gfx] [PATCH 0/4] drm/i915: Clean up crtc state flag checks Jani Nikula
2022-10-20 14:17 ` Ville Syrjälä [this message]
2022-10-20 15:02 ` Jani Nikula
2022-10-20 15:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-10-21 15:00 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Clean up crtc state flag checks (rev2) 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=Y1FYeDF7XEcYXTUe@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.