alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Naveen M <naveen.m@intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
	liam.r.girdwood@linux.intel.com,
	Harsha Priya <harshapriya.n@intel.com>,
	broonie@kernel.org, pierre-louis.bossart@intel.com
Subject: Re: [PATCH] ASoC: Intel: Skylake: Use correct nuvoton codec ID
Date: Thu, 3 Aug 2017 10:25:22 +0530	[thread overview]
Message-ID: <20170803045522.GC3053@localhost> (raw)
In-Reply-To: <1501654663-24663-1-git-send-email-naveen.m@intel.com>

On Wed, Aug 02, 2017 at 11:47:43AM +0530, Naveen M wrote:
> Correcting the nau88l25 codec ID to match secondary codec
> and load the machine driver.

We shouldn't have missed it :(

Acked-By: Vinod Koul <vinod.koul@intel.com>

> Signed-off-by: Naveen M <naveen.m@intel.com>
> Signed-off-by: Harsha Priya <harshapriya.n@intel.com>
> 
> diff --git a/sound/soc/intel/skylake/skl.c b/sound/soc/intel/skylake/skl.c
> index 334917e..608c147 100644
> --- a/sound/soc/intel/skylake/skl.c
> +++ b/sound/soc/intel/skylake/skl.c
> @@ -879,12 +879,12 @@ static void skl_remove(struct pci_dev *pci)
>  
>  static struct sst_codecs skl_codecs = {
>  	.num_codecs = 1,
> -	.codecs = {"NAU88L25"}
> +	.codecs = {"10508825"}
>  };
>  
>  static struct sst_codecs kbl_codecs = {
>  	.num_codecs = 1,
> -	.codecs = {"NAU88L25"}
> +	.codecs = {"10508825"}
>  };
>  
>  static struct sst_codecs bxt_codecs = {
> -- 
> 1.9.1
> 

-- 
~Vinod

  reply	other threads:[~2017-08-03  4:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  6:17 [PATCH] ASoC: Intel: Skylake: Use correct nuvoton codec ID Naveen M
2017-08-03  4:55 ` Vinod Koul [this message]
2017-08-03 16:28 ` Applied "ASoC: Intel: Skylake: Use correct nuvoton codec ID" to the asoc tree Mark Brown

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=20170803045522.GC3053@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=harshapriya.n@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=naveen.m@intel.com \
    --cc=pierre-louis.bossart@intel.com \
    --cc=tiwai@suse.de \
    /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).