All of lore.kernel.org
 help / color / mirror / Atom feed
From: bobby <bseventynine@yahoo.com>
To: alsa-devel@alsa-project.org
Subject: Re: Unsupported Valley View 'LPE' adapter?
Date: Thu, 27 Feb 2014 08:36:04 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140227T081207-421@post.gmane.org> (raw)
In-Reply-To: 1392795682.2351.10.camel@loki

Liam Girdwood <liam.r.girdwood <at> linux.intel.com> writes:

> 
> On Tue, 2014-02-18 at 20:59 -0800, Adam Williamson wrote:
> > On Mon, 2014-02-17 at 16:48 -0800, Adam Williamson wrote:
> > > On Mon, 2014-02-17 at 16:40 -0800, Adam Williamson wrote:
> > > > On Mon, 2014-02-17 at 09:54 +0000, bobby wrote:
> > > > > 
> > > > > This is a pci device for which the driver is not yet available.
> > > > > I went through the intel atom processor manual and found that it 
has 3 I2S 
> > > > > ports, has its 
> > > > > own DMA. The Soc is interfaced with LPE audio core via internal 
PCI bus. 
> > > > > Did you guys hear anything from intel about the driver support. 
Any inputs 
> > > > > would be of great help please
> > > > 
> > > > Jan Michael Brummer at Intel pointed this out to me recently:
> > > > 
> > > > 
https://kernel.googlesource.com/pub/scm/linux/kernel/git/lrg/asoc/+/intel/h
aswell-audio-dsp%5E
> > > > 
> > > > looks like it's being worked on.
> > > 
> > > Heh, that's actually just a mirror of the git ASoC branch. All those
> > > patches went through this very list last week. I don't know precisely
> > > how the upstreaming process goes for this stuff, but I'm guessing 
it'll
> > > wind up in 3.14 or 3.15.
> > > 
> > > (I may try building the patches into my Fedlet kernel builds and see 
if
> > > that gets anywhere...)
> > 
> > FWIW, I tried building a 3.14rc3 kernel with these patches applied and
> > the drivers enabled as modules. On boot on a Dell Venue 8 Pro, all the
> > relevant modules are loaded, but there's no ALSA device, and no
> > obviously useful errors in any logs, or useful output from alsa-
info.sh.
> > Is it expected that the driver doesn't actually work yet? Per the 
recent
> > commits, do I need some kind of firmware? Any debugging that would be
> > useful?
> 
> Sorry, we're not finished with the upstreaming yet. The current patches
> upstream are for the low level parts of the Intel DSP drivers. Jarkko
> and I still have to upstream the upper layers of the drivers (probably
> today) and you will also need firmware.
> 
> Once upstream the drivers will support Valley View, Baytrail, Haswell
> and Broadwell. The firmware for Baytrail and Valleyview will be
> available shortly too.
> 
> Liam 
> 
> 

Thanks Liam and Jarkko saw your patches related to the Intel SST Audio 
Platform drivers, I hope the upstreaming process is complete for this 
module. Please let us know when the firmware is available.

I have few question here, the i2s mode should be enabled in the platform 
drivers right. 

In the Bayley Bay bios I saw that the LPE audio could be enumerated via 
PCI or ACPI, the patches I saw mostly cover the ACPI mode. Will the PCI 
mode be covered in the patches.

Thanks in Advance
Bobby

      reply	other threads:[~2014-02-27  8:36 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
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 [this message]

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=loom.20140227T081207-421@post.gmane.org \
    --to=bseventynine@yahoo.com \
    --cc=alsa-devel@alsa-project.org \
    /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.