All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Laura Abbott <labbott@redhat.com>, Jie Yang <yang.jie@intel.com>,
	Takashi Iwai <tiwai@suse.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Correct modules for Bay Trail MAX98090 soc?
Date: Thu, 11 Aug 2016 18:31:27 -0500	[thread overview]
Message-ID: <3a548725-5b52-4b3e-457a-f6ca93645b15@linux.intel.com> (raw)
In-Reply-To: <88774f89-ce4a-1877-db49-b018d725f1cd@redhat.com>

On 8/11/16 3:42 PM, Laura Abbott wrote:
> Hi,
>
> Fedora got a bug report[1] that sound was failing on Intel Bay Trail Socs
> that use the MAX98090 module. I found
>
> Author: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> Date:   Mon Feb 8 10:45:38 2016 +0530
>
>     ASoC: Intel: Load the atom DPCM driver only
>         DPCM driver is recommended for BYT, CHT based platforms, so if
>     CONFIG_SND_SST_IPC_ACPI is selected then don't compile the BYT
>     Device IDs in common ACPI driver to avoid probe conflicts.
>         Signed-off-by: Pierre-Louis Bossart
> <pierre-louis.bossart@linux.intel.com>
>     Acked-by: Jie Yang <yang.jie@intel.com>
>     Signed-off-by: Vinod Koul <vinod.koul@intel.com>
>     Signed-off-by: Mark Brown <broonie@kernel.org>
>
>
> which changed the dependencies for CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH.
> The set of options Fedora selects means that
> CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH
> can't be selected. Is there another driver that's supposed to replace
> CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH on Bay Trail or do the dependencies
> need to be updated? The bugzilla has alsa-info for working and non-
> working cases and the Fedora config is attached.

If you remove support for all other baytrail options this driver should 
still be there and selectable. We just can't support both this driver 
for Chromebooks and the rest for other machines with the same 
distribution at the moment.

  reply	other threads:[~2016-08-11 23:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 20:42 Correct modules for Bay Trail MAX98090 soc? Laura Abbott
2016-08-11 23:31 ` Pierre-Louis Bossart [this message]
2016-08-12  9:53   ` Mark Brown
2016-08-12  9:53     ` Mark Brown
2016-08-12 11:37     ` Pierre-Louis Bossart
2016-08-12 11:49       ` Mark Brown
2016-08-12 15:51         ` Laura Abbott
2016-08-12 16:12           ` Mark Brown
2016-08-12 19:26             ` [alsa-devel] " Pierre-Louis Bossart

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=3a548725-5b52-4b3e-457a-f6ca93645b15@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=labbott@redhat.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=vinod.koul@intel.com \
    --cc=yang.jie@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.