From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 15E694915BE for ; Thu, 1 Oct 2026 13:15:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790860510; cv=none; b=VHk4SJsm5I7nK71j7gdZDqwzhsyLkCKzGJ7e/t/o3v1VJC0YJDrIhyTtMGGmcBDPTaq4tzpxQsQ2OyGJFntRrQAp56x3NAigyCb52fTxsZdBkMg0cxLUwZH+POFETbxL501yJxueBO7ErzZB79CFlpG53wx8HpNAWcnmcbGSmEA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790860510; c=relaxed/simple; bh=VGwFQCjCSfPYMA9Ab99e5JUE7Q/RBW7qFpn9nSHEoXA=; h=From:Subject:To:Cc:In-Reply-To:References:Content-Type:Date: Message-Id; b=oUOJRtS/5sbQiO5fLBqyC4VphO60/osIwsG10Jo7rux83ZKnHbxTHiVse8hufOnn8L4pR/0IvQmFj4Qwy1tVwhO2WB3R/+DgcTv1mCXlphEDnDnDPbKOf0KZFDgDDRbl79o9S0eE7hQj6eFEgsuX0sQL97ijTT2KZuL//cS90ts= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=GngcDDBV; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="GngcDDBV" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F50F1F000FF; Thu, 1 Oct 2026 13:15:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790860508; bh=YPQcl+2hdQB930rYPjewmwTMJsK6jvBrW9cCTzQbfvU=; h=From:Subject:Reply-To:To:Cc:In-Reply-To:References:Date; b=GngcDDBVwFwgLNbSha1zfcCWcld0lWXM57js4DNSc0WaJ3rHSXo27OVb9bGeDbZ8q 3TsZeqVRBCWb4MwpVCEfiOhw/Wy5wMD7xxAcnQj6A98SdbVHFADl+c6fQBba6NCmnf tY5er2sa1hx//lNJPr3+2fQNM0cGdvIsh9LA8op3w2Rk50ZI7/7/96DlSzzb0/Mue6 eUqSGLX/Y+bz7Kf1b3ZzDPkFZa9y6iZMC8QA9O+sA1rA2lwgVvCe3r1hl5Y5e0rScm EAIMRsj/YSZzjavILTdrCfbLXDN4M63MFI6sAz+daMTLXyKjI9ah9CK6rw0GphlHgs tnL8y/k5h4vwA== From: sashiko-bot@kernel.org Subject: Re: [PATCH RFC v2 16/24] drm/mipi-dsi: notify about DSI attach Reply-To: sashiko-reviews@lists.linux.dev To: "Luca Ceresoli" Cc: imx@lists.linux.dev, Frank.Li@kernel.org, dri-devel@lists.freedesktop.org In-Reply-To: <20261001-drm-bridge-hotplug-v2-16-8e34986dcb68@bootlin.com> References: <20261001-drm-bridge-hotplug-v2-0-8e34986dcb68@bootlin.com> <20261001-drm-bridge-hotplug-v2-16-8e34986dcb68@bootlin.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Thu, 01 Oct 2026 13:15:07 +0000 Message-Id: <20261001131508.5F50F1F000FF@smtp.kernel.org> Precedence: bulk X-Mailing-List: imx@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: Thank you for your contribution! Sashiko AI review found 1 potential issue(= s) to consider: - [Medium] drm: commit message contradicts ATTACHED event semantics -- commit 3106f1037d08f7d82066d0ccd2f170f5facd1bf0 Author: Luca Ceresoli drm/mipi-dsi: notify about DSI attach This commit introduces an event notification when a DSI device is attached = to its host. This is added in preparation for DRM bridge hotplug support. > In preparation to support DRM bridge hotplug, let the drm_mipi_dsi co= de > emit an event when a DSI device is attached to the corresponding DSI = host, > so that this event can trigger the actions needed to deconfigure the > pipeline and unregister the connector as appropriate. [Severity: Medium] Does this commit message contradict the ATTACHED event semantics used in mipi_dsi_attach() in drivers/gpu/drm/drm_mipi_dsi.c? The commit message explicitly claims the DRM_MIPI_DSI_ATTACHED event is intended to trigger actions to "deconfigure the pipeline and unregister the connector". However, since this event is emitted when a device is attached, shouldn't it be used to configure the pipeline and register the connector (which is what the hotplug helper actually does)? The teardown path is structurally safe because error unwinding (via devres) calls drm_bridge_remove(), which detaches the bridge from the encoder and emits DRM_BRIDGE_DETACHED. The hotplug helper correctly listens to DRM_BRIDGE_DETACHED to unregister the connector, meaning the lifecycle is perfectly symmetrical without needing a dedicated DRM_MIPI_DSI_DETACHED event. Could the commit message be updated to reflect that this event triggers configuration and registration rather than deconfiguration and unregistration? > diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_mipi_ds= i.c > index 3ac1dd5ad640a..eaa474da4a519 100644 > --- a/drivers/gpu/drm/drm_mipi_dsi.c > +++ b/drivers/gpu/drm/drm_mipi_dsi.c [ ... ] > @@ -386,6 +387,8 @@ int mipi_dsi_attach(struct mipi_dsi_device *dsi) > =20 > dsi->attached =3D true; > =20 > + drm_event_notifier_notify(DRM_MIPI_DSI_ATTACHED, dsi); > + > return 0; > } --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/20261001-drm-bridge= -hotplug-v2-0-8e34986dcb68@bootlin.com?part=3D16