From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH] ASoC: fsl: fsl_asrc: Check for clk_prepare_enable() error
Date: Sat, 20 Jun 2015 13:27:05 -0700 [thread overview]
Message-ID: <20150620202705.GA7632@Asurada> (raw)
In-Reply-To: <1434825674-8618-1-git-send-email-festevam@gmail.com>
On Sat, Jun 20, 2015 at 03:41:14PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> clk_prepare_enable() may fail, so we should better check its return value
> and propagate it in the case of error.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> sound/soc/fsl/fsl_asrc.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/sound/soc/fsl/fsl_asrc.c b/sound/soc/fsl/fsl_asrc.c
> index c068494..37dde26 100644
> --- a/sound/soc/fsl/fsl_asrc.c
> +++ b/sound/soc/fsl/fsl_asrc.c
> @@ -931,14 +931,22 @@ static int fsl_asrc_probe(struct platform_device *pdev)
> static int fsl_asrc_runtime_resume(struct device *dev)
> {
> struct fsl_asrc *asrc_priv = dev_get_drvdata(dev);
> - int i;
> + int i, ret;
>
> - clk_prepare_enable(asrc_priv->mem_clk);
> - clk_prepare_enable(asrc_priv->ipg_clk);
> + ret = clk_prepare_enable(asrc_priv->mem_clk);
> + if (ret)
> + return ret;
> + ret = clk_prepare_enable(asrc_priv->ipg_clk);
> + if (ret)
> + goto disable_mem_clk;
> for (i = 0; i < ASRC_CLK_MAX_NUM; i++)
> clk_prepare_enable(asrc_priv->asrck_clk[i]);
How about these clocks?
disable_clk:
for (i--; i >= 0; i--)
clk_disable_unprepare(asrc_priv->asrc_clk[i]);
Might be better?
Thank you
Nicolin
prev parent reply other threads:[~2015-06-20 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 18:41 [PATCH] ASoC: fsl: fsl_asrc: Check for clk_prepare_enable() error Fabio Estevam
2015-06-20 20:27 ` Nicolin Chen [this message]
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=20150620202705.GA7632@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.