From: Michal Simek <michal.simek@amd.com>
To: phucduc.bui@gmail.com,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ASoC: xilinx: xlnx_i2s: Use dev_err_probe() and drop redundant error handling
Date: Fri, 10 Jul 2026 09:29:12 +0200 [thread overview]
Message-ID: <5d058564-5546-4e48-99eb-fc44b07c733b@amd.com> (raw)
In-Reply-To: <20260710050223.14266-2-phucduc.bui@gmail.com>
On 7/10/26 07:02, phucduc.bui@gmail.com wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> Use dev_err_probe() for probe error handling where appropriate to
> simplify the code and properly handle deferred probe.
> Also remove redundant error messages when the called helper already
> reports failures, returning the error directly to avoid duplicate
> logging.
>
> Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>
> ---
> sound/soc/xilinx/xlnx_i2s.c | 18 +++++++-----------
> 1 file changed, 7 insertions(+), 11 deletions(-)
>
> diff --git a/sound/soc/xilinx/xlnx_i2s.c b/sound/soc/xilinx/xlnx_i2s.c
> index ca915a001ad5..0676da122edd 100644
> --- a/sound/soc/xilinx/xlnx_i2s.c
> +++ b/sound/soc/xilinx/xlnx_i2s.c
> @@ -185,17 +185,15 @@ static int xlnx_i2s_probe(struct platform_device *pdev)
> return PTR_ERR(drv_data->base);
>
> ret = of_property_read_u32(node, "xlnx,num-channels", &drv_data->channels);
> - if (ret < 0) {
> - dev_err(dev, "cannot get supported channels\n");
> - return ret;
> - }
> + if (ret < 0)
> + return dev_err_probe(dev, ret, "cannot get supported channels\n");
> +
> drv_data->channels *= 2;
>
> ret = of_property_read_u32(node, "xlnx,dwidth", &drv_data->data_width);
> - if (ret < 0) {
> - dev_err(dev, "cannot get data width\n");
> - return ret;
> - }
> + if (ret < 0)
> + return dev_err_probe(dev, ret, "cannot get data width\n");
> +
> switch (drv_data->data_width) {
> case 16:
> format = SNDRV_PCM_FMTBIT_S16_LE;
> @@ -233,10 +231,8 @@ static int xlnx_i2s_probe(struct platform_device *pdev)
>
> ret = devm_snd_soc_register_component(&pdev->dev, &xlnx_i2s_component,
> &drv_data->dai_drv, 1);
> - if (ret) {
> - dev_err(&pdev->dev, "i2s component registration failed\n");
> + if (ret)
> return ret;
> - }
>
> dev_info(&pdev->dev, "%s DAI registered\n", drv_data->dai_drv.name);
>
Reviewed-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
next prev parent reply other threads:[~2026-07-10 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 5:02 [PATCH 0/2] ASoC: xilinx: Use dev_err_probe() and drop redundant error handling phucduc.bui
2026-07-10 5:02 ` [PATCH 1/2] ASoC: xilinx: xlnx_i2s: " phucduc.bui
2026-07-10 7:29 ` Michal Simek [this message]
2026-07-10 5:02 ` [PATCH 2/2] ASoC: xilinx: xlnx_spdif: " phucduc.bui
2026-07-10 7:34 ` Michal Simek
2026-07-10 8:17 ` Bui Duc Phuc
2026-07-10 8:48 ` Michal Simek
2026-07-10 10:20 ` Bui Duc Phuc
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=5d058564-5546-4e48-99eb-fc44b07c733b@amd.com \
--to=michal.simek@amd.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phucduc.bui@gmail.com \
--cc=tiwai@suse.com \
--cc=vincenzo.frascino@arm.com \
/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