From: Tony Lindgren <tony@atomide.com> To: Tomi Valkeinen <tomba@kernel.org>, David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Sebastian Reichel <sre@kernel.org>, dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH] drm/omap: dsi: Fix deferred probe warnings Date: Wed, 12 Apr 2023 10:39:53 +0300 [thread overview] Message-ID: <20230412073954.20601-1-tony@atomide.com> (raw) We may not have dsi->dsidev initialized during probe, and that can lead into various dsi related warnings as omap_dsi_host_detach() gets called with dsi->dsidev set to NULL. The warnings can be "Fixed dependency cycle(s)" followed by a WARNING: CPU: 0 PID: 787 at drivers/gpu/drm/omapdrm/dss/dsi.c:4414. Let's fix the warnings by checking for a valid dsi->dsidev. Signed-off-by: Tony Lindgren <tony@atomide.com> --- drivers/gpu/drm/omapdrm/dss/dsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/omapdrm/dss/dsi.c b/drivers/gpu/drm/omapdrm/dss/dsi.c --- a/drivers/gpu/drm/omapdrm/dss/dsi.c +++ b/drivers/gpu/drm/omapdrm/dss/dsi.c @@ -4411,7 +4411,7 @@ static int omap_dsi_host_detach(struct mipi_dsi_host *host, { struct dsi_data *dsi = host_to_omap(host); - if (WARN_ON(dsi->dsidev != client)) + if (dsi->dsidev && WARN_ON(dsi->dsidev != client)) return -EINVAL; cancel_delayed_work_sync(&dsi->dsi_disable_work); -- 2.40.0
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com> To: Tomi Valkeinen <tomba@kernel.org>, David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch> Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, dri-devel@lists.freedesktop.org, Sebastian Reichel <sre@kernel.org> Subject: [PATCH] drm/omap: dsi: Fix deferred probe warnings Date: Wed, 12 Apr 2023 10:39:53 +0300 [thread overview] Message-ID: <20230412073954.20601-1-tony@atomide.com> (raw) We may not have dsi->dsidev initialized during probe, and that can lead into various dsi related warnings as omap_dsi_host_detach() gets called with dsi->dsidev set to NULL. The warnings can be "Fixed dependency cycle(s)" followed by a WARNING: CPU: 0 PID: 787 at drivers/gpu/drm/omapdrm/dss/dsi.c:4414. Let's fix the warnings by checking for a valid dsi->dsidev. Signed-off-by: Tony Lindgren <tony@atomide.com> --- drivers/gpu/drm/omapdrm/dss/dsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/omapdrm/dss/dsi.c b/drivers/gpu/drm/omapdrm/dss/dsi.c --- a/drivers/gpu/drm/omapdrm/dss/dsi.c +++ b/drivers/gpu/drm/omapdrm/dss/dsi.c @@ -4411,7 +4411,7 @@ static int omap_dsi_host_detach(struct mipi_dsi_host *host, { struct dsi_data *dsi = host_to_omap(host); - if (WARN_ON(dsi->dsidev != client)) + if (dsi->dsidev && WARN_ON(dsi->dsidev != client)) return -EINVAL; cancel_delayed_work_sync(&dsi->dsi_disable_work); -- 2.40.0
next reply other threads:[~2023-04-12 7:40 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 7:39 Tony Lindgren [this message] 2023-04-12 7:39 ` [PATCH] drm/omap: dsi: Fix deferred probe warnings Tony Lindgren 2023-04-12 8:50 ` Laurent Pinchart 2023-04-12 8:50 ` Laurent Pinchart 2023-04-12 8:55 ` Tomi Valkeinen 2023-04-12 8:55 ` Tomi Valkeinen 2023-04-12 8:59 ` Laurent Pinchart 2023-04-12 8:59 ` Laurent Pinchart 2023-09-13 7:37 ` Tony Lindgren 2023-09-13 7:37 ` Tony Lindgren 2023-09-13 12:02 ` Tomi Valkeinen 2023-09-13 12:02 ` Tomi Valkeinen 2023-04-12 9:00 ` H. Nikolaus Schaller 2023-04-12 9:00 ` H. Nikolaus Schaller 2023-09-13 11:59 ` Tomi Valkeinen 2023-09-13 11:59 ` Tomi Valkeinen 2023-09-13 12:50 ` Tony Lindgren 2023-09-13 12:50 ` Tony Lindgren 2023-09-16 12:50 ` H. Nikolaus Schaller 2023-09-16 12:50 ` H. Nikolaus Schaller 2023-09-18 3:48 ` Tony Lindgren 2023-09-18 3:48 ` Tony Lindgren
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230412073954.20601-1-tony@atomide.com \ --to=tony@atomide.com \ --cc=airlied@gmail.com \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=sre@kernel.org \ --cc=tomba@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.