From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A155AC43458 for ; Sun, 5 Jul 2026 22:20:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:References:Cc:To :From:Subject:Message-Id:Date:Content-Type:Content-Transfer-Encoding: Mime-Version:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=XzP4IrwF64OOqXOnzQR9aMpiMXv9vAON16c9GzABhuU=; b=lVRPvJiqrxqdvYCx8niIDdFg1+ ycOXXo+Ft98A/ghluGckkeX0ox0y/vUf4GdioOG7IiyYUZbZ0rd7nz+x4DUQLTdGjQj51aXKry+mm YdofGRQ+/Fo5l2Wpd9zeQhVgN8zOhqctl6jcZJnvQqBKd/wdOxQ4619wrNvYO7WNd10K4qhFpazrk sE+nYjzEzjeFJEwqLBZb75Nb6j5PmhBCQjF6YQ4siuadfWDIrx+XRmIp9NAndqR1vaDHItBskqDPj VnF7+5pQbdGkOnwNII3Vic+SL11MDYseSNrXWbe6lvjwFMzH/jN6YjE3UlfmqFSy9KEJEnieI1PxJ 5U2l+sPg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wgVCO-0000000ADyN-0uoX; Sun, 05 Jul 2026 22:20:28 +0000 Received: from out-189.mta0.migadu.com ([2001:41d0:1004:224b::bd]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wgVCK-0000000ADwI-475b for linux-arm-kernel@lists.infradead.org; Sun, 05 Jul 2026 22:20:26 +0000 Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow-tech.com; s=key1; t=1783290019; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XzP4IrwF64OOqXOnzQR9aMpiMXv9vAON16c9GzABhuU=; b=N1Wvfg7Dq10Z/RxZQ+tgS9JhIQqoRQ/28Z90K5duhdeFQNuVR5zMBM40gudTQDrMhxZ7By 99luTqRHljddy0yN7kDEVVODul5MmXZ0Uk/umkixPZuR/JQP0GcTx6grrwAFFJ8H+92Qud NHeYbi0IRDMV1X1WiE+MtmFnDrwzcO3pz7B6+aGvZ5yX2hPsrYHk0zISLnGdLAzwZ8p2Gp U/3NBKqeu5uQnzizL+j2E/L1JKsk2V7tqtyepoHi0YC2+tsD9L9UxlXW56LCoC5ojWgnvh mJoSMHesEs9hbaQRUHuS6v6hSc8LxMfaXpQYzyChEttuAJ7VGnujAOLH2OSIyA== Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 06 Jul 2026 00:20:13 +0200 Message-Id: Subject: Re: [PATCH 2/9] drm/rockchip: vop2: Reset AXI and DCLK to improve robustness X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Diederik de Haas" To: "Cristian Ciocaltea" , "Diederik de Haas" , "Sandy Huang" , =?utf-8?q?Heiko_St=C3=BCbner?= , "Andy Yan" , "David Airlie" , "Simona Vetter" , "Maarten Lankhorst" , "Maxime Ripard" , "Thomas Zimmermann" , "Rob Herring" , "Krzysztof Kozlowski" , "Conor Dooley" , "Philipp Zabel" , "Andrzej Hajda" , "Neil Armstrong" , "Robert Foss" , "Laurent Pinchart" , "Jonas Karlman" , "Jernej Skrabec" , "Luca Ceresoli" Cc: , "Andy Yan" , , , , , References: <20260617-dw-hdmi-qp-yuv-v1-0-a665cfd06d7d@collabora.com> <20260617-dw-hdmi-qp-yuv-v1-2-a665cfd06d7d@collabora.com> In-Reply-To: X-Migadu-Flow: FLOW_OUT X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260705_152025_414966_850742D5 X-CRM114-Status: GOOD ( 12.82 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Cristian, On Sun Jul 5, 2026 at 10:46 PM CEST, Cristian Ciocaltea wrote: > On 7/5/26 4:28 PM, Diederik de Haas wrote: >> On Wed Jun 17, 2026 at 8:52 PM CEST, Cristian Ciocaltea wrote: >>> Assert the AXI reset in the CRTC disable path, and the VP DCLK reset in >>> the enable path. >>> >>> These resets are intended to leave the hardware in a clean state for th= e >>> next use, helping recover from exceptions such as IOMMU page faults, as >>> well as to prevent random display output glitches, such as a blank >>> image, observed when switching modes that also change the color format, >>> e.g. from RGB to YUV420 and vice versa. >>> >>> For now this seems to affect only the RK3588, hence the resets are >>> optional and will be provided in the device tree for this SoC only. >>=20 >> Why do you think it only effect RK3588?=20 > > My findings are exclusively in the context of validating YUV support for = DW HDMI > QP, hence targeting RK3588 and RK3576. Since RK3576 didn't exhibit any > anomalies, I concluded the resets are needed just for RK3588. Ok, that's indeed a different technology stack. >> I reported about my RK3568 test here: >> https://lore.kernel.org/linux-rockchip/DFRU6ODDM71P.3NQGLRK8IVDUY@cknow-= tech.com/ >> "I then went on to try LibreELEC's builds. The artifacts I (sometimes) >> saw, were gone :-D OTOH, I did get several major issues 'in return', >> like rk_iommu Page fault resulting in a black screen and the only way to >> 'recover' from it, was a reboot." >>=20 >> And I reported some more test results here: >> https://forum.libreelec.tv/thread/29953-le13-testing-for-rk3288-rk3328-r= k3399-rk3566-rk3568-rk3576-rk3588/?postID=3D204691#post204691 >>=20 >> That seems to me a (strong) indication it also affects RK3566/RK3568? > > If coincidentally this helps improve the reliability of some of the older= SoCs > as well, the resets can easily be added to the corresponding DTs and subm= itted > as a follow-up series. Agreed. Thanks :) Cheers, Diederik