From: Laura Abbott <labbott@redhat.com>
To: Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: 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 08:51:34 -0700 [thread overview]
Message-ID: <6c9c0e51-76e1-b887-c5ea-2937bba116f9@redhat.com> (raw)
In-Reply-To: <20160812114905.GE9347@sirena.org.uk>
On 08/12/2016 04:49 AM, Mark Brown wrote:
> On Fri, Aug 12, 2016 at 06:37:11AM -0500, Pierre-Louis Bossart wrote:
>> On 8/12/16 4:53 AM, Mark Brown wrote:
>>> On Thu, Aug 11, 2016 at 06:31:27PM -0500, Pierre-Louis Bossart wrote:
>
>>>> 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.
>
> That's not really that helpful for a distro kernel (this is for Fedora
> AIUI).
>
Yes, this is unfortunate as it means that something is going to lose sound
support in Fedora. :( It's probably going to be the Chromebook unless another
group starts screaming louder.
Thanks,
Laura
next prev parent reply other threads:[~2016-08-12 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 20:42 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
2016-08-12 11:49 ` Mark Brown
2016-08-12 15:51 ` Laura Abbott [this message]
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=6c9c0e51-76e1-b887-c5ea-2937bba116f9@redhat.com \
--to=labbott@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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
all inboxes | Powered by JetHome®