From: Dianne Skoll <dianne@skoll.ca>
To: Jaak Ristioja <jaak@ristioja.ee>
Cc: "Mario Limonciello" <mario.limonciello@amd.com>,
"Salvatore Bonaccorso" <carnil@debian.org>,
"Chris Park" <chris.park@amd.com>,
"Matthew Stewart" <matthew.stewart2@amd.com>,
"Dan Wheeler" <daniel.wheeler@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
1139950@bugs.debian.org, regressions@lists.linux.dev,
stable@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [resend] [regression] amdgpu carrizo: no display signal after modeset
Date: Mon, 22 Jun 2026 15:34:49 -0400 [thread overview]
Message-ID: <20260622153449.453b493e@gato.skoll.ca> (raw)
In-Reply-To: <6cf6be99-76c3-43b3-854f-96cae180318c@ristioja.ee>
On Mon, 22 Jun 2026 20:46:44 +0300
Jaak Ristioja <jaak@ristioja.ee> wrote:
> Reverting commit fee50077656 ("drm/amd/display: Bump the HDMI clock to
> 340MHz") on top of v7.1.1 appears to resolve the issue, as I am now able
> to get a picture.
Unfortunately, reverting that commit will *break* it for me with my Dasung
E-Ink monitor. :(
If it's not possible to detect what the maximum HDMI clock should be, perhaps
a module parameter specifying the HDMI version could be implemented? Or
a parameter to specify the maximum HDMI clock directly?
Regards,
Dianne.
next prev parent reply other threads:[~2026-06-22 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9fba2020-24d1-4235-9869-319d4aab3a4c@ristioja.ee>
2026-06-20 20:11 ` Salvatore Bonaccorso
2026-06-20 21:52 ` [resend] " Salvatore Bonaccorso
2026-06-21 7:39 ` Mario Limonciello
2026-06-22 13:52 ` Jaak Ristioja
2026-06-22 17:46 ` Jaak Ristioja
2026-06-22 19:34 ` Dianne Skoll [this message]
2026-07-13 7:13 ` Thorsten Leemhuis
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=20260622153449.453b493e@gato.skoll.ca \
--to=dianne@skoll.ca \
--cc=1139950@bugs.debian.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=carnil@debian.org \
--cc=chris.park@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.wheeler@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=harry.wentland@amd.com \
--cc=jaak@ristioja.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=matthew.stewart2@amd.com \
--cc=regressions@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=stable@vger.kernel.org \
--cc=sunpeng.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome