alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Michele Curti <michele.curti@gmail.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org, ao2@ao2.it,
	jarkko.nikula@linux.intel.com,
	pierre-louis.bossart@linux.intel.com, lk@bazdara.com
Subject: Re: Intel SST on a Bay Trail tablet
Date: Mon, 24 Aug 2015 20:17:31 +0200	[thread overview]
Message-ID: <20150824181731.GA471@asus> (raw)
In-Reply-To: <20150824142625.GM13546@localhost>

On Mon, Aug 24, 2015 at 07:56:25PM +0530, Vinod Koul wrote:
> On Mon, Aug 24, 2015 at 03:29:04PM +0200, Michele Curti wrote:
> > 
> > Damn, completely missed..
> > 
> > Hi Vinod,
> > if it's possible, could you please generate a fw_sst_0f28_ssp1.bin
> > also, so I can test my driver (mine was for the Asus X205TA laptop,
> > where the codec is on SSP1 port)?
> 
> Are you sure you ahve SSP1 port enabled. I have not seen anyone using that
> one. Jarkko do you know about this?
> 
> I will ask firmware folks for generation (i don't do that) and get back
>

Yes, I can confirm, SSP1 in under LPEA

    Scope (_SB)
    {
        Device (LPEA)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Name (_HID, "80860F28" /* Intel SST Audio DSP */)  // _HID: Hardware ID

            ... snip ...

            Device (SSP1)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Name (_HID, "SSPX0000" /* Intel SSP Device */)  // _HID: Hardware ID
                Name (_CID, "SSPX0000" /* Intel SSP Device */)  // _CID: Compatible ID

Full dsdt.dsl here:
https://github.com/michelecurti/x205ta/blob/master/dsdt.dsl


Thank you,
Michele

  parent reply	other threads:[~2015-08-24 18:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 13:29 Intel SST on a Bay Trail tablet 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2015-02-23 17:39 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
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

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=20150824181731.GA471@asus \
    --to=michele.curti@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@ao2.it \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=lk@bazdara.com \
    --cc=pierre-louis.bossart@linux.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).