linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chuhong Yuan <hslester96@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/ca0132 - add missed snd_hda_gen_parse_auto_config
Date: Mon, 09 Dec 2019 17:33:48 +0100	[thread overview]
Message-ID: <s5hv9qpcvbn.wl-tiwai@suse.de> (raw)
In-Reply-To: <20191209162119.14820-1-hslester96@gmail.com>

On Mon, 09 Dec 2019 17:21:19 +0100,
Chuhong Yuan wrote:
> 
> It is found that all usages of snd_hda_parse_pin_defcfg() are followed
> with snd_hda_gen_parse_auto_config() except here.
> This should be a miss and needs to add the missed call.

No, this will break things badly.

CA0132 codec driver has own configurator, and the pincfg parser is
called there because the initialization function requires the pincfg
information for the digital audio pins.


thanks,

Takashi


> 
> Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
> ---
>  sound/pci/hda/patch_ca0132.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/sound/pci/hda/patch_ca0132.c b/sound/pci/hda/patch_ca0132.c
> index b7a1abb3e231..ea1187a13241 100644
> --- a/sound/pci/hda/patch_ca0132.c
> +++ b/sound/pci/hda/patch_ca0132.c
> @@ -24,6 +24,7 @@
>  #include "hda_local.h"
>  #include "hda_auto_parser.h"
>  #include "hda_jack.h"
> +#include "hda_generic.h"
>  
>  #include "ca0132_regs.h"
>  
> @@ -8844,6 +8845,10 @@ static int patch_ca0132(struct hda_codec *codec)
>  	if (err < 0)
>  		goto error;
>  
> +	err = snd_hda_gen_parse_auto_config(codec, &spec->autocfg);
> +	if (err < 0)
> +		goto error;
> +
>  	return 0;
>  
>   error:
> -- 
> 2.24.0
> 

      reply	other threads:[~2019-12-09 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 16:21 [PATCH] ALSA: hda/ca0132 - add missed snd_hda_gen_parse_auto_config Chuhong Yuan
2019-12-09 16:33 ` Takashi Iwai [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=s5hv9qpcvbn.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=hslester96@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --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;
as well as URLs for NNTP newsgroup(s).