From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bali.collaboradmins.com (bali.collaboradmins.com [148.251.105.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B859721FF47 for ; Mon, 16 Feb 2026 01:18:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=148.251.105.195 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771204720; cv=none; b=CMxCdSnSPNWI36jynPPn1LERbIuwMViByQw7FtkYrIdl236AGraXN8dmBB1Nc3CgJxzISe9R+AAyIvZKafZgWDQ1OUvEXCa8MToTTLRWhniRPhqZhd1BL4oy34aDXWOa0vF53ksNJetcCFJ6vBmNBIqjMLKbuyBZMdU7CIKUL5Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771204720; c=relaxed/simple; bh=Vt1/GO5k/RzR8SVs8wPxGoQATAh8Up3BHfZKh9BhnVg=; h=Message-ID:Date:MIME-Version:Subject:To:References:From: In-Reply-To:Content-Type; b=fjCxDMd0NbM6astu9St3ejiZWr8QA7Rv6T0JAzSt+aNBdUKY7ZVdwNxMgMK8ubojBs6VOQDRVAukmd/O2ijw6/b+OOJ2Oc35xdi3JU+Xf8WgYqMgEy2UwqvukYzSjbyuwEIQtuhHlOmAJLz3Q1tGDnPVccAL/UViOMNHyeZftP4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com; spf=pass smtp.mailfrom=collabora.com; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b=eq3t9Fg9; arc=none smtp.client-ip=148.251.105.195 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="eq3t9Fg9" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1771204710; bh=Vt1/GO5k/RzR8SVs8wPxGoQATAh8Up3BHfZKh9BhnVg=; h=Date:Subject:To:References:From:In-Reply-To:From; b=eq3t9Fg9j5TPlGkXwiQnKGt9JEj3U5C/5dC/FVAYZAhJ5L9U6aPV/i7Em/D5U6tOU C2PsBO7k8K/gZ14Xe09Q2HredKVuWX+eKWfmE5qlIzNnG8qLgXKKPFhfxcy3NFQBOu GQ6LRzSwzSdcTVJ4wYig21QQimje8kNwsjl8yKEJtjBLfQCrnMB6xtPhLkqxq0WJMT czE8fkVJ+b23mK1xRKAuDWHAsPI6vw1OjdMaVJKxnSwdTvcX4BSO6FQMOt7bNjBX8z 99oghpZNQz5YNjYV+je9kHJi31aKIBXeI5wfJiY60QG2mu09klxprxUNTyMkp8DcO2 HSugaCoF6bNGw== Received: from [192.168.1.90] (unknown [82.79.138.145]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: cristicc) by bali.collaboradmins.com (Postfix) with ESMTPSA id 6034617E012E; Mon, 16 Feb 2026 02:18:30 +0100 (CET) Message-ID: <98e46dbb-c8e2-451f-accb-ea48f63f9408@collabora.com> Date: Mon, 16 Feb 2026 03:18:29 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [REGRESSION] HDMI monitor not working on Radxa Rock 5B after phy rockchip samsung hdptx HDMI 2.1 FRL patchset To: dubito@online.de, Vinod Koul , Neil Armstrong , Heiko Stuebner , 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 References: <8e410a11-bd7b-4a12-a711-0514a59409c0@collabora.com> <1859c940219a4dbfdf0497afbf333e627ab0ba25.camel@online.de> Content-Language: en-US From: Cristian Ciocaltea In-Reply-To: <1859c940219a4dbfdf0497afbf333e627ab0ba25.camel@online.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Thomas, On 2/14/26 12:00 AM, Thomas Niederprüm wrote: > Hi Cristian, > > > Am Freitag, dem 13.02.2026 um 00:04 +0200 schrieb Cristian Ciocaltea: >> Hi Thomas, >> >> On 2/11/26 11:20 PM, Thomas Niederprüm wrote: >>> Hi, >>> >>> I'm running a Radxa Rock 5B (rk3588) on a 10+ year old Samsung TV screen >>> connected via HDMI. This worked flawlessly in 6.18.7 but does not work on >>> linux- >>> next. I bisected the problem and identified commit 3481fc04 to be the first >>> bad >>> commit. This points to the phy PLL clock rate calculation to be the problem >>> in >>> connection with my monitor. As it seems relevant, I attached the EDID of my >>> monitor. >>> >>> I'm booting the kernel out of EDK2 after which efifb is correctly taking >>> over >>> the initialized display and I can see the initial kernel boot messages on >>> the >>> HDMI output. After the drm/kms in the kernel takes over the screen shortly >>> turns >>> black, changes resolution, and then correctly displays on 6.18.7. However, >>> in >>> linux-next the screen remains black after kms took over. I cannot see any >>> obvious differences in the boot logs but I attached two boot logs, one for >>> the >>> working 6.18.7 kernel and one for the non-working linux-next kernel. >>> >>> When reverting 3481fc04..de5dba83 (i.e. the faulty commit and the ones that >>> followed in the HDMI 2.1 FRL series) I can build a working kernel from >>> linux- >>> next. >>> >>> I don't know where to dig from here but I'm happy to run any test necessary >>> to >>> track down the problem. >> >> It'd be helpful if you could resend the logs after booting both kernels with >> the >> following params (requires CONFIG_DYNAMIC_DEBUG=y): >> >> rockchipdrm.dyndbg=+p dw_hdmi_qp.dyndbg=+p >> phy_rockchip_samsung_hdptx.dyndbg=+p >> >> As well as running the command below before connecting your display/TV: >> >> $ echo 0x4 > /sys/module/drm/parameters/debug >> >> I've noticed you're forcing "video=HDMI-A-1:1920x1080M@60", which should be >> anyway the preferred mode (according to the EDID). > > I dumped the kernel messages for a freshly built v6.19 and a linux-next image. > For each kernel I booted with the suggested debug options and forcing the modes > 1920x1080@60, 1920x1080@50, 1920x1080@30. The boot logs are attached. For v6.19 > all modes work. Running linux-next, 1920x1080@60 and 1920x1080@50 don't work but > 1920x1080@30 works. > >> Did you try choosing a different one, e.g. 1920x1080@50 or 1920x1080@30 (they >> are supported according to the listing in CTA-861 Extension Block). That's >> more >> a test to confirm the issue affects a particular modeline, or is more general. >> > > As stated above, if I force 1920x1080@30 the screen turns on in linux-next. > 1920x1080@60 and 1920x1080@50 don't work. This points to something specific to > the modeline. > > By diff'ing the relevant part of the logs between kernels one can see that in > the cases where the screen stays black the log lacks the following lines: > > rockchip-hdptx-phy fed60000.phy: rk_hdptx_ropll_tmds_cmn_config > rate=185625000 mdiv=155 sdiv=4 sdm_en=1 k_sign=1 k=16 lc=62 > rockchip-hdptx-phy fed60000.phy: PHY clk ready > > So obviously the PHY clock never gets ready. > > I also attached the diffs I made. Thanks for checking this out! The behavior is really unexpected and I'm still unable to reproduce on my end, i.e. even tested with a Samsung TV, which is almost as old as yours: # Mine Vendor & Product Identification: Manufacturer: SAM Model: 2685 Serial Number: 1 (0x00000001) Made in: week 46 of 2012 # Yours Vendor & Product Identification: Manufacturer: SAM Model: 1641 Serial Number: 1 (0x00000001) Made in: week 47 of 2009 I added some more debug information, hence could you please apply commit [1] on your next-20260213 kernel and share the logs after testing again the 1920x1080@50 and 1920x1080@30 modes? [1] https://gitlab.collabora.com/cristicc/linux-next/-/commit/2ce4b1fb60fc601068abbe9131c05c4f09f1380c Regards, Cristian