dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, michel@daenzer.net, Marek.Olsak@amd.com,
	manasi.d.navare@intel.com, Alexander.Deucher@amd.com,
	Christian.Koenig@amd.com
Subject: Re: [PATCH v5 2/4] drm: Add vrr_enabled property to drm CRTC
Date: Sat, 13 Oct 2018 19:38:41 +0200	[thread overview]
Message-ID: <e1feafbe-2c37-d1ff-8a45-4672b4da1264@gmail.com> (raw)
In-Reply-To: <20181012164458.12864-3-nicholas.kazlauskas@amd.com>

Am 12.10.2018 um 18:44 schrieb Nicholas Kazlauskas:
> This patch introduces the 'vrr_enabled' CRTC property to allow
> dynamic control over variable refresh rate support for a CRTC.
>
> This property should be treated like a content hint to the driver -
> if the hardware or driver is not capable of driving variable refresh
> timings then this is not considered an error.
>
> Capability for variable refresh rate support should be determined
> by querying the vrr_capable drm connector property.
>
> It is worth noting that while the property is intended for atomic use
> it isn't filtered from legacy userspace queries. This allows for Xorg
> userspace drivers to implement support.

I'm honestly still not convinced that a per CRTC property is actually 
the right approach.

What we should rather do instead is to implement a target timestamp for 
the page flip.

Regards,
Christian.

>
> Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> ---
>   drivers/gpu/drm/drm_atomic_uapi.c | 4 ++++
>   drivers/gpu/drm/drm_crtc.c        | 2 ++
>   drivers/gpu/drm/drm_mode_config.c | 6 ++++++
>   include/drm/drm_crtc.h            | 9 +++++++++
>   include/drm/drm_mode_config.h     | 5 +++++
>   5 files changed, 26 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_atomic_uapi.c b/drivers/gpu/drm/drm_atomic_uapi.c
> index d5b7f315098c..eec396a57b88 100644
> --- a/drivers/gpu/drm/drm_atomic_uapi.c
> +++ b/drivers/gpu/drm/drm_atomic_uapi.c
> @@ -433,6 +433,8 @@ static int drm_atomic_crtc_set_property(struct drm_crtc *crtc,
>   		ret = drm_atomic_set_mode_prop_for_crtc(state, mode);
>   		drm_property_blob_put(mode);
>   		return ret;
> +	} else if (property == config->prop_vrr_enabled) {
> +		state->vrr_enabled = val;
>   	} else if (property == config->degamma_lut_property) {
>   		ret = drm_atomic_replace_property_blob_from_id(dev,
>   					&state->degamma_lut,
> @@ -491,6 +493,8 @@ drm_atomic_crtc_get_property(struct drm_crtc *crtc,
>   		*val = state->active;
>   	else if (property == config->prop_mode_id)
>   		*val = (state->mode_blob) ? state->mode_blob->base.id : 0;
> +	else if (property == config->prop_vrr_enabled)
> +		*val = state->vrr_enabled;
>   	else if (property == config->degamma_lut_property)
>   		*val = (state->degamma_lut) ? state->degamma_lut->base.id : 0;
>   	else if (property == config->ctm_property)
> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> index 5f488aa80bcd..e4eb2c897ff4 100644
> --- a/drivers/gpu/drm/drm_crtc.c
> +++ b/drivers/gpu/drm/drm_crtc.c
> @@ -340,6 +340,8 @@ int drm_crtc_init_with_planes(struct drm_device *dev, struct drm_crtc *crtc,
>   		drm_object_attach_property(&crtc->base, config->prop_mode_id, 0);
>   		drm_object_attach_property(&crtc->base,
>   					   config->prop_out_fence_ptr, 0);
> +		drm_object_attach_property(&crtc->base,
> +					   config->prop_vrr_enabled, 0);
>   	}
>   
>   	return 0;
> diff --git a/drivers/gpu/drm/drm_mode_config.c b/drivers/gpu/drm/drm_mode_config.c
> index ee80788f2c40..5670c67f28d4 100644
> --- a/drivers/gpu/drm/drm_mode_config.c
> +++ b/drivers/gpu/drm/drm_mode_config.c
> @@ -310,6 +310,12 @@ static int drm_mode_create_standard_properties(struct drm_device *dev)
>   		return -ENOMEM;
>   	dev->mode_config.prop_mode_id = prop;
>   
> +	prop = drm_property_create_bool(dev, 0,
> +			"VRR_ENABLED");
> +	if (!prop)
> +		return -ENOMEM;
> +	dev->mode_config.prop_vrr_enabled = prop;
> +
>   	prop = drm_property_create(dev,
>   			DRM_MODE_PROP_BLOB,
>   			"DEGAMMA_LUT", 0);
> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> index b21437bc95bf..39c3900aab3c 100644
> --- a/include/drm/drm_crtc.h
> +++ b/include/drm/drm_crtc.h
> @@ -290,6 +290,15 @@ struct drm_crtc_state {
>   	 */
>   	u32 pageflip_flags;
>   
> +	/**
> +	 * @vrr_enabled:
> +	 *
> +	 * Indicates if variable refresh rate should be enabled for the CRTC.
> +	 * Support for the requested vrr state will depend on driver and
> +	 * hardware capabiltiy - lacking support is not treated as failure.
> +	 */
> +	bool vrr_enabled;
> +
>   	/**
>   	 * @event:
>   	 *
> diff --git a/include/drm/drm_mode_config.h b/include/drm/drm_mode_config.h
> index 928e4172a0bb..49f2fcfdb5fc 100644
> --- a/include/drm/drm_mode_config.h
> +++ b/include/drm/drm_mode_config.h
> @@ -639,6 +639,11 @@ struct drm_mode_config {
>   	 * connectors must be of and active must be set to disabled, too.
>   	 */
>   	struct drm_property *prop_mode_id;
> +	/**
> +	 * @prop_vrr_enabled: Default atomic CRTC property to indicate
> +	 * whether variable refresh rate should be enabled on the CRTC.
> +	 */
> +	struct drm_property *prop_vrr_enabled;
>   
>   	/**
>   	 * @dvi_i_subconnector_property: Optional DVI-I property to

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-10-13 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 16:44 [PATCH v5 0/4] A DRM API for adaptive sync and variable refresh rate support Nicholas Kazlauskas
2018-10-12 16:44 ` [PATCH v5 1/4] drm: Add vrr_capable property to the drm connector Nicholas Kazlauskas
     [not found]   ` <20181012164458.12864-2-nicholas.kazlauskas-5C7GfCeVMHo@public.gmane.org>
2018-10-25 18:05     ` Wentland, Harry
2018-10-12 16:44 ` [PATCH v5 2/4] drm: Add vrr_enabled property to drm CRTC Nicholas Kazlauskas
2018-10-13 17:38   ` Christian König [this message]
     [not found]     ` <e1feafbe-2c37-d1ff-8a45-4672b4da1264-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-10-15  9:40       ` Michel Dänzer
     [not found]         ` <9811fdab-3efe-4701-92e1-0f53b323959d-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-10-15  9:47           ` Christian König
     [not found]             ` <c9afd2f9-c80c-3147-6458-14e386196fb7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-10-15 10:06               ` Michel Dänzer
     [not found]                 ` <ec5d531d-e91a-ba2f-7e8e-4a875b183e97-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-10-15 10:47                   ` Koenig, Christian
2018-10-26 14:27                   ` Pekka Paalanen
2018-10-25 18:08   ` Wentland, Harry
2018-10-12 16:44 ` [PATCH v5 3/4] drm: Document variable refresh properties Nicholas Kazlauskas
     [not found]   ` <20181012164458.12864-4-nicholas.kazlauskas-5C7GfCeVMHo@public.gmane.org>
2018-10-25 18:13     ` Wentland, Harry
2018-10-12 16:44 ` [PATCH v5 4/4] drm/amdgpu: Set FreeSync state using drm VRR properties Nicholas Kazlauskas
2018-10-25 18:22   ` Wentland, Harry

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=e1feafbe-2c37-d1ff-8a45-4672b4da1264@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Marek.Olsak@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=manasi.d.navare@intel.com \
    --cc=michel@daenzer.net \
    --cc=nicholas.kazlauskas@amd.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