From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpout-03.galae.net (smtpout-03.galae.net [185.246.85.4]) (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 F027B370AD4 for ; Tue, 19 May 2026 10:38:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.246.85.4 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779187106; cv=none; b=gXKKtm5uy1DM8p46n3NIp5R0Bj2SP17Iyin9Zi5gmQsVYzLkmKCFV/VQvBotU8CSO+UigH3hDJBiCKwucBZIFQJLhKmVzBo8TpJQrYza+qME2i7U4Q0cTwcyE4G6jBpu50rztNVSCOAtGOV468xb3nuOUon2rqcR38a7cT4rFVs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779187106; c=relaxed/simple; bh=C5wGDyHN494Et5weLKkq6t7JvIdVjHdO88C0ifdNGt4=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=S5OAxN+V7P9w7c+CZMxW3Gj1/U3bm/Ea345ib4fJUgob57xywz40+u5GUedPYtH5vMKCkQGzpyJNIAa8uShpx0i5rExlTv+BBZJc2PB//4gNfyd/iCHaEp7149px9Y0MLyW7H3Bvpi7H6Wz4O9OECjgzBq5uD0QFenBIPS1gUyg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=kHr+SgeM; arc=none smtp.client-ip=185.246.85.4 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="kHr+SgeM" Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-03.galae.net (Postfix) with ESMTPS id A984F4E42CF1; Tue, 19 May 2026 10:38:23 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id 7662D606E9; Tue, 19 May 2026 10:38:23 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 59BD0107E8AC6; Tue, 19 May 2026 12:38:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1779187101; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=n+kT7vAmUewDgxn0HFnyrYRIIpXTDKvHS24hGWBZNk8=; b=kHr+SgeMkKDgHfFsBa+jwf3WSU+g6MmNk/Zd47ZGKQzMTxsmVgm/iEanabVx+q6IT7wS0q tMk6l552cVuw6bofUI3j/qxXtUyAQUwE8HwsbE3LJV/782dzziRnN/lSKp5NGTs2eA6tdp R7bG0UYPTZyhpM8dIFLPDM2D7bMSJYmYVpMmAkGKqA7UEGTyd4EeTM1FYjnHCghdQD5c5G liZfh0xicJEwiqBL2kvDWQxavhLJnP4Sfzz3nbkEcjyp1hHIgHCRz5I2bXKLPHFbhM3mNF i5uWNB0i/MKl37Itesk4hc+40tgMtRg5nYbL4CoEX7ORJVQ6yq/M3s9EjVfo0Q== From: Luca Ceresoli Date: Tue, 19 May 2026 12:37:21 +0200 Subject: [PATCH 04/37] drm/display: bridge-connector: store the drm_device pointer Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <20260519-drm-bridge-hotplug-v1-4-45e2bdb3dfb4@bootlin.com> References: <20260519-drm-bridge-hotplug-v1-0-45e2bdb3dfb4@bootlin.com> In-Reply-To: <20260519-drm-bridge-hotplug-v1-0-45e2bdb3dfb4@bootlin.com> To: Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Inki Dae , Jagan Teki , Marek Szyprowski , Marek Vasut , Stefan Agner , Frank Li , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam Cc: Hui Pu , Ian Ray , Thomas Petazzoni , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org, Luca Ceresoli X-Mailer: b4 0.15.2 X-Last-TLS-Session-Version: TLSv1.3 Currently the struct drm_device pointer is only needed during the initial drm_bridge_connector_init() and in drm_bridge_connector_handle_hpd() which gets it from the struct drm_connector. This will be insufficient when introducing bridge hotplugging, because: * some of the actions in drm_bridge_connector_init() will have to be performed later on, when a bridge is hot(un)plugged * the connector will be removed and re-added based on hotplug events, so the drm_connector might just not exist or its content be cleared Store the drm_device pointer in struct drm_bridge_connector for any later needs. Also convert drm_bridge_connector_handle_hpd() to use the newly stored value. Signed-off-by: Luca Ceresoli --- drivers/gpu/drm/display/drm_bridge_connector.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/display/drm_bridge_connector.c b/drivers/gpu/drm/display/drm_bridge_connector.c index bf9b8a6bca78..62c4cb1e241f 100644 --- a/drivers/gpu/drm/display/drm_bridge_connector.c +++ b/drivers/gpu/drm/display/drm_bridge_connector.c @@ -60,6 +60,10 @@ struct drm_bridge_connector { * @base: The base DRM connector */ struct drm_connector base; + /** + * @drm: The DRM device we belong to + */ + struct drm_device *drm; /** * @encoder: * @@ -157,7 +161,7 @@ static void drm_bridge_connector_handle_hpd(struct drm_bridge_connector *bridge_ enum drm_connector_status status) { struct drm_connector *connector = &bridge_connector->base; - struct drm_device *dev = connector->dev; + struct drm_device *dev = bridge_connector->drm; mutex_lock(&dev->mode_config.mutex); connector->status = status; @@ -806,6 +810,7 @@ struct drm_connector *drm_bridge_connector_init(struct drm_device *drm, if (ret) return ERR_PTR(ret); + bridge_connector->drm = drm; bridge_connector->encoder = encoder; /* -- 2.54.0