From: Takashi Iwai <tiwai@suse.de>
To: Adam Williamson <awilliam@redhat.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
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: Sun, 05 Jan 2014 11:55:43 +0100 [thread overview]
Message-ID: <s5hwqiebsuo.wl%tiwai@suse.de> (raw)
In-Reply-To: <1388370192.15622.8.camel@adam.happyassassin.net>
At Sun, 29 Dec 2013 18:23:12 -0800,
Adam Williamson wrote:
>
> On Sun, 2013-12-29 at 18:19 -0800, Adam Williamson wrote:
> > On Mon, 2013-12-02 at 17:56 -0800, Adam Williamson wrote:
> >
> > > > > > 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.
> >
> > So I got time today to poke at this device again, and here's something:
> > it's not actually a PCI device at all, I missed that. Neither lspci
> > (Linux) nor pcitree (Windows) shows a PCI device with ID 8086:0f28. It
> > must be connected some other way, SDIO or something. So, I don't know
> > how to get more info on it, really.
> >
> > I'll file a bug on this device with all the details I have attached, for
> > now, I guess.
>
> ...or, since the bug tracker is apparently down, I guess I can't. What's
> the next step? Just wait and see if I hear from someone with an
> @intel.com ? :/
>
> I honestly wasn't expecting it to be THIS difficult to get almost
> anything working on a vlv tablet :(
Ask Intel guys at best. It must be a device controlled by
i2c/spi/whatever, not a standard HD-audio. IIRC, the control can be
taken from ACPI, but it's not implemented properly yet.
Takashi
next prev parent reply other threads:[~2014-01-05 10:55 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
2013-12-30 2:19 ` Adam Williamson
2013-12-30 2:23 ` Adam Williamson
2014-01-05 10:55 ` Takashi Iwai [this message]
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=s5hwqiebsuo.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--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 \
--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