DMA Engine development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Pan Chuang" <panchuang@vivo.com>
Cc: Frank.Li@kernel.org, dmaengine@vger.kernel.org, vkoul@kernel.org
Subject: Re: [PATCH 24/26] dmaengine: ti-edma: Remove redundant dev_err()/dev_err_probe()
Date: Thu, 09 Jul 2026 14:38:14 +0000	[thread overview]
Message-ID: <20260709143814.9D5181F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260709135846.97972-25-panchuang@vivo.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] Unhandled probe deferral from `platform_get_irq_byname` causes the driver to silently probe without interrupts.
--

--- Patch [24]: [PATCH 24/26] dmaengine: ti-edma: Remove redundant dev_err()/dev_err_probe() ---
commit 3f067543fc6aa46c8b00f2557e8220b1465e86e3
Author: Pan Chuang <panchuang@vivo.com>

dmaengine: ti-edma: Remove redundant dev_err()/dev_err_probe()

The commit removes redundant dev_err() logging around devm_request_irq()
calls. The devm_request_irq() function now automatically logs detailed error
messages on failure, eliminating the need for driver-specific messages.

> diff --git a/drivers/dma/ti/edma.c b/drivers/dma/ti/edma.c
> index d97db5af35555..e023ca9640dec 100644
> --- a/drivers/dma/ti/edma.c
> +++ b/drivers/dma/ti/edma.c
> @@ -2415,10 +2415,8 @@ static int edma_probe(struct platform_device *pdev)
>  
>  	irq = platform_get_irq_byname(pdev, "edma3_ccint");
>  	if (irq < 0 && node)
>  		irq = irq_of_parse_and_map(node, 0);
>  
>  	if (irq > 0) {
>  		irq_name = devm_kasprintf(dev, GFP_KERNEL, "%s_ccint",
>  					  dev_name(dev));
>  		if (!irq_name) {
>  			ret = -ENOMEM;
>  			goto err_disable_pm;
>  		}
>  
>  		ret = devm_request_irq(dev, irq, dma_irq_handler, 0, irq_name,
>  				       ecc);
> -		if (ret) {
> -			dev_err(dev, "CCINT (%d) failed --> %d\n", irq, ret);
> +		if (ret)
>  			goto err_disable_pm;
> -		}
>  		ecc->ccint = irq;
>  	}

[Severity: High]
This is a pre-existing issue, but does this logic handle probe deferrals
correctly?

If platform_get_irq_byname() returns -EPROBE_DEFER, the irq value is
either overwritten to 0 by irq_of_parse_and_map(), or remains -EPROBE_DEFER.
In both scenarios, the if (irq > 0) check fails, causing the driver to
silently skip interrupt setup and successfully complete the probe without
interrupts.

Could this lead to dependent devices hanging or experiencing timeouts
because DMA completions are never signaled?

[ ... ]

> @@ -2436,10 +2434,8 @@ static int edma_probe(struct platform_device *pdev)
>  
>  	irq = platform_get_irq_byname(pdev, "edma3_ccerrint");
>  	if (irq < 0 && node)
>  		irq = irq_of_parse_and_map(node, 2);
>  
>  	if (irq > 0) {
>  		irq_name = devm_kasprintf(dev, GFP_KERNEL, "%s_ccerrint",
>  					  dev_name(dev));
>  		if (!irq_name) {
>  			ret = -ENOMEM;
>  			goto err_disable_pm;
>  		}
>  
>  		ret = devm_request_irq(dev, irq, dma_ccerr_handler, 0, irq_name,
>  				       ecc);
> -		if (ret) {
> -			dev_err(dev, "CCERRINT (%d) failed --> %d\n", irq, ret);
> +		if (ret)
>  			goto err_disable_pm;
> -		}
>  		ecc->ccerrint = irq;
>  	}

[Severity: High]
This isn't a bug introduced by this patch, but the error interrupt setup
appears to suffer from the same problem.

