All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pei-Hsin Yang <peihsiny@valvesoftware.com>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>
Cc: "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: RE: [External Mail] Re: Test result / finding of "drm/amd/display: Consult MCCS FreeSync cap only if requested & supported"
Date: Tue, 26 May 2026 15:04:42 +0000	[thread overview]
Message-ID: <17aabac2d51c411c8e9aa230d799ab49@valvesoftware.com> (raw)
In-Reply-To: <1fb98dd3-55fd-4269-91bd-292b1167718b@mailbox.org>

> In the future, please send patches inline, to make giving feedback easier.

Will do.  Thanks.

> vsdb_info.freesync_supported already guards setting freesync_capable = true in the first place (given either of the other two conditions) above, so this if-statement looks superfluous now.

Yes, if hardware detection via MCCS VCP Code read is not preferred, then this if-statement can be removed.

-----Original Message-----
From: Michel Dänzer <michel.daenzer@mailbox.org> 
Sent: Tuesday, May 26, 2026 6:55 AM
To: Pei-Hsin Yang <peihsiny@valvesoftware.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [External Mail] Re: Test result / finding of "drm/amd/display: Consult MCCS FreeSync cap only if requested & supported"

On 5/23/26 00:15, Pei-Hsin Yang wrote:
>> Note that some kind of short-term solution is needed for the regression(s) in 7.1-rc.
> 
> Here is my suggestion as a short-term workaround:  
> 	- Just refer to the vsdb_info data structure to set the value of freesync_capable.  freesync_mccs_vcp_code = 0 doesn't mean FreeSync is not supported.
> 	- Check both freesync_supported and freesync_mccs_vcp_code along with do_mccs to call dm_helpers_mccs_vcp_set().
> 	- Note that MCCS command over DDC might be failed at runtime, but at least, it will not inadvertently disable the VRR if (1) sink is FreeSync supported but vcp_code = 0, or (2) dm_helpers_read_mccs_cap() failed intermittently at runtime.
> 
> Patch created based on commit 53f0235c0284fc676d1510a460e1c6c111de3ea1 is attached as a reference for AMD team to review.
> 
> commit 53f0235c0284fc676d1510a460e1c6c111de3ea1 (HEAD -> amd-staging-drm-next, origin/amd-staging-drm-next, origin/HEAD)

In the future, please send patches inline, to make giving feedback easier.


> @@ -13680,11 +13680,10 @@ void amdgpu_dm_update_freesync_caps(struct drm_connector *connector,
> 
>         if ((sink->sink_signal == SIGNAL_TYPE_HDMI_TYPE_A ||
>                 as_type == FREESYNC_TYPE_PCON_IN_WHITELIST) &&
> -               (!sink->edid_caps.freesync_vcp_code ||
> -               (sink->edid_caps.freesync_vcp_code && !sink->mccs_caps.freesync_supported)))
> +               (!vsdb_info.freesync_supported))
>                 freesync_capable = false;

vsdb_info.freesync_supported already guards setting freesync_capable = true in the first place (given either of the other two conditions) above, so this if-statement looks superfluous now.


-- 
Earthling Michel Dänzer       \        GNOME / Xwayland / Mesa developer
https://redhat.com             \               Libre software enthusiast


  reply	other threads:[~2026-05-27  7:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 20:12 Test result / finding of "drm/amd/display: Consult MCCS FreeSync cap only if requested & supported" Pei-Hsin Yang
2026-05-20  7:49 ` Michel Dänzer
2026-05-20 15:54   ` [External Mail] " Pei-Hsin Yang
2026-05-21  7:09     ` Michel Dänzer
2026-05-22 22:15       ` Pei-Hsin Yang
2026-05-26 13:55         ` Michel Dänzer
2026-05-26 15:04           ` Pei-Hsin Yang [this message]
2026-05-28 11:17       ` Thorsten Leemhuis
2026-05-28 22:02         ` Deucher, Alexander
2026-06-04  7:42           ` Michel Dänzer
2026-06-04 13:20             ` Alex Deucher
2026-06-04 13:58               ` Michel Dänzer
2026-06-04 17:21                 ` [External Mail] " Pei-Hsin Yang
2026-06-05  7:42                   ` Michel Dänzer
2026-06-05 14:43                     ` Alex Deucher

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=17aabac2d51c411c8e9aa230d799ab49@valvesoftware.com \
    --to=peihsiny@valvesoftware.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=michel.daenzer@mailbox.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 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.