[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3a548725-5b52-4b3e-457a-f6ca93645b15@linux.intel.com>
Date: Thu, 11 Aug 2016 18:31:27 -0500
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Laura Abbott <labbott@...hat.com>, Jie Yang <yang.jie@...el.com>,
Takashi Iwai <tiwai@...e.com>
Cc: Vinod Koul <vinod.koul@...el.com>, Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
alsa-devel@...a-project.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Correct modules for Bay Trail MAX98090 soc?
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@...ux.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@...ux.intel.com>
> Acked-by: Jie Yang <yang.jie@...el.com>
> Signed-off-by: Vinod Koul <vinod.koul@...el.com>
> Signed-off-by: Mark Brown <broonie@...nel.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.
Powered by blists - more mailing lists