From: Jerome Brunet <jbrunet@baylibre.com>
To: Pavel Machek <pavel@ucw.cz>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, khilman@baylibre.com,
alsa-devel@alsa-project.org, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] soc/meson: add missing free_irq() in error path
Date: Sun, 07 Jun 2020 22:43:18 +0200 [thread overview]
Message-ID: <1j5zc2k3o9.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20200606153103.GA17905@amd>
On Sat 06 Jun 2020 at 17:31, Pavel Machek <pavel@ucw.cz> wrote:
> free_irq() is missing in case of error, fix that.
>
> Signed-off-by: Pavel Machek (CIP) <pavel@denx.de>
Reviewed-by: Jerome Brunet <jbrunet@baylibre.com>
>
> diff --git a/sound/soc/meson/axg-fifo.c b/sound/soc/meson/axg-fifo.c
> index 2e9b56b29d31..b2e867113226 100644
> --- a/sound/soc/meson/axg-fifo.c
> +++ b/sound/soc/meson/axg-fifo.c
> @@ -249,7 +249,7 @@ int axg_fifo_pcm_open(struct snd_soc_component *component,
> /* Enable pclk to access registers and clock the fifo ip */
> ret = clk_prepare_enable(fifo->pclk);
> if (ret)
> - return ret;
> + goto free_irq;
>
> /* Setup status2 so it reports the memory pointer */
> regmap_update_bits(fifo->map, FIFO_CTRL1,
> @@ -269,8 +269,14 @@ int axg_fifo_pcm_open(struct snd_soc_component *component,
> /* Take memory arbitror out of reset */
> ret = reset_control_deassert(fifo->arb);
> if (ret)
> - clk_disable_unprepare(fifo->pclk);
> + goto free_clk;
> +
> + return 0;
>
> +free_clk:
> + clk_disable_unprepare(fifo->pclk);
> +free_irq:
> + free_irq(fifo->irq, ss);
> return ret;
> }
> EXPORT_SYMBOL_GPL(axg_fifo_pcm_open);
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-06-07 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 15:31 Pavel Machek
2020-06-07 20:43 ` Jerome Brunet [this message]
2020-06-08 11:40 ` Mark Brown
2020-06-08 11:57 ` Mark Brown
2020-06-09 12:54 ` Mark Brown
2020-07-07 18:51 ` patchwork-bot+linux-amlogic
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=1j5zc2k3o9.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=trivial@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
all inboxes | Powered by JetHome®