From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Bernhard Übelacker" <bernhardu@vr-web.de>, alsa-devel@alsa-project.org
Subject: Re: bytcr_rt5640, baytrail: trying to get audio working
Date: Tue, 29 Mar 2016 21:46:26 -0500 [thread overview]
Message-ID: <56FB3E02.2050101@linux.intel.com> (raw)
In-Reply-To: <56FB06B5.1060900@vr-web.de>
On 3/29/16 5:50 PM, Bernhard Übelacker wrote:
> Hello Pierre-Louis,
> thank you for your answers and your efforts.
>
> Kind regards,
> Bernhard
>
> PS.: Could some info from a preinstalled Android of any help?
What would help is the schematics for your board, there are so many
variations out there that it's hard to generalize
on Baytrail devices the SSP2 is typically connected to AIF1 and SSP0 to
AIF2. On Baytrail-CR devices the SSP0 is connected to AIF1. SSP1 is
usually used for BT/FM.
You may want to play with the DAI links to see if you get better luck by
swapping the codec connections.
>
>
> Am 29.03.2016 um 02:04 schrieb Pierre-Louis Bossart:
>> If you modified the interrupt order then it's a Baytrail-CR device and
>> you will need to use the firmware that makes use of SSP0 (SSP2 is not
>> connected in this package). I am working to enable SSP0 routing directly
>> without the need for a new firmware but I haven't had time to test it.
>>
>> That said, we've not been successful so far with such Baytrail-CR
>> devices. So far the issue seem to be in the SSP0-AIF2 connection; if you
>> do a loopback within the DSP things work fine. Without access to the
>> schematics and the board information it's not straightforward to solve
>> the problem.
>> Note also that Baytrail-CR devices typically use different microphones
>> and speaker settings (differential mics, mono speakers typically) so you
>> may need to add some quirks.
>
> Just for reference if someone gets here via search engine:
>
> I have tried the firmware [1] and put it under /lib/firmware/intel/fw_sst_0f28.bin
> with the modified interrupt order and linux 4.5.0-rc7+, entered the
> amixer sequence and the speaker-test.
>
> I saw with that also no obvious errors in dmesg.
> Interrupts are also counted.
> The clicks on device open and close are not to hear anymore.
> But unfortunately it stays silent.
>
> [1] https://git.kernel.org/cgit/linux/kernel/git/vkoul/firmware.git/plain/intel/fw_sst_0f28_ssp0.bin?h=byt
>
prev parent reply other threads:[~2016-03-30 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 18:37 bytcr_rt5640, baytrail: trying to get audio working Bernhard Übelacker
2016-03-29 0:04 ` Pierre-Louis Bossart
2016-03-29 22:50 ` Bernhard Übelacker
2016-03-30 2:46 ` 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=56FB3E02.2050101@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bernhardu@vr-web.de \
/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;
as well as URLs for NNTP newsgroup(s).