From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <jani.nikula@linux.intel.com>,
<mitulkumar.ajitkumar.golani@intel.com>
Subject: Re: [PATCH 06/13] drm/i915/vrr: Compute vrr vsync if platforms support it
Date: Wed, 4 Sep 2024 18:25:43 +0530 [thread overview]
Message-ID: <31020c97-8ae2-42ab-992e-e786ec19dbf5@intel.com> (raw)
In-Reply-To: <ZtcE5CS-TwWxcgxV@intel.com>
On 9/3/2024 6:15 PM, Ville Syrjälä wrote:
> On Mon, Sep 02, 2024 at 01:36:27PM +0530, Ankit Nautiyal wrote:
>> Previously, TRANS_VRR_VSYNC was exclusively used for panels with
>> adaptive-sync SDP support in VRR scenarios. However, to drive fixed refresh
>> rates using the VRR Timing generator, we now need to program
>> TRANS_VRR_VSYNC regardless of adaptive sync SDP support. Therefore, let's
>> remove the adaptive sync SDP check and program TRANS_VRR_VSYNC for
>> platforms where VRR timing generator is used.
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_vrr.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>> index 9a51f5bac307..03af50b9f9eb 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>> @@ -231,7 +231,7 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
>> crtc_state->mode_flags |= I915_MODE_FLAG_VRR;
>> }
>>
>> - if (intel_dp->as_sdp_supported && crtc_state->vrr.enable) {
>> + if (HAS_AS_SDP(display) && crtc_state->vrr.enable) {
> That vrr.enable check should be nuked as well. We are supposed to
> compute the full state whether VRR is actually enabled or not.
Hmm. We are trying to move to VRR TG from LNL+ so for these platform
vrr.enable will always be set.
For older platforms where vrr.enable is not set, whether enabling
TRANS_VRR_VSYNC can cause any issue?
If this is set and TRANS_VRR_CTL is disable, then perhaps it wont have
any effect.
Regards,
Ankit
>
>> crtc_state->vrr.vsync_start =
>> (crtc_state->hw.adjusted_mode.crtc_vtotal -
>> crtc_state->hw.adjusted_mode.vsync_start);
>> --
>> 2.45.2
next prev parent reply other threads:[~2024-09-04 12:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 8:06 [PATCH 00/13] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2024-09-02 8:06 ` [PATCH 01/13] drm/i915/dp: Avoid vrr compute config for HDMI sink Ankit Nautiyal
2024-09-02 8:06 ` [PATCH 02/13] drm/i915/dp: fix the Adaptive sync Operation mode for SDP Ankit Nautiyal
2024-09-02 8:06 ` [PATCH 03/13] drm/i915/display: Add member fixed_rr to denote Fixed refresh rate with VRRTG Ankit Nautiyal
2024-09-03 12:51 ` Ville Syrjälä
2024-09-04 12:54 ` Nautiyal, Ankit K
2024-09-02 8:06 ` [PATCH 04/13] drm/i915/display: Enable MSA Ignore Timing PAR only when in not fixed_rr mode Ankit Nautiyal
2024-09-03 3:15 ` kernel test robot
2024-09-03 7:52 ` kernel test robot
2024-09-02 8:06 ` [PATCH 05/13] drm/i915/dp: Set FAVT mode in DP SDP with fixed refresh rate Ankit Nautiyal
2024-09-02 8:06 ` [PATCH 06/13] drm/i915/vrr: Compute vrr vsync if platforms support it Ankit Nautiyal
2024-09-03 12:45 ` Ville Syrjälä
2024-09-04 12:55 ` Nautiyal, Ankit K [this message]
2024-09-02 8:06 ` [PATCH 07/13] drm/i915/hdmi: Use VRR Timing generator for HDMI Ankit Nautiyal
2024-09-02 8:06 ` [PATCH 08/13] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2024-09-02 8:06 ` [PATCH 09/13] drm/i915/psr: Allow PSR for fixed refrsh rate with VRR TG Ankit Nautiyal
2024-09-02 8:06 ` [PATCH 10/13] drm/i915/vrr: Avoid sending PUSH when VRR TG is used with Fixed refresh rate Ankit Nautiyal
2024-09-03 13:02 ` Ville Syrjälä
2024-09-04 12:57 ` Nautiyal, Ankit K
2024-09-02 8:06 ` [PATCH 11/13] drm/i915/vrr: Handle joiner with vrr Ankit Nautiyal
2024-09-03 13:04 ` Ville Syrjälä
2024-09-04 13:02 ` Nautiyal, Ankit K
2024-09-02 8:06 ` [PATCH 12/13] drm/i915/vrr: Always use VRR timing generator for XELPD+ Ankit Nautiyal
2024-09-03 13:25 ` Ville Syrjälä
2024-09-04 13:08 ` Nautiyal, Ankit K
2024-09-02 8:06 ` [PATCH 13/13] drm/i915/display: Add fixed_rr to crtc_state_dump Ankit Nautiyal
2024-09-02 12:23 ` ✗ Fi.CI.SPARSE: warning for Use VRR timing generator for fixed refresh rate modes (rev5) Patchwork
2024-09-02 12:43 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-02 18:08 ` ✗ 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=31020c97-8ae2-42ab-992e-e786ec19dbf5@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox