From: Jani Nikula <jani.nikula@linux.intel.com>
To: Manasi Navare <manasi.d.navare@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Harry Wentland <harry.wentland@amd.com>,
Nicholas Kazlauskas <Nicholas.Kazlauskas@amd.com>
Subject: Re: [Intel-gfx] [PATCH 2/3] drm: Create a drm_connector_helper_funcs hook for Adaptive Sync support
Date: Thu, 19 Mar 2020 12:07:37 +0200 [thread overview]
Message-ID: <87y2rwd5ee.fsf@intel.com> (raw)
In-Reply-To: <20200318063517.3844-2-manasi.d.navare@intel.com>
On Tue, 17 Mar 2020, Manasi Navare <manasi.d.navare@intel.com> wrote:
> This patch adds a hook in drm_connector_helper_funcs to get the
> support of the driver for adaptive sync functionality.
>
> This can be called in the connector probe helper function after
> the connector detect() and get_modes() hooks to also
> query the adaptive sync support of the driver.
I can obviously see that from the patch. But this does not explain at
all *why* we need another hook to begin with, and why it neeeds to be
called from ->fill_modes that is set to
drm_helper_probe_single_connector_modes().
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Nicholas Kazlauskas <Nicholas.Kazlauskas@amd.com>
> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> ---
> drivers/gpu/drm/drm_probe_helper.c | 4 ++++
> include/drm/drm_modeset_helper_vtables.h | 16 ++++++++++++++++
> 2 files changed, 20 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_probe_helper.c b/drivers/gpu/drm/drm_probe_helper.c
> index 576b4b7dcd89..4403817bfb02 100644
> --- a/drivers/gpu/drm/drm_probe_helper.c
> +++ b/drivers/gpu/drm/drm_probe_helper.c
> @@ -482,6 +482,10 @@ int drm_helper_probe_single_connector_modes(struct drm_connector *connector,
>
> count = (*connector_funcs->get_modes)(connector);
>
> + /* Get the Adaptive Sync Support if helper exists */
> + if (*connector_funcs->get_adaptive_sync_support)
> + (**connector_funcs->get_adaptive_sync_support)(connector);
> +
This is in the middle of a sequence figuring out the modes. First
->get_modes, then fallback to other mechanisms. Certainly we don't want
to do something else in the middle.
> /*
> * Fallback for when DDC probe failed in drm_get_edid() and thus skipped
> * override/firmware EDID.
> diff --git a/include/drm/drm_modeset_helper_vtables.h b/include/drm/drm_modeset_helper_vtables.h
> index 7c20b1c8b6a7..0b203fdd25df 100644
> --- a/include/drm/drm_modeset_helper_vtables.h
> +++ b/include/drm/drm_modeset_helper_vtables.h
> @@ -1079,6 +1079,22 @@ struct drm_connector_helper_funcs {
> struct drm_writeback_job *job);
> void (*cleanup_writeback_job)(struct drm_writeback_connector *connector,
> struct drm_writeback_job *job);
> +
> + /**
> + * @get_adaptive_sync_support:
> + *
> + * This hook is used by the probe helper to get the driver's support
> + * for adaptive sync or variable refresh rate.
> + * This is called from drm_helper_probe_single_connector_modes()
> + * This is called after the @get_modes hook so that the connector modes
> + * are already obtained and EDID is parsed to obtain the monitor
> + * range descriptor information.
> + *
> + * This hook is optional and defined only for the drivers and on
> + * connectors that advertise adaptive sync support.
> + *
> + */
> + void (*get_adaptive_sync_support)(struct drm_connector *connector);
> };
>
> /**
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-19 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 6:35 [Intel-gfx] [PATCH 1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD Manasi Navare
2020-03-18 6:35 ` [Intel-gfx] [PATCH 2/3] drm: Create a drm_connector_helper_funcs hook for Adaptive Sync support Manasi Navare
2020-03-18 13:42 ` Harry Wentland
2020-03-19 10:07 ` Jani Nikula [this message]
2020-03-19 22:39 ` Manasi Navare
2020-03-18 6:35 ` [Intel-gfx] [PATCH 3/3] drm/i915/dp: intel_dp connector hook for VRR support Manasi Navare
2020-03-19 10:14 ` Jani Nikula
2020-03-19 22:35 ` Manasi Navare
2020-03-18 7:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/dp: DRM DP helper for reading Ignore MSA from DPCD Patchwork
2020-03-18 7:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-18 10:00 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-03-19 9:59 ` [Intel-gfx] [PATCH 1/3] " Jani Nikula
2020-03-19 22:46 ` Manasi Navare
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=87y2rwd5ee.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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