From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>, Laura Abbott <labbott@redhat.com>
Cc: alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [alsa-devel] Correct modules for Bay Trail MAX98090 soc?
Date: Fri, 12 Aug 2016 14:26:31 -0500 [thread overview]
Message-ID: <390ded29-9be2-ba24-b24e-25ed3db26430@linux.intel.com> (raw)
In-Reply-To: <20160812161219.GG9347@sirena.org.uk>
On 8/12/16 11:12 AM, Mark Brown wrote:
> On Fri, Aug 12, 2016 at 08:51:34AM -0700, Laura Abbott wrote:
>> On 08/12/2016 04:49 AM, Mark Brown wrote:
>
>>> 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.
>
> Debian will be in the same boat too, there's another release coming
> soon.
It's not necessarily terribly complicated to enable this codec:
- we could borrow code from the existing code from the
cht_bsw_max98090_ti machine driver which relies on the dpcm driver.
- the patches developed for Baytrail-Cr will provide support for the
19.2MHz MCLK needed by this codec, they should land on the alsa-devel
mailing list this afternoon or early next week.
The main issue is to find hardware and someone with bandwidth to do the
changes.
prev parent reply other threads:[~2016-08-12 19:26 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
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 ` Pierre-Louis Bossart [this message]
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=390ded29-9be2-ba24-b24e-25ed3db26430@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 \
/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.