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

On Mon, 2013-12-02 at 12:02 +0530, Vinod Koul wrote:
> 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...

I don't think I saw anything like that. The firmware (pleeeeeease, call
it 'the firmware', I'm fighting a heroic (quixotic?) but retreating
battle against the trend to call a PC's firmware 'the BIOS' even when
it's not frickin' BIOS) is pretty barebones, it has 'on/off' switches
for various bits of hardware, but nothing more than that, and I'm pretty
sure they're all set 'on' OOTB, inc. audio.

> > > 
> > > > 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...

Hope so! Thanks for the reply and the redirect.

> > > > 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.

I'm just about to build a new test image which I'm throwing a couple of
kernel patches for other bugs into, I'll grab this lspci output while
I'm testing that.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2013-12-03  1:56 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
2013-12-03  1:56       ` Adam Williamson [this message]
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=1386035807.2566.145.camel@adam.happyassassin.net \
    --to=awilliam@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=jarkko.nikula@linux.jf.intel.com \
    --cc=lgirdwood@gmail.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