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>,
<arun.r.murthy@intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] drm/i915/vrr: Add vrr.vsync_{start,end} in vrr_params_changed
Date: Tue, 8 Apr 2025 17:04:43 +0530 [thread overview]
Message-ID: <004b6e7e-af38-4e12-9fef-cf2d4303cdec@intel.com> (raw)
In-Reply-To: <Z-_83ng-1KTFl_50@intel.com>
On 4/4/2025 9:08 PM, Ville Syrjälä wrote:
> On Fri, Apr 04, 2025 at 01:35:40PM +0530, Ankit Nautiyal wrote:
>> Add the missing vrr parameters in vrr_params_changed() helper.
>> This ensures that changes in vrr.vsync_{start,end} trigger a call to
>> appropriate helpers to update the VRR registers.
>>
>> Fixes: e8cd188e91bb ("drm/i915/display: Compute vrr_vsync params")
>> Cc: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
>> Cc: Arun R Murthy <arun.r.murthy@intel.com>
>> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: <stable@vger.kernel.org> # v6.10+
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_display.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
>> index c540e2cae1f0..ced8ba0f8d6d 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>> @@ -969,7 +969,9 @@ static bool vrr_params_changed(const struct intel_crtc_state *old_crtc_state,
>> old_crtc_state->vrr.vmin != new_crtc_state->vrr.vmin ||
>> old_crtc_state->vrr.vmax != new_crtc_state->vrr.vmax ||
>> old_crtc_state->vrr.guardband != new_crtc_state->vrr.guardband ||
>> - old_crtc_state->vrr.pipeline_full != new_crtc_state->vrr.pipeline_full;
>> + old_crtc_state->vrr.pipeline_full != new_crtc_state->vrr.pipeline_full ||
>> + old_crtc_state->vrr.vsync_start != new_crtc_state->vrr.vsync_start ||
>> + old_crtc_state->vrr.vsync_end != new_crtc_state->vrr.vsync_end;
> These seem to yet another set of values that are potentially problematic
> for the always_use_vrr_tg()==true case. I'm not sure how careful we
> should be with this stuff...
>
> And the whole encoder->update_pipe()/infoframe fastset stuff needs to
> be rewritten to make sure the all the changes it does are either atomic
> or happen on the correct side of the actual commit. Right now, for AS
> SDP specifically, we enable/disable the infoframe potentially before
> the actual commit, which I think is wrong at least for the disable case.
>
> Also we still seem to be missing EMP_AS_SDP_TL completely.
>
> Anyways, this patch isn't wrong at least so
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks for the review, the patch was pushed to drm-intel-next, missed to
update earlier.
Regards,
Ankit
>
>> }
>>
>> static bool cmrr_params_changed(const struct intel_crtc_state *old_crtc_state,
>> --
>> 2.45.2
next prev parent reply other threads:[~2025-04-08 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 8:05 [PATCH] drm/i915/vrr: Add vrr.vsync_{start, end} in vrr_params_changed Ankit Nautiyal
2025-04-04 8:05 ` [PATCH] drm/i915/vrr: Add vrr.vsync_{start,end} " Ankit Nautiyal
2025-04-04 9:45 ` ✓ i915.CI.BAT: success for drm/i915/vrr: Add vrr.vsync_{start, end} " Patchwork
2025-04-04 12:02 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-04 15:38 ` [PATCH] drm/i915/vrr: Add vrr.vsync_{start,end} " Ville Syrjälä
2025-04-07 8:58 ` Nautiyal, Ankit K
2025-04-08 11:34 ` Nautiyal, Ankit K [this message]
2025-04-06 5:00 ` ✓ i915.CI.BAT: success for drm/i915/vrr: Add vrr.vsync_{start, end} in vrr_params_changed (rev2) Patchwork
2025-04-06 6:36 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-07 8:00 ` ✓ i915.CI.Full: success " 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=004b6e7e-af38-4e12-9fef-cf2d4303cdec@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.