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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (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 CC180D3E79C for ; Thu, 11 Dec 2025 08:28:41 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id E596E10E779; Thu, 11 Dec 2025 08:28:40 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=bootlin.com header.i=@bootlin.com header.b="nkKh22R7"; dkim-atps=neutral Received: from smtpout-04.galae.net (smtpout-04.galae.net [185.171.202.116]) by gabe.freedesktop.org (Postfix) with ESMTPS id 46F9710E770 for ; Thu, 11 Dec 2025 08:28:39 +0000 (UTC) Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-04.galae.net (Postfix) with ESMTPS id 299B8C19347; Thu, 11 Dec 2025 08:28:13 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id 16FC26068C; Thu, 11 Dec 2025 08:28:37 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id E6ACF103C8C1E; Thu, 11 Dec 2025 09:28:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1765441716; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=0SrfXUdcUykyhFz/Z2PprfF3ar6YbChnSr+9vH8ynbE=; b=nkKh22R7g0PLjyBcO7yn2yXRd61A0yeRhie7iL8AkagNhIYKDDPex+SbNyXNEKlhHFadEX o49mTdgbZNoOH9/+Ynuh8dxNkX4OsiIGa3Nsm3mN2LGrY2E53EKTGyCSKd8NeV/2SK7Pc7 8s2+/C0R85xxoGQjWWvzVF1QYlM/TZAS5dlBEujUnlHAl4EkfBvFeg50GDgEcfE2AsEjMC dAt8d3iBcLg64TqoLzd0eiQ5HLbJg7DuZT46lYpKC3Dz7jA2yfcYWWCP9ph8AhAwZx0j5m NxvETRYA1fNTDLY1tmtyqggyYSR2w4AzxCTY+YiT69m3sj3NSuDqAYPaI77UBw== Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 11 Dec 2025 09:28:29 +0100 Message-Id: Subject: Re: [PATCH v3 0/2] drm/bridge: handle gracefully atomic updates during bridge removal Cc: , , "Andrzej Hajda" , "David Airlie" , "Dmitry Baryshkov" , "Hui Pu" , "Jernej Skrabec" , "Jonas Karlman" , "Laurent Pinchart" , "Maarten Lankhorst" , "Neil Armstrong" , "Robert Foss" , "Simona Vetter" , "Thomas Petazzoni" , "Thomas Zimmermann" , "Francesco Dolcini" , "Emanuele Ghidoli" , =?utf-8?q?Jo=C3=A3o_Paulo_Gon=C3=A7alves?= To: "Maxime Ripard" From: "Luca Ceresoli" X-Mailer: aerc 0.20.1 References: <20251112-drm-bridge-atomic-vs-remove-v3-0-85db717ce094@bootlin.com> <546bc098a35360c659b6dfb88d5cb451@kernel.org> <20251128-cheerful-muscular-chameleon-1ec2f5@houat> In-Reply-To: <20251128-cheerful-muscular-chameleon-1ec2f5@houat> X-Last-TLS-Session-Version: TLSv1.3 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hello, On Fri Nov 28, 2025 at 11:07 AM CET, Maxime Ripard wrote: > On Fri, Nov 28, 2025 at 09:09:17AM +0100, Luca Ceresoli wrote: >> Hi Maxime, >> >> +Cc Emanuele, Francesco, Jo=C3=A3o >> >> On Thu Nov 27, 2025 at 7:35 PM CET, Maxime Ripard wrote: >> > On Wed, 12 Nov 2025 17:34:33 +0100, Luca Ceresoli wrote: >> >> This is a first attempt at gracefully handling the case of atomic upd= ates >> >> happening concurrently to physical removal of DRM bridges. >> >> >> >> This is part of the work to support hotplug of DRM bridges. The grand= plan >> >> was discussed in [1]. >> >> >> >> [ ... ] >> > >> > Reviewed-by: Maxime Ripard >> >> Thanks for reviewing! >> >> Two alternative patches [0][1] have been sent to address the issue with >> PLL_UNLOCK, and both would conflict with patch 2 of this series. So I'd >> keep this series on hold for a while, waiting for a decision to be taken >> about how the PLL_UNLOCK issue will be handled. I'll then rebase this >> series as needed. > > Yep, agreed. Turns out the patch that got applied does not conflict with this series, out of luck with the code layout. So I'm applying this one today. Luca -- Luca Ceresoli, Bootlin Embedded Linux and Kernel engineering https://bootlin.com