ASoC: meson: Use dev_err_probe() for device reset failures
PATCH 1/1 ASoC: meson: Use dev_err_probe() for device reset failures
From: bui duc phuc <[email protected]>
device_reset() may return -EPROBE_DEFER. Switch to dev_err_probe() so probe failures are reported consistently and deferred probing is handled properly.
This matches the existing pattern used in aiu_probe().
No functional change intended.
--- sound/soc/meson/g12a-toacodec.c | 2 +- sound/soc/meson/g12a-tohdmitx.c | 2 +- sound/soc/meson/t9015.c | 6 ++---- 3 files changed, 4 insertions(+), 6 deletions(-)
sound/soc/meson/g12a-toacodec.c +1 -1
@@ -312,7 +312,7 @@ static int g12a_toacodec_probe(struct platform_device *pdev) ret =device_reset (dev);if (ret) -return ret; +return dev_err_probe (dev, ret,"failed to reset device\n" ); regs =devm_platform_ioremap_resource (pdev,0 );if (IS_ERR (regs))
sound/soc/meson/g12a-tohdmitx.c +1 -1
@@ -251,7 +251,7 @@ static int g12a_tohdmitx_probe(struct platform_device *pdev) ret =device_reset (dev);if (ret) -return ret; +return dev_err_probe (dev, ret,"failed to reset device\n" ); regs =devm_platform_ioremap_resource (pdev,0 );if (IS_ERR (regs))
sound/soc/meson/t9015.c +2 -4
@@ -265,10 +265,8 @@ static int t9015_probe(struct platform_device *pdev)return dev_err_probe (dev,PTR_ERR (priv->avdd),"failed to AVDD\n" ); ret =device_reset (dev); -if (ret) { -dev_err (dev,"reset failed\n" ); -return ret; - } +if (ret) +return dev_err_probe (dev, ret,"failed to reset device\n" ); regs =devm_platform_ioremap_resource (pdev,0 );if (IS_ERR (regs)) {
Signature · 1 line
2.43.0
Mark Brown
maintainerQuoted 1 line · On Fri, 12 Jun 2026 09:01:12 +0700, [email protected] wrote:
ASoC: meson: Use
dev_err_probe()for device reset failures
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3
Thanks!
[1/1] ASoC: meson: Use dev_err_probe() for device reset failures
https://git.kernel.org/broonie/sound/c/6ed013a581d0
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark