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

On Thu, Mar 12, 2015 at 04:30:38PM +0200, Jarkko Nikula wrote:
> Hi
> 
> On 03/12/2015 03:45 PM, Antonio Ospite wrote:
> >>Do you confirm that the ADMA0F28 and SSPX0000 devices I mentioned in the
> >>original mail are not necessary in the DSDT?
> >[...]
> >
> I don't know what their function is. I've seen them only in newer
> DSDT tables. I guess Windows 8.1 uses them for power management etc
> or it has separate drivers for DMA and SSP ports.
> 
> >Ping.
> >
> >Can anyone comment on this and my other questions in the previous email
> >regarding the DSP firmware?
> >
> Vinod, Ramesh: Do you know would it be possible to run that Android
> ELF firmware that is installed in the Teclast with the newer stack
> in sound/soc/intel/sst?
Sorry havent followed the thread, but we should be able to use the upstream
firware.
The ELF binary and the upstream ones are similar, we decided sometime back
to not use ELF for future dev so we didnt upstream that part.

-- 
~Vinod

  reply	other threads:[~2015-03-13  6:37 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
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 [this message]
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=20150313063345.GC32000@intel.com \
    --to=vinod.koul@intel.com \
    --cc=Ramesh.Babu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@ao2.it \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=omair.m.abdullah@intel.com \
    --cc=priya.harsha@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).