mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Meng Tang <tangmeng@uniontech.com>,
	"nicoleotsuka@gmail.com" <nicoleotsuka@gmail.com>,
	"Xiubo.Lee@gmail.com" <Xiubo.Lee@gmail.com>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"shengjiu.wang@gmail.com" <shengjiu.wang@gmail.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"perex@perex.cz" <perex@perex.cz>,
	"tiwai@suse.com" <tiwai@suse.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: fsl-asoc-card: Fix jack_event() always return 0
Date: Mon, 21 Mar 2022 06:44:54 +0000	[thread overview]
Message-ID: <951b1a57-99d7-caaf-2bf4-7a308a6ff3a8@csgroup.eu> (raw)
In-Reply-To: <20220318093536.15385-1-tangmeng@uniontech.com>



Le 18/03/2022 à 10:35, Meng Tang a écrit :
> Today, hp_jack_event and mic_jack_event always return 0. However,
> snd_soc_dapm_disable_pin and snd_soc_dapm_enable_pin may return a
> non-zero value, this will cause the user who calling hp_jack_event
> and mic_jack_event don't know whether the operation was really
> successfully.
> 
> This patch corrects the behavior by properly returning 1 when the
> value gets updated.
> 
> Signed-off-by: Meng Tang <tangmeng@uniontech.com>
> ---
>   sound/soc/fsl/fsl-asoc-card.c | 16 ++++++++++------
>   1 file changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/sound/soc/fsl/fsl-asoc-card.c b/sound/soc/fsl/fsl-asoc-card.c
> index 370bc790c6ba..f2641c2cb047 100644
> --- a/sound/soc/fsl/fsl-asoc-card.c
> +++ b/sound/soc/fsl/fsl-asoc-card.c
> @@ -457,16 +457,18 @@ static int fsl_asoc_card_audmux_init(struct device_node *np,
>   static int hp_jack_event(struct notifier_block *nb, unsigned long event,
>   			 void *data)
>   {
> +	int ret;
> +

You don't need that new local var. There are coccinelle scripts that 
track those unnecessary intermediates so don't add a new one.

>   	struct snd_soc_jack *jack = (struct snd_soc_jack *)data;
>   	struct snd_soc_dapm_context *dapm = &jack->card->dapm;
>   
>   	if (event & SND_JACK_HEADPHONE)
>   		/* Disable speaker if headphone is plugged in */
> -		snd_soc_dapm_disable_pin(dapm, "Ext Spk");
> +		ret = snd_soc_dapm_disable_pin(dapm, "Ext Spk");

Should be
		return snd_soc_dapm_disable_pin(dapm, "Ext Spk");

>   	else
> -		snd_soc_dapm_enable_pin(dapm, "Ext Spk");
> +		ret = snd_soc_dapm_enable_pin(dapm, "Ext Spk");

and

		return snd_soc_dapm_enable_pin(dapm, "Ext Spk");

>   
> -	return 0;
> +	return ret;

And completely drop that.

>   }
>   
>   static struct notifier_block hp_jack_nb = {
> @@ -476,16 +478,18 @@ static struct notifier_block hp_jack_nb = {
>   static int mic_jack_event(struct notifier_block *nb, unsigned long event,
>   			  void *data)
>   {
> +	int ret;
> +

And do exactly the same here.

>   	struct snd_soc_jack *jack = (struct snd_soc_jack *)data;
>   	struct snd_soc_dapm_context *dapm = &jack->card->dapm;
>   
>   	if (event & SND_JACK_MICROPHONE)
>   		/* Disable dmic if microphone is plugged in */
> -		snd_soc_dapm_disable_pin(dapm, "DMIC");
> +		ret = snd_soc_dapm_disable_pin(dapm, "DMIC");
>   	else
> -		snd_soc_dapm_enable_pin(dapm, "DMIC");
> +		ret = snd_soc_dapm_enable_pin(dapm, "DMIC");
>   
> -	return 0;
> +	return ret;
>   }
>   
>   static struct notifier_block mic_jack_nb = {

      reply	other threads:[~2022-03-21  6:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  9:35 Meng Tang
2022-03-21  6:44 ` Christophe Leroy [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=951b1a57-99d7-caaf-2bf4-7a308a6ff3a8@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=Xiubo.Lee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=perex@perex.cz \
    --cc=shengjiu.wang@gmail.com \
    --cc=tangmeng@uniontech.com \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®