All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Tyler Yeomans <tyeo098@gmail.com>
Cc: alsa-devel@alsa-project.org, jarkko.nikula@intel.com,
	liam.r.girdwood@intel.com
Subject: Re: Intel Baytrail Linux Audio
Date: Wed, 24 Jun 2015 21:33:14 +0530	[thread overview]
Message-ID: <20150624160314.GM19530@localhost> (raw)
In-Reply-To: <558ABDB6.4010702@gmail.com>

On Wed, Jun 24, 2015 at 10:24:54AM -0400, Tyler Yeomans wrote:
> Vinod,
> 
> Thank you for looking into this.
> I have attached the dmesg for this device.
> Please note I have tried kernels 3.16/19 4.0 and 4.1, all with same result.
> The attached dmesg file is from booting kernel 4.1/amd64:
> Linux mykro 4.1.0-040100-generic #201506220235 SMP Mon Jun 22
> 06:36:19 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> On Ubuntu 15.04
I can see these errors:
[    6.012196] (NULL device *): ipc: error DSP boot timeout
[    6.012386] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio not
registered

Jarrko, can you see why DSP boot fails, perhpas some resources are
missing/wrong

-- 
~Vinod

  reply	other threads:[~2015-06-24 16:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5589D025.7090700@gmail.com>
2015-06-24 10:11 ` Intel Baytrail Linux Audio Vinod Koul
2015-06-24 14:24   ` Tyler Yeomans
2015-06-24 16:03     ` Vinod Koul [this message]
2015-06-24 17:40       ` Tyler Yeomans
2015-06-25  6:38       ` Jarkko Nikula
2015-06-30 18:24         ` Tyler Yeomans
2015-06-30 22:57         ` Tyler Yeomans
2015-07-02 18:40           ` Nicolas George
2015-07-03  8:51             ` Liam Girdwood
2015-07-03  9:08               ` Antonio Ospite
2015-07-03  9:46                 ` Nicolas George
2015-07-03 10:32                   ` Antonio Ospite
2015-07-03 11:12                     ` Nicolas George
2015-07-03 12:10 Koul, Vinod
2015-07-03 12:36 ` Antonio Ospite
2015-07-03 13:06   ` Nicolas George
     [not found]     ` <559A90CE.2030105@gmail.com>
     [not found]       ` <20150707031950.GD11002@localhost>
2015-07-07 14:00         ` Tyler Yeomans
2015-07-07 17:08           ` Vinod Koul
2015-07-07 21:06             ` Tyler Yeomans
2015-07-08  3:36               ` Vinod Koul
2015-07-08  8:23                 ` Antonio Ospite
2015-07-08 14:30                   ` Tyler Yeomans
2015-07-08 16:21                     ` Antonio Ospite
2015-07-08 16:32                       ` Tyler Yeomans
2015-07-08 20:17                         ` Antonio Ospite
2015-07-08 20:24                           ` tyeo098
     [not found]                           ` <559EC436.30900@gmail.com>
2015-07-10  4:06                             ` Vinod Koul
2015-07-10 12:41                               ` Tyler Yeomans
2015-07-13 17:06                               ` Tyler Yeomans
2015-07-14  8:47                                 ` Vinod Koul
2015-07-23 15:24                                   ` Tyler Yeomans
2015-07-10  4:03                     ` Vinod Koul
2015-07-08 20:57                   ` Luka Karinja
     [not found]                   ` <559D88C1.3010504@bazdara.com>
2015-07-10  4:00                     ` Vinod Koul
2015-07-10 15:24                       ` Luka Karinja
  -- strict thread matches above, loose matches on Subject: below --
2015-07-03 13:43 Koul, Vinod

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=20150624160314.GM19530@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jarkko.nikula@intel.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=tyeo098@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.