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 2C9AC38734D for ; Wed, 2 Sep 2026 18:00:56 +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=1788372058; cv=none; b=NPcMMPmjCYhViG+69jZ+4My/ZvjS06qqHdKDDZjF1uRM5XmreVoiu+GgEeVhqmnhz/gvoqGb73XX/PE/CZCCmSBv634O1l34OG4B8LDhv0j0lOQ3sIJ+bgUYZj2w5m4wuYMIt07Nh50h0e6BqiACgLaRZnGAEfptSnPPtmLwPm8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788372058; c=relaxed/simple; bh=RFGuLr+hSZX4q95E8FmOb9I0Oj/VY5jMv/JY+fIYb70=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=ciUfsMOY5FNtvqateYUwcxgLazv5S4rcfeU0Wde5Sv33Tx48JRp9c9BIdETvezUiU9LRQe8drMRjqCin8y3Uu8dDF1RtefgROLSojaNlTfMy81c6UxusTyNZy9PfNAoUYVinabKHu2I/kgMQY2HUrem7XgGMSXCyQWVrJiXh/hA= 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=kM8qFYh5; 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="kM8qFYh5" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1788372054; bh=RFGuLr+hSZX4q95E8FmOb9I0Oj/VY5jMv/JY+fIYb70=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=kM8qFYh5ALIzTeH3UbstMxl+7wLpe4Bu2oDWFRouwXe8W1lQ2GcXh+oO+gqLoidmZ HQMSqjKsWcNXbvTSuuxlb1faCUJMb8G8Q2KjH+S5nlOxiyhKfua21QDEf3ybTPMDn/ 3kJolpG+4VJaUhI1Prg5LGUz+oDvMBVHfkRpy3tPaE4Oc2xDfbl3QO4+RJPRPqQXJx E+FrN7SHhoB92fRWYYh9euh+0JLQRU4+nvzQNDFtaktWHWuZv56boO33PhpQou+Bnp oJwFxRsjPWxC2hXEzrUrOBvYHt84IFXkSAraUfM8Nohm2jmh7IyExwzXcC9rsQspUj tbeVQmjFUg3PA== Received: from [100.64.0.241] (unknown [100.64.0.241]) (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 C7E3417E0260; Wed, 02 Sep 2026 20:00:53 +0200 (CEST) Message-ID: Date: Wed, 2 Sep 2026 21:00:53 +0300 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: [PATCH v11 00/74] Add HDMI 2.0 support to DW HDMI QP TX To: Igor Paunovic Cc: Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Dave Stevenson , Dmitry Baryshkov , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Luca Ceresoli , Chen-Yu Tsai , Samuel Holland , mcanal@igalia.com, Raspberry Pi Kernel Maintenance , Raphael Gallais-Pou , Sandy Huang , Heiko Stuebner , Andy Yan , Algea Cao , Daniel Stone , Liu Ying , Phong LE , Helge Deller , kernel@collabora.com, Dmitry Baryshkov , Diederik de Haas , Maud Spierings , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org References: <20260901-dw-hdmi-qp-scramb-v11-0-bc12954a0688@collabora.com> <20260902152838.5771-1-royalnet026@gmail.com> Content-Language: en-US From: Cristian Ciocaltea In-Reply-To: <20260902152838.5771-1-royalnet026@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi Igor, On 9/2/26 6:28 PM, Igor Paunovic wrote: > Hi Cristian, > >> This has been tested on the following boards: > > One more, with a sink pair your boards cannot cover: > > Tested-by: Igor Paunovic # RK3588 Orange Pi 5 Plus, dual HDMI > > Setup: whole v11 on its stated base (drm-misc-next 47b823940e38), > both SoC HDMI ports driven at once: a Samsung with HF-VSDB (max > TMDS character rate 600 MHz, SCDC present) and a Sony limited to > 300 MHz TMDS. > > 1) HDMI 2.0 path: the Samsung now offers and runs 3840x2160@60 RGB > with a 594 MHz pixel clock (modetest-confirmed). Without the > series the same port tops out at 4K@30. A stable picture at > 594 MHz is only possible with scrambling and the 1/40 TMDS ratio > active; it stayed stable across boot, mode changes and hotplug. > > 2) Non-2.0 fallback: the Sony keeps its 297 MHz 4K@30 modes. > No regression. > > 3) The result I care most about: this Sony in standby keeps EDID/5V > up but drops the link, and on my 7.2 stack that generates a > storm of detect/modeset cycles - measured 119-194 per hour, > enough to make the desktop stutter. On v11, twenty minutes of > standby produced ZERO events, and wake restored both sinks by > itself. Whatever share of that the cached-status detect and the > SCDC-loss handling each take - thank you. > > 4) Hotplug on both ports: clean detach and reattach, no storms. > > 5) Audio on a dead link: this morning my 7.2 stack took an SError > panic (regmap read in dw_hdmi_qp_bridge_clear_audio_infoframe > when a PCM was closed on a link whose SCDC never came up - full > UART trace available if useful). On v11 I could not reproduce > the class: six open/close cycles against the standby sink plus > one natural prepare-failure-then-close during replug all > survived cleanly. Caveat: different base kernels, so this is > not a clean A/B on the series alone. Thanks for the detailed testing report! > Scope: RGB output only (the YUV420 output series is separate), no > USB-C DP on this base, VC4 side not exercised. I will manually apply your T-b on the relevant patches before submitting a new revision. Cristian