amdgpu_dm_connector_mode_valid regression
Alex Deucher
alexdeucher at gmail.com
Thu Apr 24 13:12:13 UTC 2025
On Thu, Apr 24, 2025 at 4:49 AM Marek Marczykowski-Górecki
<marmarek at invisiblethingslab.com> wrote:
>
> 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?
I believe this should be fixed in this patch which is already in this
week's -fixes PR:
https://gitlab.freedesktop.org/agd5f/linux/-/commit/b316727a27d0dac1e6b7ae51204df4d0f241fcc2
Alex
>
> --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
More information about the amd-gfx
mailing list