From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 6/6] drm/i915: Treat DMRRS as static DRRS
Date: Fri, 27 May 2022 23:49:49 +0300 [thread overview]
Message-ID: <20220527204949.2264-7-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20220527204949.2264-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Some machines declare DRRS type = seamless, DRRS = no, DMRRS = yes.
I *think* DMRRS stands for "dynamcic media refresh rate", and
I suspect the way it's meant to work is that it lets the driver
switch refresh rates to match the frame rate for media playback.
Obviously for us all that kind of policy stuff is entirely up to
userspace, so the only thing we may do is make the extra refresh
rate(s) available.
So let's treat this case as just static DRRS for now. In the
future We might want to differentiate the "seamless w/ downclocking"
vs. "seamless w/o downclocking" cases so that we could do seamless
refresh rate changes for systems that only claim to support DMRRS.
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/125
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
drivers/gpu/drm/i915/display/intel_bios.c | 24 +++++++++++++++++++----
1 file changed, 20 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_bios.c b/drivers/gpu/drm/i915/display/intel_bios.c
index 0774238e429b..c42b9e7d0dce 100644
--- a/drivers/gpu/drm/i915/display/intel_bios.c
+++ b/drivers/gpu/drm/i915/display/intel_bios.c
@@ -1279,8 +1279,16 @@ parse_panel_driver_features(struct drm_i915_private *i915,
* static DRRS is 0 and DRRS not supported is represented by
* driver->drrs_enabled=false
*/
- if (!driver->drrs_enabled)
- panel->vbt.drrs_type = DRRS_TYPE_NONE;
+ if (!driver->drrs_enabled && panel->vbt.drrs_type != DRRS_TYPE_NONE) {
+ /*
+ * FIXME Should DMRRS perhaps be treated as seamless
+ * but without the automatic downclocking?
+ */
+ if (driver->dmrrs_enabled)
+ panel->vbt.drrs_type = DRRS_TYPE_STATIC;
+ else
+ panel->vbt.drrs_type = DRRS_TYPE_NONE;
+ }
panel->vbt.psr.enable = driver->psr_enabled;
}
@@ -1310,8 +1318,16 @@ parse_power_conservation_features(struct drm_i915_private *i915,
* static DRRS is 0 and DRRS not supported is represented by
* power->drrs & BIT(panel_type)=false
*/
- if (!(power->drrs & BIT(panel_type)))
- panel->vbt.drrs_type = DRRS_TYPE_NONE;
+ if (!(power->drrs & BIT(panel_type)) && panel->vbt.drrs_type != DRRS_TYPE_NONE) {
+ /*
+ * FIXME Should DMRRS perhaps be treated as seamless
+ * but without the automatic downclocking?
+ */
+ if (power->dmrrs & BIT(panel_type))
+ panel->vbt.drrs_type = DRRS_TYPE_STATIC;
+ else
+ panel->vbt.drrs_type = DRRS_TYPE_NONE;
+ }
if (i915->vbt.version >= 232)
panel->vbt.edp.hobl = power->hobl & BIT(panel_type);
--
2.35.1
next prev parent reply other threads:[~2022-05-27 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 20:49 [Intel-gfx] [PATCH 0/6] drm/i915: Accept more fixed modes with VRR/DMRRS panels Ville Syrjala
2022-05-27 20:49 ` [Intel-gfx] [PATCH 1/6] drm/i915: Parse VRR capability from VBT Ville Syrjala
2022-05-30 12:18 ` Jani Nikula
2022-05-27 20:49 ` [Intel-gfx] [PATCH 2/6] drm/i915: Print out rejected fixed modes Ville Syrjala
2022-05-30 12:20 ` Jani Nikula
2022-05-27 20:49 ` [Intel-gfx] [PATCH 3/6] drm/i915: Accept more fixed modes with VRR panels Ville Syrjala
2022-05-30 12:31 ` Jani Nikula
2022-05-27 20:49 ` [Intel-gfx] [PATCH 4/6] drm/i915/bios: Fix aggressiveness typos Ville Syrjala
2022-05-30 12:33 ` Jani Nikula
2022-05-27 20:49 ` [Intel-gfx] [PATCH 5/6] drm/i915/bios: Define more BDB contents Ville Syrjala
2022-05-30 12:55 ` Jani Nikula
2022-05-31 18:24 ` Lyude Paul
2022-05-31 19:03 ` Ville Syrjälä
2022-05-27 20:49 ` Ville Syrjala [this message]
2022-05-30 13:22 ` [Intel-gfx] [PATCH 6/6] drm/i915: Treat DMRRS as static DRRS Jani Nikula
2022-05-30 13:26 ` Jani Nikula
2022-05-28 15:01 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Accept more fixed modes with VRR/DMRRS panels 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=20220527204949.2264-7-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.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