From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luka Karinja Subject: Re: [PATCH 18/19] ASoC: Intel: Atom: add support for RT5642 Date: Tue, 22 Dec 2015 19:38:12 +0100 Message-ID: <56799894.90404@gmail.com> References: <5679871B.1050200@gmail.com> <56798CFC.7040909@gmail.com> <567991B8.4060304@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by alsa0.perex.cz (Postfix) with ESMTP id A65AB2659FC for ; Tue, 22 Dec 2015 19:38:15 +0100 (CET) Received: by mail-wm0-f45.google.com with SMTP id p187so121711535wmp.0 for ; Tue, 22 Dec 2015 10:38:15 -0800 (PST) In-Reply-To: <567991B8.4060304@linux.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Pierre-Louis Bossart , "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org > >> 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. > > Ok, thanks for the clarification, been fighting audio on it for a year too. i'll keep checking the list for followups