From: sashiko-bot@kernel.org
To: phucduc.bui@gmail.com
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH v2 5/6] ASoC: dwc: Propagate optional IRQ lookup errors
Date: Tue, 10 Nov 2026 10:06:29 +0000 [thread overview]
Message-ID: <sashiko-outbox-206833@kernel.org> (raw)
In-Reply-To: <20261110095525.504660-6-phucduc.bui@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] ASoC: dwc: unbalanced reset deassert in dw_i2s_probe() on IRQ
error
--
commit f22e35683fe4bb23831ac84cbbbb8c5cfc290ae0
Author: bui duc phuc <phucduc.bui@gmail.com>
ASoC: dwc: Propagate optional IRQ lookup errors
This commit updates dw_i2s_probe() to propagate errors other than -ENXIO
from platform_get_irq_optional() using dev_err_probe().
> diff --git a/sound/soc/dwc/dwc-i2s.c b/sound/soc/dwc/dwc-i2s.c
> index b0d3413c27d2b..0d2be2d8d31ae 100644
> --- a/sound/soc/dwc/dwc-i2s.c
> +++ b/sound/soc/dwc/dwc-i2s.c
> @@ -961,8 +961,8 @@ static int dw_i2s_probe(struct platform_device *pdev)
> }
>
> irq = platform_get_irq_optional(pdev, 0);
> - if (irq == -EPROBE_DEFER)
> - return irq;
> + if (irq < 0 && irq != -ENXIO)
> + return dev_err_probe(&pdev->dev, irq, "failed to get IRQ\n");
[Severity: Medium]
Does returning directly here leave dev->reset deasserted when
platform_get_irq_optional() fails?
Just before the IRQ lookup, dw_i2s_probe() manually deasserts the shared
reset control via reset_control_deassert(dev->reset), and later failure
paths jump to err_assert_reset to call reset_control_assert(dev->reset).
Bypassing err_assert_reset leaves the hardware reset line deasserted and
leaks a deassert reference on the shared reset control.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110095525.504660-1-phucduc.bui@gmail.com?part=5
next prev parent reply other threads:[~2026-11-10 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 9:55 [PATCH v2 0/6] ASoC: dwc: Fix several issues in the I2S driver phucduc.bui
2026-11-10 9:55 ` [PATCH v2 1/6] ASoC: dwc: Fix bit clock rate in TDM mode phucduc.bui
2026-11-10 9:55 ` [PATCH v2 2/6] ASoC: dwc: Fix error handling in dw_i2s_set_fmt() phucduc.bui
2026-11-10 9:55 ` [PATCH v2 3/6] ASoC: dwc: Fix channels_max derived from COMP_PARAM_1 phucduc.bui
2026-11-10 9:55 ` [PATCH v2 4/6] ASoC: dwc: Fix DMA fifo_size calculation phucduc.bui
2026-11-10 10:02 ` sashiko-bot
2026-11-11 1:49 ` Bui Duc Phuc
2026-11-10 9:55 ` [PATCH v2 5/6] ASoC: dwc: Propagate optional IRQ lookup errors phucduc.bui
2026-11-10 10:06 ` sashiko-bot [this message]
2026-11-11 1:45 ` Bui Duc Phuc
2026-11-10 9:55 ` [PATCH v2 6/6] ASoC: dwc: Remove redundant error messages phucduc.bui
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=sashiko-outbox-206833@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=phucduc.bui@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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