All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] Adjustments to common mode behavior
Date: Wed, 24 Sep 2025 19:13:06 +0200	[thread overview]
Message-ID: <29cbab3f-083a-41a8-81a1-b0234f36152f@gmail.com> (raw)
In-Reply-To: <20250924161624.1975819-1-mario.limonciello@amd.com>



On 9/24/25 18:16, Mario Limonciello wrote:
> As part of enablement for SI and CIK in DC Timur pointed out some
> differences in behavior for common mode handling for DC vs non DC
> code paths. This series lines up the behavior between the two
> implementations.
> 
Reviewed-by: Timur Kristóf <timur.kristof@gmail.com>

Thank you Mario, this series makes good sense to me.
My only worry is this: is it possible that removing the common modes 
from connectors like DP, HDMI, etc. will regress somebody's setup?

Two possible cases come to mind:
1. When we are unable to read the EDID for some reason
2. When the EDID is buggy and/or doesn't contain any modes
Are these issues real or am I overthinking it?

Thanks & best regards,
Timur

  parent reply	other threads:[~2025-09-24 17:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 16:16 [PATCH 0/5] Adjustments to common mode behavior Mario Limonciello
2025-09-24 16:16 ` [PATCH 1/5] drm/amd/display: Only enable common modes for eDP and LVDS Mario Limonciello
2025-09-24 17:58   ` Harry Wentland
2025-09-24 16:16 ` [PATCH 2/5] drm/amd: Drop unnecessary check in amdgpu_connector_add_common_modes() Mario Limonciello
2025-09-24 16:16 ` [PATCH 3/5] drm/amd: Use dynamic array size declaration for amdgpu_connector_add_common_modes() Mario Limonciello
2025-09-24 17:05   ` Alex Deucher
2025-09-24 16:16 ` [PATCH 4/5] drm/amd: Drop some common modes from amdgpu_connector_add_common_modes() Mario Limonciello
2025-09-24 16:16 ` [PATCH 5/5] drm/amd: Add name to " Mario Limonciello
2025-09-24 17:07   ` Alex Deucher
2025-09-24 17:13 ` Timur Kristóf [this message]
2025-09-24 17:21   ` [PATCH 0/5] Adjustments to common mode behavior Mario Limonciello
2025-09-24 17:33     ` Timur Kristóf
2025-09-24 17:48       ` Mario Limonciello
2025-09-24 18:11         ` Timur Kristóf
2025-09-24 18:31           ` Mario Limonciello
2025-09-24 21:04             ` Timur Kristóf
2025-09-24 18:24         ` Harry Wentland
2025-09-24 19:11           ` Alex Deucher
2025-09-24 20:00             ` Harry Wentland
2025-09-24 20:07               ` 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=29cbab3f-083a-41a8-81a1-b0234f36152f@gmail.com \
    --to=timur.kristof@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=mario.limonciello@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 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.