public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Laura Abbott <labbott@redhat.com>, Jie Yang <yang.jie@intel.com>,
	Takashi Iwai <tiwai@suse.com>, Vinod Koul <vinod.koul@intel.com>,
	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: Fri, 12 Aug 2016 06:37:11 -0500	[thread overview]
Message-ID: <4cba0e60-2dd4-38bd-6353-a6bf5b404d75@linux.intel.com> (raw)
In-Reply-To: <20160812095317.GZ9347@sirena.org.uk>

On 8/12/16 4:53 AM, Mark Brown wrote:
> On Thu, Aug 11, 2016 at 06:31:27PM -0500, Pierre-Louis Bossart wrote:
>> On 8/11/16 3:42 PM, Laura Abbott wrote:
>
>>> 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.
>
> That sounds like a regression, what's the plan to fix it.

The simple fix is easy: disable all other codecs and the
BYT_MAX98090 option will be enabled. BYT_MAX98090 relies on the 'old' 
non-dpcm driver which is used only for Chromebooks with Baytrail, which 
never enable any other codecs, so there was never any issue before.
If there is a need for concurrency, then a new machine driver based on 
the dpcm Atom driver needs to be created. I don't have a Baytrail 
chromebook so don't want to commit on the change.

  reply	other threads:[~2016-08-12 11:37 UTC|newest]

Thread overview: 8+ 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
2016-08-12  9:53   ` Mark Brown
2016-08-12 11:37     ` Pierre-Louis Bossart [this message]
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=4cba0e60-2dd4-38bd-6353-a6bf5b404d75@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox