From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Tang Bin <tangbin@cmss.chinamobile.com>,
broonie@kernel.org, cezary.rojewski@intel.com,
liam.r.girdwood@linux.intel.com, yang.jie@linux.intel.com,
perex@perex.cz, tiwai@suse.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Intel: atom: Remove redundant check to simplify the code
Date: Mon, 29 Nov 2021 10:22:41 -0600 [thread overview]
Message-ID: <3ca07ce3-6d5c-20cc-8992-4700490ea472@linux.intel.com> (raw)
In-Reply-To: <20211125075028.8500-1-tangbin@cmss.chinamobile.com>
On 11/25/21 1:50 AM, Tang Bin wrote:
> In the function sst_platform_get_resources(), if platform_get_irq()
> failed, the return should not be zero, as the example in
> platform.c is
> * int irq = platform_get_irq(pdev, 0)
> * if (irq < 0)
> * return irq;
> So remove the redundant check to simplify the code.
Humm, it's a bit of a gray area.
the comments for platform_get_irq and platform_get_irq_optional say:
* Return: non-zero IRQ number on success, negative error number on failure.
but if you look at platform_get_irq_optional, there are two references
to zero being a possible return value:
if (num == 0 && has_acpi_companion(&dev->dev)) {
ret = acpi_dev_gpio_irq_get(ACPI_COMPANION(&dev->dev), num);
/* Our callers expect -ENXIO for missing IRQs. */
if (ret >= 0 || ret == -EPROBE_DEFER)
goto out;
out_not_found:
ret = -ENXIO;
out:
WARN(ret == 0, "0 is an invalid IRQ number\n");
return ret;
https://elixir.bootlin.com/linux/latest/source/drivers/base/platform.c#L234
I am not sure if there's any merit in removing the test for the zero
return value. It may be on the paranoid side but it's aligned with a
possible code path in the platform code.
Or it could be that the platform code is wrong, and the label used
should have been
/* Our callers expect -ENXIO for missing IRQs. */
if (ret >= 0 || ret == -EPROBE_DEFER)
goto out_not_found;
Adding Andy Shevchenko for advice.
>
> Signed-off-by: Tang Bin <tangbin@cmss.chinamobile.com>
> ---
> sound/soc/intel/atom/sst/sst_acpi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/intel/atom/sst/sst_acpi.c b/sound/soc/intel/atom/sst/sst_acpi.c
> index 3be64430c..696d547c5 100644
> --- a/sound/soc/intel/atom/sst/sst_acpi.c
> +++ b/sound/soc/intel/atom/sst/sst_acpi.c
> @@ -226,8 +226,8 @@ static int sst_platform_get_resources(struct intel_sst_drv *ctx)
> /* Find the IRQ */
> ctx->irq_num = platform_get_irq(pdev,
> ctx->pdata->res_info->acpi_ipc_irq_index);
> - if (ctx->irq_num <= 0)
> - return ctx->irq_num < 0 ? ctx->irq_num : -EIO;
> + if (ctx->irq_num < 0)
> + return ctx->irq_num;
>
> return 0;
> }
>
next prev parent reply other threads:[~2021-11-29 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 7:50 [PATCH] ASoC: Intel: atom: Remove redundant check to simplify the code Tang Bin
2021-11-29 16:22 ` Pierre-Louis Bossart [this message]
2021-11-29 17:11 ` Mark Brown
2021-11-29 19:01 ` Andy Shevchenko
2021-11-29 19:05 ` Andy Shevchenko
2021-11-29 19:08 ` Mark Brown
2022-01-25 18:09 ` Andy Shevchenko
2021-11-30 9:46 ` Andy Shevchenko
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=3ca07ce3-6d5c-20cc-8992-4700490ea472@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tangbin@cmss.chinamobile.com \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.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