From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Gergo Koteles <soyer@irl.hu>
Cc: Dmitry Baryshkov <dbaryshkov@gmail.com>,
Dmitry Baryshkov <lumag@kernel.org>,
regressions@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
Hans de Goede <hdegoede@redhat.com>,
Alex Deucher <alexander.deucher@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Alex Hung <alex.hung@amd.com>,
Harry Wentland <harry.wentland@amd.com>
Subject: Re: amdgpu_dm_connector_mode_valid regression
Date: Thu, 24 Apr 2025 10:48:02 +0200 [thread overview]
Message-ID: <aAn6wsnJ-6mqK4vR@mail-itl> (raw)
In-Reply-To: <Z_jodBrNFdEpJRKA@mail-itl>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Fri, Apr 11, 2025 at 12:01:28PM +0200, Marek Marczykowski-Górecki wrote:
>
> Hi,
>
> On Wed, Apr 02, 2025 at 04:35:05PM +0200, Gergo Koteles wrote:
> > Hi Dmitry,
> >
> > But the code would start to become quite untraceable.
> > duplicate mode in amdgpu_dm_connector_mode_valid()
> > call drm_mode_set_crtcinfo() in amdgpu_dm_connector_mode_valid()
> > duplicate mode in create_stream_for_sink()
> > overwrite ctrc in decide_crtc_timing_for_drm_display_mode()
> > if crtc_clock == 0 call drm_mode_set_crtcinfo() again in
> > create_stream_for_sink()
>
> FWIW I'm affected by the same issue (on HP ProBook 445 G7, with AMD
> Ryzen 5 4500U). And the patch quoted below fixes it for me too.
I've re-tested it with 6.15-rc3 and the issue is still there. Is there
something I can do to help fixing it before final 6.15 is out?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-24 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 10:40 Gergo Koteles
2025-04-02 12:00 ` Gergo Koteles
2025-04-02 13:36 ` Dmitry Baryshkov
2025-04-02 14:35 ` Gergo Koteles
2025-04-02 14:40 ` Dmitry Baryshkov
2025-04-02 15:00 ` Gergo Koteles
2025-04-11 10:01 ` Marek Marczykowski-Górecki
2025-04-24 8:48 ` Marek Marczykowski-Górecki [this message]
2025-04-24 9:06 ` Gergo Koteles
2025-04-24 13:12 ` 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=aAn6wsnJ-6mqK4vR@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dbaryshkov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
--cc=soyer@irl.hu \
/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
all inboxes | Powered by JetHome®