From: Shengjiu Wang <shengjiu.wang@gmail.com>
To: zhangqilong <zhangqilong3@huawei.com>
Cc: alsa-devel@alsa-project.org, Xiubo Li <Xiubo.Lee@gmail.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>,
Nicolin Chen <nicoleotsuka@gmail.com>,
Mark Brown <broonie@kernel.org>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH V2] ASoC: fsl_xcvr:Fix unbalanced pm_runtime_enable in fsl_xcvr_probe
Date: Thu, 2 Jun 2022 10:51:44 +0800 [thread overview]
Message-ID: <CAA+D8AMuZx0CT6GVVh5AhrAKJEFSumFPpAXkNnCdLX5FiwuFFw@mail.gmail.com> (raw)
In-Reply-To: <20220530083533.52254-1-zhangqilong3@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]
On Mon, May 30, 2022 at 4:33 PM zhangqilong <zhangqilong3@huawei.com> wrote:
> a) Add missing pm_runtime_disable() when probe error out. It could
> avoid pm_runtime implementation complains when removing and probing
> again the driver.
> b) Add remove for missing pm_runtime_disable().
>
> v2: add remove to put PM usage counter.
> Fix:c590fa80b3928 ("ASoC: fsl_xcvr: register platform component before
> registering cpu dai")
> Signed-off-by: Zhang Qilong <zhangqilong3@huawei.com>
> ---
>
The changelog should be in the place after "---"
Best regards
Wang shengjiu
sound/soc/fsl/fsl_xcvr.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/sound/soc/fsl/fsl_xcvr.c b/sound/soc/fsl/fsl_xcvr.c
> index d0556c79fdb1..55e640cba87d 100644
> --- a/sound/soc/fsl/fsl_xcvr.c
> +++ b/sound/soc/fsl/fsl_xcvr.c
> @@ -1228,6 +1228,7 @@ static int fsl_xcvr_probe(struct platform_device
> *pdev)
> */
> ret = devm_snd_dmaengine_pcm_register(dev, NULL, 0);
> if (ret) {
> + pm_runtime_disable(dev);
> dev_err(dev, "failed to pcm register\n");
> return ret;
> }
> @@ -1235,6 +1236,7 @@ static int fsl_xcvr_probe(struct platform_device
> *pdev)
> ret = devm_snd_soc_register_component(dev, &fsl_xcvr_comp,
> &fsl_xcvr_dai, 1);
> if (ret) {
> + pm_runtime_disable(dev);
> dev_err(dev, "failed to register component %s\n",
> fsl_xcvr_comp.name);
> }
> @@ -1242,6 +1244,12 @@ static int fsl_xcvr_probe(struct platform_device
> *pdev)
> return ret;
> }
>
> +static int fsl_xcvr_remove(struct platform_device *pdev)
> +{
> + pm_runtime_disable(&pdev->dev);
> + return 0;
> +}
> +
> static __maybe_unused int fsl_xcvr_runtime_suspend(struct device *dev)
> {
> struct fsl_xcvr *xcvr = dev_get_drvdata(dev);
> @@ -1370,6 +1378,7 @@ static struct platform_driver fsl_xcvr_driver = {
> .pm = &fsl_xcvr_pm_ops,
> .of_match_table = fsl_xcvr_dt_ids,
> },
> + .remove = fsl_xcvr_remove,
> };
> module_platform_driver(fsl_xcvr_driver);
>
> --
> 2.31.1
>
>
[-- Attachment #2: Type: text/html, Size: 3399 bytes --]
prev parent reply other threads:[~2022-06-02 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 8:35 [PATCH V2] ASoC: fsl_xcvr:Fix unbalanced pm_runtime_enable in fsl_xcvr_probe zhangqilong
2022-06-02 2:51 ` Shengjiu Wang [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=CAA+D8AMuZx0CT6GVVh5AhrAKJEFSumFPpAXkNnCdLX5FiwuFFw@mail.gmail.com \
--to=shengjiu.wang@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=zhangqilong3@huawei.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;
as well as URLs for NNTP newsgroup(s).