From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Luka Karinja <luka.karinja@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 18/19] ASoC: Intel: Atom: add support for RT5642
Date: Tue, 22 Dec 2015 12:08:56 -0600 [thread overview]
Message-ID: <567991B8.4060304@linux.intel.com> (raw)
In-Reply-To: <56798CFC.7040909@gmail.com>
>> The machine driver is not loaded when the BIOS uses the 10EC5642
>> _HID. Add it to the white list of known _HIDs, codec_name is
>> already taken care of by previous commit
>>
>> Tested on Asus T100TAF.
>>
>
> I'm trying to get sound working on my T100TAF i did apply all the 19
> patches
> on top of broonie/sound and added UCM files to my system.
> Does the TAF need different UCM file than the T100TA?
The probe was tested but I am still fighting to get audio out. There are
additional patches needed to work-around a BIOS changes that fixes the
download issue shown in your log and also a change in the I2S routing,
but we can't figure out if there are any additional changes needed. I
suspect something is wrong with the i2S pin configuration (gpio setup)
Those patches and updated firmware have not been submitted so far, i'd
like to do so when it's actually working. This is on our to-do list,
along with MCLK support and jack detection. There are so many variations
of hardware that we are progressing slowly unfortunately.
next prev parent reply other threads:[~2015-12-22 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5679871B.1050200@gmail.com>
2015-12-22 17:48 ` [PATCH 18/19] ASoC: Intel: Atom: add support for RT5642 Luka Karinja
2015-12-22 18:08 ` Pierre-Louis Bossart [this message]
2015-12-22 18:38 ` Luka Karinja
2016-02-11 10:12 ` Luka Karinja
2016-02-11 14:00 ` Pierre-Louis Bossart
2015-12-18 2:35 [PATCH 00/19] Baytrail/Cherrytrail cleanups and fixes Pierre-Louis Bossart
2015-12-18 2:35 ` [PATCH 18/19] ASoC: Intel: Atom: add support for RT5642 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=567991B8.4060304@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=luka.karinja@gmail.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;
as well as URLs for NNTP newsgroup(s).