Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Adam Williamson <awilliam@redhat.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
	alsa-devel@alsa-project.org,
	Harsha Priya <priya.harsha@intel.com>
Subject: Re: Unsupported Valley View 'LPE' adapter?
Date: Sat, 30 Nov 2013 22:45:14 +0100	[thread overview]
Message-ID: <529A5C6A.70604@ladisch.de> (raw)
In-Reply-To: <1385840039.2566.12.camel@adam.happyassassin.net>

Adam Williamson wrote:
> In Windows' Device Manager I see an 'Intel SST Audio Device' with PCI ID
> 0x86:0f28. Indeed, the PCI ID database has this listed as "ValleyView
> LPE Audio Controller" - http://pci-ids.ucw.cz/read/PC/8086/0f28 . But
> hda-intel does not have 0f28 as a supported device.
>
> So...what is this 0f28?

It is not an HDA controller.  The SST thingy uses I²S codecs.

> Is support for it going to be added?

There is something in sound/soc/mid-x86/, but that is only for the
Medfield platform.  The PCI SST driver that was not merged four years
ago used the ID 080a.

Only Intel knows.

> Is there any info I can provide to help?

"lspci -vv -d 8086:0f28"?


Regards,
Clemens

  reply	other threads:[~2013-11-30 21:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 19:33 Unsupported Valley View 'LPE' adapter? Adam Williamson
2013-11-30 21:45 ` Clemens Ladisch [this message]
2013-12-01  2:38   ` Adam Williamson
2013-12-02  6:32     ` Vinod Koul
2013-12-03  1:56       ` Adam Williamson
2013-12-30  2:19         ` Adam Williamson
2013-12-30  2:23           ` Adam Williamson
2014-01-05 10:55             ` Takashi Iwai
2014-02-17  9:54               ` bobby
2014-02-18  0:40                 ` Adam Williamson
2014-02-18  0:48                   ` Adam Williamson
2014-02-19  4:59                     ` Adam Williamson
2014-02-19  7:41                       ` Liam Girdwood
2014-02-27  8:36                         ` bobby

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=529A5C6A.70604@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=awilliam@redhat.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