alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Antonio Ospite <ao2@ao2.it>, alsa-devel@alsa-project.org
Cc: Vinod Koul <vinod.koul@intel.com>,
	Harsha Priya <priya.harsha@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Ramesh Babu K V <Ramesh.Babu@intel.com>,
	Omair Mohammed Abdullah <omair.m.abdullah@intel.com>
Subject: Re: Intel SST on a Bay Trail tablet
Date: Tue, 03 Mar 2015 16:54:53 +0200	[thread overview]
Message-ID: <54F5CB3D.7020100@linux.intel.com> (raw)
In-Reply-To: <20150303151621.c6fc3cfa308aed62484b87a0@ao2.it>

Hi

On 03/03/2015 04:16 PM, Antonio Ospite wrote:
> On Mon, 23 Feb 2015 18:39:13 +0100
> Antonio Ospite <ao2@ao2.it> wrote:
>
>> Hi,
>>
>> I am trying to get the Intel SST driver working on a Teclast X98 Air 3G
>> [1], it's a Bay Trail tablet. The tests below have been made with
>> 4.0.0-rc1 and the firmware files from
>> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/intel
>>
>
> Hi, has anyone had a chance to take a look at my previous message?
>
I forgot to answer... Some earlier notes including Teclast X98 Air 3G 
and patch attempts are collected here:

https://bugzilla.kernel.org/show_bug.cgi?id=86581

Unfortunately bug is not solved since it looks these newer Baytrail 
Windows 8.1 based machines use different SSP port than previous ones and 
Linux DSP firmware is hardcoded for SSP2.

What's interesting does that Android FW use other than SSP2 or does 
Teclast have some extra amplifier.

> [...]
>> Last question, what is the difference between having the device detected
>> by sound/soc/intel/sst-acpi.c (like in my case) opposed to
>> sound/soc/intel/sst/sst_acpi.c? I can see the 80860F28 id in both the
>> files but they seem to load different firmwares.
>>

Different firmware, driver stack and machine driver despite the same LPE 
ACPI ID and codec ACPI ID. (We really should have some additional DMI 
quirks that does the selection because of the same ACPI IDs).

>
> Another thing I noticed is that the Android driver for the rt5640 codec
> defines some controls which are not in the mainline driver:
>
>    OUT MIXR BST3 Switch
>    OUT MIXL BST3 Switch
>    RECMIXR BST3 Switch
>    RECMIXL BST3 Switch
>    IN1 Mode Control
>    IN2 Mode Control
>
I'm not sure but these might be FW implemented DSP controls? Vinod, do 
you know?

-- 
Jarkko

  reply	other threads:[~2015-03-03 14:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 17:39 Intel SST on a Bay Trail tablet Antonio Ospite
2015-03-03 14:16 ` Antonio Ospite
2015-03-03 14:54   ` Jarkko Nikula [this message]
2015-03-03 16:17     ` Vinod Koul
2015-03-03 16:25       ` Babu, Ramesh
2015-03-04 16:02     ` Antonio Ospite
2015-03-12 13:45       ` Antonio Ospite
2015-03-12 14:30         ` Jarkko Nikula
2015-03-13  6:33           ` Vinod Koul
2015-03-13 14:36             ` Antonio Ospite
2015-04-03 13:34       ` Antonio Ospite
2015-04-14 13:02         ` Antonio Ospite
2015-04-14 14:06           ` Jarkko Nikula
2015-04-16 15:21             ` Antonio Ospite
2015-04-16 15:21             ` Antonio Ospite
2015-06-24 10:16             ` Vinod Koul
2015-06-24 11:25               ` Antonio Ospite
2015-06-25  5:50               ` Vinod Koul
2015-06-25 10:21                 ` Antonio Ospite
2015-06-25 16:47                   ` Vinod Koul
2015-06-26 13:05                     ` Antonio Ospite
2015-06-27 14:47                       ` Vinod Koul
2015-07-15 10:11                         ` Istvan Sandor
2015-09-18  0:41                         ` LemonZou
  -- strict thread matches above, loose matches on Subject: below --
2015-08-24 13:29 Michele Curti
2015-08-24 14:26 ` Vinod Koul
2015-08-24 15:05   ` Luka Karinja
2015-08-24 15:37     ` Pierre-Louis Bossart
2015-08-24 15:38     ` Michele Curti
2015-08-24 18:17   ` Michele Curti
2015-08-24 19:28     ` Pierre-Louis Bossart
2015-08-25  8:06       ` Michele Curti
2015-09-17 20:54         ` Luka Karinja
2015-09-21  7:14           ` Michele Curti

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=54F5CB3D.7020100@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=Ramesh.Babu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@ao2.it \
    --cc=mika.westerberg@linux.intel.com \
    --cc=omair.m.abdullah@intel.com \
    --cc=priya.harsha@intel.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 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).