From: Anusha Srivatsa <anusha.srivatsa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/4] Move CDCLK checks to atomic check phase
Date: Wed, 27 Jul 2022 16:26:39 -0700 [thread overview]
Message-ID: <20220727232643.533884-1-anusha.srivatsa@intel.com> (raw)
The intention is to check for squashing, crawling conditions
at atomic check phase and prepare for commit phase. This basically
means the in-flight cdclk state is available. intel_cdclk_can_squash(),
intel_cdclk_can_crawl() and intel_cdclk_needs_modeset() have changes
to accommodate this.
Cc: Matt Roper <matthew.d.roper@intel.com>
Anusha Srivatsa (4):
drm/i915/display: Add CDCLK actions to intel_cdclk_state
drm/i915/display: s/intel_cdclk_can_squash/intel_cdclk_squash
drm/i915/display: s/intel_cdclk_can_crawl/intel_cdclk_crawl
drm/i915/display: Add cdclk checks to atomic check
drivers/gpu/drm/i915/display/intel_cdclk.c | 151 ++++++++++++++-------
drivers/gpu/drm/i915/display/intel_cdclk.h | 13 ++
2 files changed, 112 insertions(+), 52 deletions(-)
--
2.25.1
next reply other threads:[~2022-07-27 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 23:26 Anusha Srivatsa [this message]
2022-07-27 23:26 ` [Intel-gfx] [PATCH 1/4] drm/i915/display: Add CDCLK actions to intel_cdclk_state Anusha Srivatsa
2022-07-27 23:26 ` [Intel-gfx] [PATCH 2/4] drm/i915/display: s/intel_cdclk_can_squash/intel_cdclk_squash Anusha Srivatsa
2022-07-27 23:26 ` [Intel-gfx] [PATCH 3/4] drm/i915/display: s/intel_cdclk_can_crawl/intel_cdclk_crawl Anusha Srivatsa
2022-07-27 23:26 ` [Intel-gfx] [PATCH 4/4] drm/i915/display: Add cdclk checks to atomic check Anusha Srivatsa
2022-07-27 23:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Move CDCLK checks to atomic check phase Patchwork
2022-07-27 23:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-07-28 0:13 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=20220727232643.533884-1-anusha.srivatsa@intel.com \
--to=anusha.srivatsa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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