The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Andy Yan" <andyshrk@163.com>
To: "Alper Ak" <alperyasinak1@gmail.com>
Cc: andy.yan@rock-chips.com,
	"Andrzej Hajda" <andrzej.hajda@intel.com>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Robert Foss" <rfoss@kernel.org>,
	"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
	"Jonas Karlman" <jonas@kwiboo.se>,
	"Jernej Skrabec" <jernej.skrabec@gmail.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re:[PATCH] drm/bridge: synopsys: dw-dp: Pass dp->irq instead of ret to ERR_PTR() on IRQ failure
Date: Fri, 26 Dec 2025 16:13:58 +0800 (CST)	[thread overview]
Message-ID: <3d96a2f5.6efd.19b59b8bdf0.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <20251226072001.16623-1-alperyasinak1@gmail.com>


Hello Alper,

At 2025-12-26 15:20:01, "Alper Ak" <alperyasinak1@gmail.com> wrote:
>The error handling after platform_get_irq() incorrectly passes ret to
>ERR_PTR(), but ret still holds the value 0 from the previous successful
>devm_add_action_or_reset() call. This causes ERR_PTR(0) which returns NULL
>instead of a proper error pointer.
>
>Pass dp->irq to ERR_PTR() since platform_get_irq() returns the negative
>error code directly in dp->irq on failure.
>
>Fixes: 86eecc3a9c2e ("drm/bridge: synopsys: Add DW DPTX Controller support library")
>Signed-off-by: Alper Ak <alperyasinak1@gmail.com>

Reviewed-by: Andy Yan <andyshrk@163.com>

Thanks

>---
> drivers/gpu/drm/bridge/synopsys/dw-dp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/gpu/drm/bridge/synopsys/dw-dp.c b/drivers/gpu/drm/bridge/synopsys/dw-dp.c
>index 36382956bbe0..718397a29e80 100644
>--- a/drivers/gpu/drm/bridge/synopsys/dw-dp.c
>+++ b/drivers/gpu/drm/bridge/synopsys/dw-dp.c
>@@ -2079,7 +2079,7 @@ struct dw_dp *dw_dp_bind(struct device *dev, struct drm_encoder *encoder,
> 
> 	dp->irq = platform_get_irq(pdev, 0);
> 	if (dp->irq < 0)
>-		return ERR_PTR(ret);
>+		return ERR_PTR(dp->irq);
> 
> 	ret = devm_request_threaded_irq(dev, dp->irq, NULL, dw_dp_irq,
> 					IRQF_ONESHOT, dev_name(dev), dp);
>-- 
>2.43.0

      reply	other threads:[~2025-12-26  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-26  7:20 [PATCH] drm/bridge: synopsys: dw-dp: Pass dp->irq instead of ret to ERR_PTR() on IRQ failure Alper Ak
2025-12-26  8:13 ` Andy Yan [this message]

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=3d96a2f5.6efd.19b59b8bdf0.Coremail.andyshrk@163.com \
    --to=andyshrk@163.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=alperyasinak1@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=andy.yan@rock-chips.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox