From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>,
Jarkko Nikula <jarkko.nikula@linux.jf.intel.com>,
lgirdwood@gmail.com, tiwai@suse.de, liam.r.girdwood@intel.com,
subhransu.s.prusty@intel.com
Subject: Re: [PATCH v2 0/5] ASoC: Intel: ACPI support and machines
Date: Wed, 05 Nov 2014 09:49:35 +0200 [thread overview]
Message-ID: <5459D68F.6030100@linux.intel.com> (raw)
In-Reply-To: <20141104111513.GE3815@sirena.org.uk>
On 11/04/2014 01:15 PM, Mark Brown wrote:
>> Ok, so firmware appears to works on other than CR Baytrails too. Is it
>> available in linux-firmware since if it's not when changing the platform
>> drivers there will be obvious regressions to users?
> Can we take a step back here: what are the firmwares and hardware
> platforms we're talking about here?
Only Baytrail and its variants. Current upstreamed drivers use
"intel/fw_sst_0f28.bin-48kHz_i2s_master" but that FW doesn't have as
much features like compressed audio and is not compatible with the one
Vinod's team is upstreaming.
Goal is to switch to new implementation since it covers more platforms
but do switchover as seamlessly as possible for Baytrail. Problem at the
moment for Baytrail that both current and new drivers probe using the
same ACPIIDs and FW for new drivers is not yet in linux-firmware.
>
>> Well, those audio routing differences require to have DMI quirks. E.g. T100
>> has analogue internal mic, Dell Venue 8 Pro 5830 has digital mic connected
>> to DMIC2 of the RT564x and some have it connected to DMIC1.
> Are any of these things on sale at the minute? Looks like T100 and the
> Dell both are but I'm not sure if they're current or previous models.
T100 and Dell are. Third known audio routing difference is used in
reference design so I guess that setup is found on some models too. Then
there are byt-max98090 based Chromebooks that use current drivers and FW.
--
Jarkko
next prev parent reply other threads:[~2014-11-05 7:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 5:31 [PATCH v2 0/5] ASoC: Intel: ACPI support and machines Vinod Koul
2014-11-04 5:31 ` [PATCH v2 1/5] ASoC: Intel: mrfld - remove unnecessary check for pointer Vinod Koul
2014-11-04 5:31 ` [PATCH v2 2/5] ASoC: Intel: mrfld - create separate module for pci part Vinod Koul
2014-11-04 5:31 ` [PATCH v2 3/5] ASoC: Intel: mrfld - add shim save restore Vinod Koul
2014-11-04 5:31 ` [PATCH v2 4/5] ASoC: Intel: mrfld- add ACPI module Vinod Koul
2014-11-04 5:31 ` [PATCH v2 5/5] ASoC: Intel: add BYTCR machine driver with RT5640 Vinod Koul
2014-11-04 9:19 ` Jarkko Nikula
2014-11-04 9:32 ` Vinod Koul
2014-11-05 7:54 ` Jarkko Nikula
2014-11-05 8:44 ` Vinod Koul
2014-11-04 8:09 ` [PATCH v2 0/5] ASoC: Intel: ACPI support and machines Jarkko Nikula
2014-11-04 8:25 ` Vinod Koul
2014-11-04 9:05 ` Jarkko Nikula
2014-11-04 9:15 ` Liam Girdwood
2014-11-04 9:31 ` Vinod Koul
2014-11-04 9:33 ` Vinod Koul
2014-11-04 11:15 ` Mark Brown
2014-11-05 7:49 ` Jarkko Nikula [this message]
2014-11-05 8:43 ` Vinod Koul
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=5459D68F.6030100@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.jf.intel.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=tiwai@suse.de \
--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.