From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 5/5] drm/i915/tv: use DISPLAY_VER instead of GRAPHICS_VER
Date: Thu, 4 Jan 2024 19:43:50 +0200 [thread overview]
Message-ID: <20240104174350.823605-5-jani.nikula@intel.com> (raw)
In-Reply-To: <20240104174350.823605-1-jani.nikula@intel.com>
Display code should not care about graphics version. It's only comments
here, but update anyway.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
drivers/gpu/drm/i915/display/intel_tv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_tv.c b/drivers/gpu/drm/i915/display/intel_tv.c
index d4386cb3569e..9a217805d2f6 100644
--- a/drivers/gpu/drm/i915/display/intel_tv.c
+++ b/drivers/gpu/drm/i915/display/intel_tv.c
@@ -1327,7 +1327,7 @@ intel_tv_compute_config(struct intel_encoder *encoder,
* the active portion. Hence following this formula seems
* more trouble that it's worth.
*
- * if (GRAPHICS_VER(dev_priv) == 4) {
+ * if (DISPLAY_VER(dev_priv) == 4) {
* num = cdclk * (tv_mode->oversample >> !tv_mode->progressive);
* den = tv_mode->clock;
* } else {
--
2.39.2
next prev parent reply other threads:[~2024-01-04 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 17:43 [PATCH 1/5] drm/i915/irq: use DISPLAY_VER instead of GRAPHICS_VER Jani Nikula
2024-01-04 17:43 ` [PATCH 2/5] drm/i915/dmc: " Jani Nikula
2024-01-04 17:43 ` [PATCH 3/5] drm/i915/hdcp: " Jani Nikula
2024-01-04 17:43 ` [PATCH 4/5] drm/i915/display: use IS_DISPLAY_VER instead of IS_GRAPHICS_VER Jani Nikula
2024-01-04 17:43 ` Jani Nikula [this message]
2024-01-04 21:32 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/5] drm/i915/irq: use DISPLAY_VER instead of GRAPHICS_VER Patchwork
2024-01-04 21:46 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-04 22:26 ` [PATCH 1/5] " Matt Roper
2024-01-05 13:59 ` Jani Nikula
2024-01-04 23:42 ` ✗ Fi.CI.IGT: failure for series starting with [1/5] " 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=20240104174350.823605-5-jani.nikula@intel.com \
--to=jani.nikula@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