Would an unhandled probe deferral from platform_get_irq_byname() result
in silently swallowed errors here as well?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260709135846.97972-1-panchuang@vivo.com?part=24

  reply	other threads:[~2026-07-09 14:38 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 13:58 [PATCH 00/26] dmaengine: Remove redundant error messages on IRQ request failure Pan Chuang
2026-07-09 13:58 ` [PATCH 01/26] dmaengine: fsl-edma-main: Remove redundant dev_err()/dev_err_probe() Pan Chuang
2026-07-09 14:12   ` sashiko-bot
2026-07-09 14:33   ` Frank Li
2026-07-09 13:58 ` [PATCH 02/26] dmaengine: fsl-qdma: " Pan Chuang
2026-07-09 14:08   ` sashiko-bot
2026-07-09 14:34   ` Frank Li
2026-07-09 13:58 ` [PATCH 03/26] dmaengine: loongson-loongson1-apb-dma: " Pan Chuang
2026-07-09 14:11   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 04/26] dmaengine: mediatek-mtk-cqdma: " Pan Chuang
2026-07-09 14:10   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 05/26] dmaengine: mediatek-mtk-hsdma: " Pan Chuang
2026-07-09 14:10   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 06/26] dmaengine: mmp_pdma: " Pan Chuang
2026-07-09 14:08   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 07/26] dmaengine: moxart-dma: " Pan Chuang
2026-07-09 14:16   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 08/26] dmaengine: owl-dma: " Pan Chuang
2026-07-09 14:16   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 09/26] dmaengine: pxa_dma: " Pan Chuang
2026-07-09 14:20   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 10/26] dmaengine: qcom-gpi: " Pan Chuang
2026-07-09 14:19   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 11/26] dmaengine: sf-pdma-sf-pdma: " Pan Chuang
2026-07-09 14:18   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 12/26] dmaengine: sh-rcar-dmac: " Pan Chuang
2026-07-09 14:23   ` sashiko-bot
2026-07-09 14:31   ` Geert Uytterhoeven
2026-07-09 13:58 ` [PATCH 13/26] dmaengine: sh-rz-dmac: " Pan Chuang
2026-07-09 14:32   ` Geert Uytterhoeven
2026-07-09 13:58 ` [PATCH 14/26] dmaengine: sh-shdmac: " Pan Chuang
2026-07-09 14:24   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 15/26] dmaengine: sh-usb-dmac: " Pan Chuang
2026-07-09 14:27   ` sashiko-bot
2026-07-09 14:33   ` Geert Uytterhoeven
2026-07-09 13:58 ` [PATCH 16/26] dmaengine: sprd-dma: " Pan Chuang
2026-07-09 14:27   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 17/26] dmaengine: st_fdma: " Pan Chuang
2026-07-09 14:30   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 18/26] dmaengine: stm32-stm32-dma: " Pan Chuang
2026-07-09 14:30   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 19/26] dmaengine: stm32-stm32-dma3: " Pan Chuang
2026-07-09 14:33   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 20/26] dmaengine: stm32-stm32-mdma: " Pan Chuang
2026-07-09 14:32   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 21/26] dmaengine: sun4i-dma: " Pan Chuang
2026-07-09 14:35   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 22/26] dmaengine: sun6i-dma: " Pan Chuang
2026-07-09 13:58 ` [PATCH 23/26] dmaengine: tegra20-apb-dma: " Pan Chuang
2026-07-09 13:58 ` [PATCH 24/26] dmaengine: ti-edma: " Pan Chuang
2026-07-09 14:38   ` sashiko-bot [this message]
2026-07-09 13:58 ` [PATCH 25/26] dmaengine: uniphier-xdmac: " Pan Chuang
2026-07-09 14:41   ` sashiko-bot
2026-07-09 13:58 ` [PATCH 26/26] dmaengine: xgene-dma: " Pan Chuang
2026-07-09 14:39   ` sashiko-bot
2026-07-09 14:26 ` [PATCH 00/26] dmaengine: Remove redundant error messages on IRQ request failure Wolfram Sang

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=20260709143814.9D5181F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=panchuang@vivo.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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: 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