From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: dubito@online.de, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] HDMI monitor not working on Radxa Rock 5B after phy rockchip samsung hdptx HDMI 2.1 FRL patchset
Date: Wed, 18 Feb 2026 22:56:52 +0200 [thread overview]
Message-ID: <a662745a-1b2a-47b3-a66d-7c1c5c8af525@collabora.com> (raw)
In-Reply-To: <a3c3964e9e13c82d944fa1ee0acbb1a7806dd382.camel@online.de>
Hi Thomas,
On 2/18/26 10:43 PM, 1und1 wrote:
> Hi Cristian,
>
>
> Am Mittwoch, dem 18.02.2026 um 22:15 +0200 schrieb Cristian Ciocaltea:
>> On 2/18/26 3:22 AM, Cristian Ciocaltea wrote:
>>> On 2/18/26 2:52 AM, Cristian Ciocaltea wrote:
>>>> Hi Thomas,
>>> [...]
>>>
>>>>
>>>> Sorry, I somehow missed the following warning message, though it has been
>>>> already present in all the logs you've sent to me so far:
>>>>
>>>> rockchip-hdptx-phy fed60000.phy: PLL locked by unknown consumer!
>>>>
>>>> That indicates the PHY has been preconfigured by an external component
>>>> (e.g. the
>>>> bootloader), which is actually a scenario that I didn't verify.
>>>>
>>>> However, this just another way to expose a limitation of the current
>>>> approach
>>>> for managing the TMDS character rate: done via the Common Clock Framework
>>>> API
>>>> instead of the HDMI PHY configuration API.
>>>>
>>>> As a matter of fact, it was actually an item on my TODOs list for quite a
>>>> while,
>>>> but blocked until recently due to several dependencies waiting to be
>>>> merged
>>>> upstream.
>>>>
>>>> Hence I took the opportunity to finalize this task - please give the
>>>> following
>>>> commits in my rk3588-hdmi-debug branch [2] a try:
>>>
>>> I've just realized I introduced a regression while doing some cleanup work,
>>> hence
>>> please ignore this until further notice.
>>
>> I think I got this working properly now, at least it passes all the tests I
>> could run. The updated commits in [2] are:
>>
>> fa7cd1e75aaa ("phy: rockchip: samsung-hdptx: Fix rate recalculation for high
>> bpc")
>> 8048db5544da ("phy: rockchip: samsung-hdptx: Exclusively use PHY config API
>> for PLL changes")
>> 0085a382dfd0 ("[DEBUG] drm/rockchip: Add HDMI verbose logging")
>>
>
> applying these commits solves my problems. I tested 1920x1080@60, 1920x1080@50
> and 1920x1080@30. All work now. Thanks for the quick fix!
Thanks for the quick test!
I can add you to cc: when I submit the series, so that you may provide your
Tested-by tag if you'd like to.
> And the positive side> effect seems to be that you can now take one of your
> old todos from your list.
Indeed. :-)
Regards,
Cristian
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-02-18 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 21:20 [REGRESSION] HDMI monitor not working on Radxa Rock 5B after phy rockchip samsung hdptx HDMI 2.1 FRL patchset Thomas Niederprüm
2026-02-12 22:04 ` Cristian Ciocaltea
[not found] ` <1859c940219a4dbfdf0497afbf333e627ab0ba25.camel@online.de>
2026-02-16 1:18 ` Cristian Ciocaltea
2026-02-16 10:48 ` Thomas Niederprüm
2026-02-18 0:52 ` Cristian Ciocaltea
2026-02-18 1:22 ` Cristian Ciocaltea
2026-02-18 20:15 ` Cristian Ciocaltea
2026-02-18 20:43 ` 1und1
2026-02-18 20:56 ` Cristian Ciocaltea [this message]
2026-02-21 15:05 ` Thomas Niederprüm
2026-02-28 0:19 ` Cristian Ciocaltea
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=a662745a-1b2a-47b3-a66d-7c1c5c8af525@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=dubito@online.de \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox