Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: pstglia@android-x86.org, patch@alsa-project.org
Cc: alsa-devel@alsa-project.org, Paulo Sergio Travaglia <pstglia@gmail.com>
Subject: Re: [PATCH] ASoC: Intel: add bytcr-wm5102 machine driver
Date: Sun, 4 Jun 2017 17:27:51 -0500	[thread overview]
Message-ID: <df6f715c-5f63-9403-8dd0-13dad8f62fa6@linux.intel.com> (raw)
In-Reply-To: <593313f5.3636c80a.50e05.47e9@mx.google.com>


> diff --git a/sound/soc/intel/atom/sst/sst_acpi.c b/sound/soc/intel/atom/sst/sst_acpi.c
> index dd250b8..1669c46 100644
> --- a/sound/soc/intel/atom/sst/sst_acpi.c
> +++ b/sound/soc/intel/atom/sst/sst_acpi.c
> @@ -240,10 +240,17 @@ static int sst_platform_get_resources(struct intel_sst_drv *ctx)
>   }
>   
>   
> -static int is_byt_cr(struct device *dev, bool *bytcr)
> +static int is_byt_cr(struct device *dev, struct sst_acpi_mach *mach, bool *bytcr)
>   {
>   	int status = 0;
>   
> +	/* Lenovo Yoga2 exception - acpi_ipc_irq_index is the 1st index,
> +	   but iosf_mbi_read (bios_status) returns 0 for bits 26:27 */
> +	if (!strcmp(mach->drv_name, "bytcr_wm5102")) {
> +		*bytcr = true;
> +		return status;
> +	}

well no, this isn't the right way to do this. quirks need to be based on 
real hardware information (e.g. DMI) and not a driver name.

The rest looks more of less ok, it's not clear to me if all the quirks 
are needed and make sense.

  reply	other threads:[~2017-06-04 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 19:54 [PATCH] ASoC: Intel: add bytcr-wm5102 machine driver pstglia
2017-06-04 22:27 ` Pierre-Louis Bossart [this message]
2017-06-05 14:25   ` Paulo Sergio
2017-06-05 16:37     ` Pierre-Louis Bossart
2017-06-05 17:01       ` Paulo Sergio

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=df6f715c-5f63-9403-8dd0-13dad8f62fa6@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=patch@alsa-project.org \
    --cc=pstglia@android-x86.org \
    --cc=pstglia@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox