From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: [PATCH v2 4/7] drm/i915/psr: Rename psr_force_hw_tracking_exit as psr_force_exit
Date: Fri, 1 Nov 2024 08:27:25 +0200 [thread overview]
Message-ID: <20241101062728.3865980-5-jouni.hogander@intel.com> (raw)
In-Reply-To: <20241101062728.3865980-1-jouni.hogander@intel.com>
psr_force_hw_tracking_exit is misleading name as it is used for PSR1, PSR2
HW tracking and PSR2 selective fetch. Due to this rename it as
psr_force_exit.
Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
---
drivers/gpu/drm/i915/display/intel_psr.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
index a82d75f97c55..c1cf63f55fe6 100644
--- a/drivers/gpu/drm/i915/display/intel_psr.c
+++ b/drivers/gpu/drm/i915/display/intel_psr.c
@@ -2307,7 +2307,7 @@ static u32 man_trk_ctl_continuos_full_frame(struct intel_display *display)
PSR2_MAN_TRK_CTL_SF_CONTINUOS_FULL_FRAME;
}
-static void psr_force_hw_tracking_exit(struct intel_dp *intel_dp)
+static void psr_force_exit(struct intel_dp *intel_dp)
{
struct intel_display *display = to_intel_display(intel_dp);
enum transcoder cpu_transcoder = intel_dp->psr.transcoder;
@@ -2855,7 +2855,7 @@ void intel_psr_post_plane_update(struct intel_atomic_state *state,
/* Force a PSR exit when enabling CRC to avoid CRC timeouts */
if (crtc_state->crc_enabled && psr->enabled)
- psr_force_hw_tracking_exit(intel_dp);
+ psr_force_exit(intel_dp);
/*
* Clear possible busy bits in case we have
@@ -3252,10 +3252,10 @@ static void _psr_flush_handle(struct intel_dp *intel_dp)
* continuous full frame is disabled, only a single full
* frame is required
*/
- psr_force_hw_tracking_exit(intel_dp);
+ psr_force_exit(intel_dp);
}
} else {
- psr_force_hw_tracking_exit(intel_dp);
+ psr_force_exit(intel_dp);
if (!intel_dp->psr.active && !intel_dp->psr.busy_frontbuffer_bits)
queue_work(dev_priv->unordered_wq, &intel_dp->psr.work);
--
2.34.1
next prev parent reply other threads:[~2024-11-01 6:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 6:27 [PATCH v2 0/7] Use trans push mechanism to generate frame change event Jouni Högander
2024-11-01 6:27 ` [PATCH v2 1/7] drm/i915/psr: Add TRANS_PUSH register bit definition for PSR Jouni Högander
2024-11-01 6:27 ` [PATCH v2 2/7] drm/i915/vrr: Do not overwrite TRANS_PUSH PSR Frame Change Enable Jouni Högander
2024-11-01 6:27 ` [PATCH v2 3/7] drm/i915/vrr: Use TRANS_PUSH mechanism for PSR frame change Jouni Högander
2024-11-01 6:27 ` Jouni Högander [this message]
2024-11-01 6:27 ` [PATCH v2 5/7] drm/i915/psr: Simplify frontbuffer invalidate/flush callbacks Jouni Högander
2024-11-01 6:27 ` [PATCH v2 6/7] drm/i915/psr: Add VRR send push interface for PSR usage Jouni Högander
2024-11-01 6:27 ` [PATCH v2 7/7] drm/i915/display: Generate PSR frame change event on cursor update Jouni Högander
2024-11-04 10:01 ` ✗ Fi.CI.SPARSE: warning for Use trans push mechanism to generate frame change event (rev2) Patchwork
2024-11-04 11:51 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-04 18:30 ` ✗ 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=20241101062728.3865980-5-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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