All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Adam Williamson <awilliam@redhat.com>,
	lgirdwood@gmail.com,
	Jarkko Nikula <jarkko.nikula@linux.jf.intel.com>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Unsupported Valley View 'LPE' adapter?
Date: Mon, 2 Dec 2013 12:02:16 +0530	[thread overview]
Message-ID: <20131202063216.GJ8834@intel.com> (raw)
In-Reply-To: <1385865517.2566.36.camel@adam.happyassassin.net>

On Sat, Nov 30, 2013 at 06:38:37PM -0800, Adam Williamson wrote:
> On Sat, 2013-11-30 at 22:45 +0100, Clemens Ladisch wrote:
> > 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.
yes it doesnt look like HDA, but the SoC might have one which can be enabled
in BIOS...
> > 
> > > 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.
I think Liam or Jarkko might have something for you...

--
~Vinod
> 
> Ah! I did see that stuff, but it seemed so old it couldn't be
> relevant...
> 
> > > Is there any info I can provide to help?
> > 
> > "lspci -vv -d 8086:0f28"?
> 
> OK, will get that for you shortly. Thanks for the info.
> -- 
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> 

-- 

  reply	other threads:[~2013-12-02  7:29 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
2013-12-01  2:38   ` Adam Williamson
2013-12-02  6:32     ` Vinod Koul [this message]
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=20131202063216.GJ8834@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=awilliam@redhat.com \
    --cc=clemens@ladisch.de \
    --cc=jarkko.nikula@linux.jf.intel.com \
    --cc=lgirdwood@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.